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

BEROPS, s.r.o.

ActiveCompany ID (IČO) 36336963Limited liability company (s.r.o.)Est. 2004Trenčín, Trenčín Region
Official record (RPO) ↗
Age22 yearsincorporated 10 Jul 2004
In Trenčín7,012live companies
At this address21live companies incl. this one

In brief

BEROPS, s.r.o. is a limited liability company (s.r.o.) established in Slovakia on 10 July 2004. Its registered office is in Trenčín, Trenčín District, Trenčín Region, at an address shared with 20 other live companies. It was previously called BHS Technology s.r.o., a name it changed on 13 September 2016.

Register details

Registered nameBEROPS, s.r.o.
Company ID (IČO)36336963
Company typeLimited liability company (s.r.o.)
Registered officePiaristická 6836, 911 01 Trenčín

Timeline

Register events, newest first.

  • Name changedPreviously BHS Technology s.r.o.
  • Incorporated

Register entries

From the register.

Incorporated10 July 2004
Share capital€6,640

Location

Registered office in Trenčín, Trenčín District, Trenčín Region.

Live companies in Trenčín7,012
Live companies in Trenčín District10,188
New in Trenčín, past 12 months415

Also registered at this address

20 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.