Trust Pay, a. s.
In brief
Trust Pay, a. s. is a joint-stock company (a.s.) established in Slovakia on 3 December 2009. At 16 years old it is older than 94% of the 449 live companies whose main activity is other activities auxiliary to financial services, except insurance and pension funding. Its registered office is in Bratislava-Nové Mesto, Bratislava III, Bratislava Region, at an address shared with 14 other live companies. 24 live companies in Bratislava-Nové Mesto share the same main activity.
Register details
Timeline
Register events, newest first.
- Incorporated
Register entries
From the register.
Other activities auxiliary to financial services, except insurance and pension funding in Slovakia
Live companies whose main activity is 66.19: 449 in total, median age 4 years, 24 incorporated in the past 12 months.
Location
Registered office in Bratislava-Nové Mesto, Bratislava III, Bratislava Region.
Also registered at this address
14 other live companies share this registered office; shown are those incorporated closest in time to this one.
- PKPlavecký klub ORCA SPORT42135460 · Est. 2008 · 93.12
- IFInštitút finančného a podnikateľského vzdelávania50592122 · Est. 2016 · 94.11
- KA"Klub Atid"36064572 · Est. 2002 · 94.99
- BCBusiness Consultant s.r.o.50866559 · Est. 2017
- PK"PCM - KOMUNIKUJETE? ALEBO LEN ROZPRÁVATE..."51171783 · Est. 2017 · 94.99
- Pplávame.sk53113314 · Est. 2020 · 93.12
- PKPlavecký klub ORCA Bratislava31266665 · Est. 1998 · 93.12
- JNJunion nadácia31781209 · Est. 1997 · 88.99
Similar companies
Live companies with the same main activity, nearest first.
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.