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

English

DRU - PRESS

Age36 years
older than 99% of its sector
Same activity, Slovakia1,469live companies · the oldest
At this address1only this company

In brief

DRU - PRESS is a cooperative established in Slovakia on 21 June 1990. At 36 years old it is older than 99% of the 1,469 live companies whose main activity is other publishing activities, except software publishing.

Register details

Registered nameDRU - PRESS
Company ID (IČO)00680559
Company typeCooperative
Registered officeFraňa Kráľa 16, Bratislava
Nature of business (NACE Rev. 2.1, converted from SK NACE Rev. 2)58.19 Other publishing activities, except software publishing
International sector (ISIC Rev.4)J · 58 Publishing activities

Timeline

Register events, newest first.

  • Incorporated

Register entries

From the register.

Incorporated21 June 1990
Share capital€1,659.70

Other publishing activities, except software publishing in Slovakia

Live companies whose main activity is 58.19: 1,469 in total, median age 10 years, 96 incorporated in the past 12 months.

All 1,469 companies
This company's decadeOther decades
02004006008001990s: 81811990s2000s: 2612612000s2010s: 5955952010s2020s: 5325322020s
Incorporated per year, still live
0501001502002011: 4220112012: 572013: 9620132014: 762015: 4520152016: 562017: 6220172018: 552019: 6120192020: 542021: 8120212022: 632023: 7620232024: 842025: 9520252026: 79

Location

Registered office.

Similar companies

Live companies with the same main activity, nearest first.

Compare all

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.