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

HerbaLuxe s. r. o.

ActiveCompany ID (IČO) 46228551Limited liability company (s.r.o.)Est. 2011Humenné, Prešov Region
Official record (RPO) ↗
Age15 yearsincorporated 15 Jun 2011
In Humenné2,097live companies
At this address17live companies incl. this one

In brief

HerbaLuxe s. r. o. is a limited liability company (s.r.o.) established in Slovakia on 15 June 2011. Its registered office is in Humenné, Humenné District, Prešov Region, at an address shared with 16 other live companies. It was previously called INVEST&CREDIT, s.r.o., a name it changed on 12 February 2026.

Register details

Registered nameHerbaLuxe s. r. o.
Company ID (IČO)46228551
Company typeLimited liability company (s.r.o.)
Registered officeLipová 1, 066 01 Humenné

Timeline

Register events, newest first.

  • Name changedPreviously INVEST&CREDIT, s.r.o.
  • Incorporated

Register entries

From the register.

Incorporated15 June 2011
Share capital€50,000

Location

Registered office in Humenné, Humenné District, Prešov Region.

Live companies in Humenné2,097
Live companies in Humenné District3,290
New in Humenné, past 12 months112

Also registered at this address

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