ISPER Data s. r. o.
In brief
ISPER Data s. r. o. is a limited liability company (s.r.o.) established in Slovakia on 10 May 2012. It is 14 years old; 81% of the 159 live companies whose main activity is telecommunication reselling activities and intermediation service activities for telecommunication are older. Its registered office is in Bratislava-Petržalka, Bratislava V, Bratislava Region, at an address shared with 14 other live companies. 15 live companies in Bratislava-Petržalka share the same main activity.
Register details
Timeline
Register events, newest first.
- Incorporated
Register entries
From the register.
Telecommunication reselling activities and intermediation service activities for telecommunication in Slovakia
Live companies whose main activity is 61.20: 159 in total, median age 19 years, 0 incorporated in the past 12 months.
Location
Registered office in Bratislava-Petržalka, Bratislava V, Bratislava Region.
Also registered at this address
14 other live companies share this registered office; shown are those incorporated closest in time to this one.
- ISISPER Slovakia s.r.o.46660551 · Est. 2012 · 61.20
- IIISPER Internet s. r. o.46660585 · Est. 2012
- IDISPER Datatechnik s. r. o.46661816 · Est. 2012
- ISISPER Services s. r. o.46536256 · Est. 2012 · 61.20
- INISPER Networks s. r. o.46524312 · Est. 2012 · 61.20
- ITISPER Technologies s.r.o.46945920 · Est. 2013 · 61.20
- IPISPER Provider s. r. o.46945857 · Est. 2013 · 61.20
- HKHokejbalový klub Buccaneers42176824 · Est. 2010 · 93.12
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.