Data from the official company registers of 12 countries. Not an official register.

English
About
SearchMethodologyAbout

Countries

CZCzechiaEEEstoniaFIFinlandFRFranceIEIrelandLVLatviaNONorwayRORomaniaSKSlovakiaSESwedenTWTaiwanGBUnited Kingdom

Languages

EnglishGaeilgeNorskSuomiSvenskaEestiLatviešuFrançaisČeštinaSlovenčinaRomână繁體中文

Code Support s. r. o.

ActiveCompany ID (IČO) 51943000Limited liability company (s.r.o.)Est. 2018Košice-Staré Mesto, Košice Region
Official record (RPO) ↗
Age8 yearsincorporated 11 Sept 2018
In Košice-Staré Mesto8,663live companies
At this address4live companies incl. this one

In brief

Code Support s. r. o. is a limited liability company (s.r.o.) established in Slovakia on 11 September 2018. Its registered office is in Košice-Staré Mesto, Košice I, Košice Region, at an address shared with 3 other live companies. It was previously called Pixenio, s.r.o., a name it changed on 18 June 2025.

Register details

Registered nameCode Support s. r. o.
Company ID (IČO)51943000
Company typeLimited liability company (s.r.o.)
Registered officeSvätoplukova 21, 040 01 Košice-Staré Mesto

Timeline

Register events, newest first.

  • Name changedPreviously Pixenio, s.r.o.
  • Incorporated

Register entries

From the register.

Incorporated11 September 2018
Share capital€5,100

Location

Registered office in Košice-Staré Mesto, Košice I, Košice Region.

Live companies in Košice-Staré Mesto8,663
Live companies in Košice I12,006
New in Košice-Staré Mesto, past 12 months304

Also registered at this address

3 other live companies share this registered office.

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.