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ă繁體中文

Extrabuild s. r. o.

ActiveCompany ID (IČO) 57010978Limited liability company (s.r.o.)Est. 2025Košice-Pereš, Košice Region
Official record (RPO) ↗
Age1 yearincorporated 17 Jun 2025
In Košice-Pereš214live companies
At this address22live companies incl. this one

In brief

Extrabuild s. r. o. is a limited liability company (s.r.o.) established in Slovakia on 17 June 2025. Its registered office is in Košice-Pereš, Košice II, Košice Region, at an address shared with 21 other live companies. It was previously called Welp s. r. o., a name it changed on 3 December 2025.

Register details

Registered nameExtrabuild s. r. o.
Company ID (IČO)57010978
Company typeLimited liability company (s.r.o.)
Registered officeSabinovská 138/2, 040 11 Košice-Pereš

Timeline

Register events, newest first.

  • Name changedPreviously Welp s. r. o.
  • Incorporated

Register entries

From the register.

Incorporated17 June 2025
Share capital€5,000

Location

Registered office in Košice-Pereš, Košice II, Košice Region.

Live companies in Košice-Pereš214
Live companies in Košice II8,059
New in Košice-Pereš, past 12 months15

Also registered at this address

21 other live companies share this registered office; shown are those incorporated closest in time to this one.

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.