SetArn s. r. o.
In brief
SetArn s. r. o. is a limited liability company (s.r.o.) established in Slovakia on 6 April 2022. It is 4 years old; 72% of the 769 live companies whose main activity is manufacture of computers and peripheral equipment are older. Its registered office is in Bratislava-Nové Mesto, Bratislava III, Bratislava Region, at an address shared with 1,324 other live companies. 28 live companies in Bratislava-Nové Mesto share the same main activity. It was previously called Attix Bro s. r. o., a name it changed on 22 December 2023.
Register details
Timeline
Register events, newest first.
- Name changedPreviously Attix Bro s. r. o.
- Incorporated
Register entries
From the register.
Manufacture of computers and peripheral equipment in Slovakia
Live companies whose main activity is 26.20: 769 in total, median age 6 years, 11 incorporated in the past 12 months.
Location
Registered office in Bratislava-Nové Mesto, Bratislava III, Bratislava Region.
Also registered at this address
1,324 other live companies share this registered office; shown are those incorporated closest in time to this one.
- MAM&A aviation s. r. o.54516943 · Est. 2022 · 51.21
- GSGlobal Smart Solution s.r.o.54514177 · Est. 2022
- MSmegaprodukt s. r. o.54497515 · Est. 2022 · 68.20
- LSLAKI Servis s. r. o.54546010 · Est. 2022
- AGAE garage s. r. o.54497027 · Est. 2022 · 49.41
- IMIFB Market s.r.o.54558433 · Est. 2022 · 69.20
- FTFee Trading s.r.o.54503353 · Est. 2022 · 46.12
- LELEO education, s. r. o.54546494 · Est. 2022
Similar companies
Live companies with the same main activity, nearest first.
Sources
Register data: Ministry of the Interior of the Slovak Republic, Register of Legal Entities, Entrepreneurs and Public Authorities, bulk open data (CC BY 4.0), as of 21 October 2026. Region and district names: Wikidata (CC0). Industry names: European Union, EU Vocabularies (NACE Rev. 2.1). Context figures are modified and derived data computed by FirmsDB from these sources. This page is not an official register; check the company's entry in the RPO before relying on it.