Open Company Data in Slovakia: Official Sources, APIs and Reuse Rights

Slovakia has a serious official company-data ecosystem, but it should not be reduced to a simple list of companies. The right way to evaluate Slovakia is to start with the official register, then add open-data, statistics, procurement, intellectual-property and regulator layers.

The strongest route is RPO Register of Legal Entities, ORSR Commercial Register, Register of Financial Statements, Slovak statistics API, RPVS open data and API, data.slovensko.sk, Public Procurement Office, NBS supervised entities, Industrial Property Office, Financial Administration, Slov-Lex, Ministry of Justice register pages and GLEIF LEI records. That makes Slovakia a deep EU official-source guide with RPO/ORSR/RPVS/statistics API evidence, GDPR/beneficial-owner caveats, source logos, Resource Pack and contact-data boundary, but it does not remove the usual reuse checks: dataset terms, attribution, no-endorsement language, privacy, marketing-law boundaries and source freshness.

This guide maps the main official sources for company data in Slovakia, explains what each source can and cannot do, and shows where a normalized CompaniesData-style dataset adds value.

The deeper question is not whether a source exists. The useful question is which source can be trusted for identity, which one proves events or filings, which one is usable at scale, which one is only a manual service, and which fields become legally sensitive once the data is reused commercially.

Quick Answer

Slovakia is publishable as a deep EU reference article because the Statistical Office's RPO, the Ministry of Justice commercial register, the financial statements register, RPVS open data/API, statistics APIs, the national open-data portal, procurement, NBS supervised-entity data, industrial-property, tax, legal-publication and GLEIF layers all passed live QA. The safe claim is not that Slovakia publishes one unrestricted master file with every commercially useful company field. The safe claim is that Slovakia has unusually strong official legal-entity, commercial-register, public-sector-partner, financial-statement and API/open-data layers, while GDPR, beneficial-owner reuse, officer/contact fields, no-endorsement language and marketing-contact boundaries still matter.

For practical work, the most useful source stack is: RPO Register of Legal Entities, RPO organization record with history, ORSR Commercial Register, Register of Financial Statements, Slovak Statistics API help, RPVS open data.

The safe editorial answer is this: Slovakia has strong public and official business-data sources, but public data is not automatically bulk-downloadable, marketing-ready or free of personal-data constraints.

A serious Slovakia dataset normally needs at least four layers: the legal register for entity identity, official publications or filings for change events, public procurement/regulator/IP/statistical sources for enrichment, and a separate compliance layer for privacy, contact-data use, suppression and lawful outreach.

Key Takeaways

• Best starting point: RPO Register of Legal Entities, ORSR Commercial Register, Register of Financial Statements, Slovak statistics API, RPVS open data and API, data.slovensko.sk, Public Procurement Office, NBS supervised entities, Industrial Property Office, Financial Administration, Slov-Lex, Ministry of Justice register pages and GLEIF LEI records.
• Core source stack: RPO Register of Legal Entities, RPO organization record with history, ORSR Commercial Register, Register of Financial Statements, Slovak Statistics API help, RPVS open data.
• Reuse rule: public visibility is not the same as bulk reuse, resale permission or marketing-contact permission.
• Buyer value: the useful dataset is the normalized, deduplicated and source-auditable version, not a raw list of portal links.
• Commercial separation: official company records, enriched company profiles and business contact data should remain separate layers with separate compliance notes.

Editorial Methodology

This article uses an official-source-first method. Sources are included when they help verify legal existence, public filings, procurement activity, taxpayer or identifier context, IP ownership, regulated status, statistics or lawful compliance context. Commercial providers and contact-data products are not used as authority for official reuse rights.

• Prefer the national registry, company house, gazette or official business-registration authority before any secondary source.
• Classify access as search, API, bulk download, paid extract, subscription, document workflow, data catalogue or unclear/manual access.
• Separate legal-entity data from establishment statistics, procurement suppliers, listed-company disclosures, tax identifiers and private contact data.
• Treat beneficial owners, officers, addresses, signatures, insolvency notices and sole-trader records as privacy-sensitive unless the source and law clearly support reuse.
• Hold or omit unstable source links when live QA shows 403, 429, 5xx, DNS, TLS or timeout behaviour that would create broken-link noise.

What Counts as Company Data in Slovakia?

In Slovakia, these layers should not be collapsed into one undifferentiated database. A registry result may prove legal existence, a procurement notice may prove public-sector activity, an IP record may prove brand or invention ownership, and a regulator list may prove supervision. Those are different facts with different update cycles, identifiers and reuse boundaries.

Reuse Rights and Compliance

Across jurisdictions, public-sector-information and open-data policies can support reuse of public-sector data, and high-value dataset rules increasingly treat company and company-ownership data as important public information. In practice, Slovakia's actual reuse position still depends on each source, endpoint, licence and access method.

• Cite official sources and preserve update dates where the source provides them.
• Do not imply that a derived dataset is endorsed by the registry or public authority.
• Do not mix public register data with marketing-contact permission.
• Check whether API, bulk download, paid extract and web-search access have different terms.
• Treat officers, beneficial owners and natural-person data as GDPR-sensitive where applicable.

publishable as a Slovakia deep article using RPO, ORSR, Registeruz, RPVS open data/API, statistics API, data.slovensko.sk, procurement, NBS, IP, tax, Slov-Lex, Ministry of Justice and GLEIF as clean linked sources with EU/GDPR, beneficial-owner, no-endorsement, no-single-master-file and contact-data caveats

Coverage, Access and Update Risk

The most common mistake in Slovakia company-data work is to confuse visibility with completeness. A public search screen can be authoritative for one entity lookup without being suitable for bulk ingestion. A downloadable dataset can be reusable for a defined snapshot while still excluding filings, documents, directors, inactive entities or historical changes.

• Coverage: identify whether the source covers companies, business names, branches, non-profits, sole traders, listed issuers, regulated entities or only a sector subset.
• Freshness: preserve the source update date and avoid mixing live portal results with old downloaded files without version labels.
• Identifiers: map registration numbers, tax identifiers, procurement supplier IDs, LEI records and exchange tickers as separate keys until verified.
• Language and formats: normalize local-language names, legal forms, transliteration, accents, abbreviations and address formats carefully.
• Operational access: document whether the workflow is public search, API, bulk file, paid extract, login-only service, PDF, CKAN/OData/SPARQL or manual request.

Reuse Checklist for Slovakia

Controlled Registry Workflow and Source-Risk Clearance

Slovakia passes the publication bar as an official-source and API/open-data guide, not as a claim of one unrestricted master company file. The public article links only to official or high-quality public sources that passed live QA from this node. Held routes remain documented as source-risk findings, but they are not linked as public evidence.

Claims allowed in this article

• RPO and ORSR provide the core legal-entity and commercial-register verification route for Slovak companies.
• Registeruz, RPVS open data/API, the Slovak statistics API and data.slovensko.sk add financial-statement, public-sector-partner, beneficial-owner and machine-readable context.
• UVO procurement, NBS supervised entities, the Industrial Property Office, Financial Administration, Slov-Lex, Ministry of Justice register pages and GLEIF can enrich known entities when field provenance is preserved.

Claims blocked from this article

• Do not claim one unrestricted official Slovak bulk file with every registry, financial, beneficial-owner, tax, procurement and contact field.
• Do not treat RPVS beneficial-owner or other natural-person data as a marketing-contact source.
• Do not use RPO, ORSR, Registeruz, UVO, NBS, IP, tax or legal-publication visibility as consent for email, phone or sales-prospecting outreach.

Held source-risk findings

• NBS financial-market-supervision direct page: nbs.sk – held because live QA returned 404; NBS supervised-entities search is used instead.
• Financial Administration VAT verification direct route: www.financnasprava.sk – held because live QA returned 404; the Financial Administration homepage is used as tax/VAT context instead.
• FinStat private business portal: www.finstat.sk – researched as market context but not used because official sources are strong and private portals are not needed as evidence.

Source-risk notes

• RPO boundary: RPO is the legal-entity identity anchor, but every downstream use still needs source date, access model and field provenance.
• ORSR and Registeruz boundary: commercial-register and financial-statement records are official evidence layers, not a guarantee of one consolidated free bulk file.
• RPVS boundary: public-sector-partner and beneficial-owner data can be valuable for compliance, but natural-person fields require GDPR, purpose-limitation and lawful-use review.
• Open-data boundary: data.slovensko.sk and the statistics API improve machine access, yet licence and provenance must be checked dataset by dataset.
• Contact-data boundary: public official records do not authorize marketing-contact extraction.

Resource Pack

Use this resource pack as a working map for verification, ingestion planning and source-risk review. The small source logos are decorative credibility cues only; the authority still comes from the official URL, owner, access model and reuse note.

Main Official Sources: Deep Dive

1. RPO Register of Legal Entities

Owner: official statistics / legal-entity register. Access: https://rpo.statistics.sk/.

• What it gives: Legal-entity identity, identifiers and RPO registry context.
• Reuse value: official terms; dataset-specific reuse
• Main limitation: Registry portal; endpoint and dataset terms must be checked before bulk reuse.

RPO Register of Legal Entities is a official statistics / legal-entity register source for Slovakia. Its main practical value is Legal-entity identity, identifiers and RPO registry context. Access is through https://rpo.statistics.sk/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: official terms; dataset-specific reuse. The main limitation is Registry portal; endpoint and dataset terms must be checked before bulk reuse. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

2. RPO organization record with history

Owner: official statistics / legal-entity register. Access: https://rpo.statistics.sk/new/organization/7034039/withHistory.

• What it gives: Record-level example showing history and entity fields for normalization design.
• Reuse value: official terms
• Main limitation: Example record only; not a bulk-access claim.

RPO organization record with history is a official statistics / legal-entity register source for Slovakia. Its main practical value is Record-level example showing history and entity fields for normalization design. Access is through https://rpo.statistics.sk/new/organization/7034039/withHistory, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: official terms. The main limitation is Example record only; not a bulk-access claim. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

3. ORSR Commercial Register

Owner: official registry / Ministry of Justice. Access: https://www.orsr.sk/.

• What it gives: Commercial-register verification, company filings and registry-search context.
• Reuse value: ORSR terms
• Main limitation: Search workflow, not one complete open-bulk dataset.

ORSR Commercial Register is a official registry / Ministry of Justice source for Slovakia. Its main practical value is Commercial-register verification, company filings and registry-search context. Access is through https://www.orsr.sk/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: ORSR terms. The main limitation is Search workflow, not one complete open-bulk dataset. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

4. Register of Financial Statements

Owner: official financial statements register. Access: https://www.registeruz.sk/cruz-public/?lang=en.

• What it gives: Financial statements and accounting-entity enrichment for known Slovak companies.
• Reuse value: register terms
• Main limitation: Filing layer, not a company master file.

Register of Financial Statements is a official financial statements register source for Slovakia. Its main practical value is Financial statements and accounting-entity enrichment for known Slovak companies. Access is through https://www.registeruz.sk/cruz-public/?lang=en, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: register terms. The main limitation is Filing layer, not a company master file. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

5. Slovak Statistics API help

Owner: official statistics. Access: https://data.statistics.sk/api/html/help-en.html.

• What it gives: Machine-readable statistics access and business-statistics context.
• Reuse value: statistics API terms
• Main limitation: Aggregate/statistical layer; not entity-level registry by itself.

Slovak Statistics API help is a official statistics source for Slovakia. Its main practical value is Machine-readable statistics access and business-statistics context. Access is through https://data.statistics.sk/api/html/help-en.html, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: statistics API terms. The main limitation is Aggregate/statistical layer; not entity-level registry by itself. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

6. RPVS open data

Owner: official registry / Ministry of Justice. Access: https://www.justice.gov.sk/sluzby/register-partnerov-verejneho-sektora/open-data/.

• What it gives: Compliance context for public-sector partners and beneficial-owner data.
• Reuse value: official open-data terms; GDPR and personal-data caution
• Main limitation: Sensitive natural-person data; not marketing-contact data.

RPVS open data is a official registry / Ministry of Justice source for Slovakia. Its main practical value is Compliance context for public-sector partners and beneficial-owner data. Access is through https://www.justice.gov.sk/sluzby/register-partnerov-verejneho-sektora/open-data/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: official open-data terms; GDPR and personal-data caution. The main limitation is Sensitive natural-person data; not marketing-contact data. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

7. RPVS OpenData v2 Swagger

Owner: official registry / Ministry of Justice. Access: https://rpvs.gov.sk/opendatav2/swagger/index.html.

• What it gives: Machine-readable RPVS access for public-sector partner scope.
• Reuse value: official API terms; personal-data caution
• Main limitation: API coverage is limited to RPVS scope, not all companies.

RPVS OpenData v2 Swagger is a official registry / Ministry of Justice source for Slovakia. Its main practical value is Machine-readable RPVS access for public-sector partner scope. Access is through https://rpvs.gov.sk/opendatav2/swagger/index.html, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: official API terms; personal-data caution. The main limitation is API coverage is limited to RPVS scope, not all companies. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

8. Slovakia national open-data portal

Owner: official open data. Access: https://data.gov.sk/.

• What it gives: Dataset discovery and open-data governance context.
• Reuse value: dataset-specific open-data terms
• Main limitation: Each dataset needs separate provenance and licence review.

Slovakia national open-data portal is a official open data source for Slovakia. Its main practical value is Dataset discovery and open-data governance context. Access is through https://data.gov.sk/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific open-data terms. The main limitation is Each dataset needs separate provenance and licence review. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

9. Justice Ministry datasets on data.slovensko.sk

Owner: official open data / Ministry of Justice. Access: https://data.gov.sk/dataset?organization=ministerstvo-spravodlivosti-sr.

• What it gives: Justice dataset discovery around registers and public-sector information.
• Reuse value: dataset-specific open-data terms
• Main limitation: Catalogue route, not a claim that every register field is reusable.

Justice Ministry datasets on data.slovensko.sk is a official open data / Ministry of Justice source for Slovakia. Its main practical value is Justice dataset discovery around registers and public-sector information. Access is through https://data.gov.sk/dataset?organization=ministerstvo-spravodlivosti-sr, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: dataset-specific open-data terms. The main limitation is Catalogue route, not a claim that every register field is reusable. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

10. Public Procurement Office

Owner: official procurement. Access: https://www.uvo.gov.sk/.

• What it gives: Tender, award and supplier context for Slovak companies.
• Reuse value: procurement portal terms
• Main limitation: Procurement subset only.

Public Procurement Office is a official procurement source for Slovakia. Its main practical value is Tender, award and supplier context for Slovak companies. Access is through https://www.uvo.gov.sk/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: procurement portal terms. The main limitation is Procurement subset only. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

How to Build a Slovakia Company Dataset

A defensible Slovakia company dataset should start with RPO and ORSR, then keep financial statements, public-sector-partner data, procurement, regulator, IP, tax, legal-publication and LEI layers separately sourced. Slovakia has strong official data infrastructure, but the dataset design still has to preserve access model, retrieval date, reuse note and lawful-use flags for every field.

1. RPO identity seed: use RPO for legal-entity identity, identifiers, registration context and history-oriented normalization.
2. ORSR statutory layer: add ORSR commercial-register verification for companies that need statutory, filing and register evidence.
3. Registeruz filing layer: enrich accounting entities with financial statements and document-level evidence.
4. RPVS compliance layer: add RPVS open data/API for public-sector partners and beneficial-owner context with GDPR safeguards.
5. Open-data/API layer: use data.slovensko.sk and the Slovak statistics API for machine-readable discovery and statistical context.
6. Procurement layer: add UVO public-procurement signals where supplier or tender history matters.
7. Regulator, IP, tax and legal layer: add NBS, Industrial Property Office, Financial Administration and Slov-Lex only as separately labelled enrichment.
8. LEI and commercial delivery: cross-check eligible entities with GLEIF and store source URL, retrieval date, access model, reuse note, field provenance and contact-data suppression flags.

Practical Options

Official open-data or API route

Start with RPO for legal-entity identity and identifiers, ORSR for commercial-register verification, and Registeruz for financial statements. Add RPVS open data and Swagger for public-sector partner/beneficial-owner compliance context, then use data.slovensko.sk, the statistics API, UVO procurement, NBS supervised entities, Industrial Property Office, Financial Administration, Slov-Lex, Ministry of Justice register pages and GLEIF for enrichment.

For production use, treat this route as an ingestion plan rather than a single download. Start with the official registry or data catalogue, keep raw source snapshots, record access terms, then add enrichment sources one by one with field-level provenance.

Manual verification and document route

Some countries expose important company facts through certificates, PDF filings, gazette notices, paid extracts or login-based services. Those sources can be valuable, but they should be documented as controlled workflows. Do not describe them as open APIs or bulk datasets unless the authority clearly publishes that access model.

Contact-data and marketing-list route

For sales outreach, company identity data is only the first layer. Business emails, phone numbers, contact roles, suppression logic and segmentation require a separate compliant contact-data process. That layer should be documented separately from official registry reuse.

Private reports and risk products

Private company-report providers can be useful for manual due diligence in Slovakia, but the editorial focus here is not a directory of competitors. The strategic value is understanding which official sources exist and where normalization is required.

If a user needs CRM-ready company records, the practical path is to combine official-source provenance with enrichment, deduplication, quality checks and lawful delivery controls. That is different from buying a generic lead list: the official-source layer explains what can be verified, while the commercial dataset layer explains how the records can be used operationally.

What Is Missing from Official Open Data?

• Do not claim one unrestricted official Slovak bulk file containing every useful registry, financial, beneficial-owner, tax, procurement and contact field.
• Do not treat RPO, ORSR, RPVS, Registeruz, UVO, NBS or tax visibility as marketing-contact permission.
• Do not reuse beneficial-owner or natural-person data without GDPR, lawful-use and purpose-limitation review.
• Do not rely on private Slovak business-information portals as authority for official reuse rights.
• Do not blur official company identity data with enriched commercial contact-data products.

This is why company-data products often add value even when the underlying public sources are strong: official data is frequently split across authorities, formats, languages, identifiers and access models.

Missing data should be treated explicitly in the dataset design. If an official source lacks bulk downloads, CompaniesData should not pretend that the bulk file exists; it should record the source limitation, add alternate official enrichment where lawful, and expose confidence fields so users know which attributes came from which layer.

Recommended Data Model

A practical CompaniesData-style model for Slovakia should keep source evidence and commercial-use fields separate. The core table should hold legal entity identity, status, registration identifiers, legal form, jurisdiction, registered address and source dates. Separate enrichment tables can then store procurement awards, IP assets, regulator status, listed-company signals, LEI matches, sanctions/compliance hits and statistics-sector context.

• Entity identity: legal name, normalized name, registration number, jurisdiction, legal form and lifecycle status.
• Source provenance: source URL, authority, retrieval date, access method, licence/reuse note and confidence flag.
• Event history: incorporation, amendments, filings, gazette notices, insolvency or dissolution where legally public.
• Enrichment: procurement, IP, regulator, exchange, LEI and official statistics layers with their own source dates.
• Commercial delivery: CRM-ready exports, segmentation and contact-data fields only when a separate lawful basis and suppression workflow exist.

How CompaniesData Adds Value

For Slovakia, CompaniesData's role is to turn fragmented source material into a usable business dataset: normalized company names, deduplicated entities, consistent country and activity fields, source provenance, update tracking and enrichment hooks.

• Normalize register identifiers and legal names.
• Match official company records with procurement, IP, LEI and regulator signals.
• Flag source provenance so every derived profile can be audited.
• Separate company identity from contact-data and marketing-permission layers.
• Package data for analysis, CRM enrichment and market research instead of forcing users to parse portals manually.

For Slovakia, the editorial value of CompaniesData is not claiming that every record is open or that every field can be reused without conditions. The value is the opposite: making source boundaries visible, normalizing messy records, adding explainable enrichment and delivering a dataset that users can audit instead of a black-box scrape.

Request a CompaniesData sample for Slovakia if you need a practical dataset rather than a list of source portals.

Commercial Dataset and Contact-Data Boundary

This Slovakia guide supports CompaniesData’s company-database work, but official registry, financial-statement, beneficial-owner, procurement, tax, regulator or IP visibility is not outreach permission. These sources can verify company facts and compliance context. They do not automatically authorize email lists, phone outreach, WhatsApp enrichment or sales-prospecting resale.

• Company identity layer: legal name, identifiers, legal form, RPO/ORSR source URL, retrieval date and confidence.
• Official enrichment layer: Registeruz, RPVS, UVO, NBS, Industrial Property Office, Financial Administration, Slov-Lex and LEI context with separate source dates.
• Compliance layer: GDPR, beneficial-owner sensitivity, no-endorsement language, dataset-specific licence review and held-source status.
• Contact-data layer: business emails, phones, roles, segmentation and suppression require a separate lawful workflow through CompaniesData.cloud.
• Spanish-speaking buyers: Hispanic contact-data demand should be routed to CentraldeComunicacion.es instead of third-party contact-data competitors.

Source Matrix

Source	Owner	What it gives	Reuse value	Limitations
RPO Register of Legal Entities	official statistics / legal-entity register	Legal-entity identity, identifiers and RPO registry context.	official terms; dataset-specific reuse	Registry portal; endpoint and dataset terms must be checked before bulk reuse.
RPO organization record with history	official statistics / legal-entity register	Record-level example showing history and entity fields for normalization design.	official terms	Example record only; not a bulk-access claim.
ORSR Commercial Register	official registry / Ministry of Justice	Commercial-register verification, company filings and registry-search context.	ORSR terms	Search workflow, not one complete open-bulk dataset.
Register of Financial Statements	official financial statements register	Financial statements and accounting-entity enrichment for known Slovak companies.	register terms	Filing layer, not a company master file.
Slovak Statistics API help	official statistics	Machine-readable statistics access and business-statistics context.	statistics API terms	Aggregate/statistical layer; not entity-level registry by itself.
RPVS open data	official registry / Ministry of Justice	Compliance context for public-sector partners and beneficial-owner data.	official open-data terms; GDPR and personal-data caution	Sensitive natural-person data; not marketing-contact data.
RPVS OpenData v2 Swagger	official registry / Ministry of Justice	Machine-readable RPVS access for public-sector partner scope.	official API terms; personal-data caution	API coverage is limited to RPVS scope, not all companies.
Slovakia national open-data portal	official open data	Dataset discovery and open-data governance context.	dataset-specific open-data terms	Each dataset needs separate provenance and licence review.
Justice Ministry datasets on data.slovensko.sk	official open data / Ministry of Justice	Justice dataset discovery around registers and public-sector information.	dataset-specific open-data terms	Catalogue route, not a claim that every register field is reusable.
Public Procurement Office	official procurement	Tender, award and supplier context for Slovak companies.	procurement portal terms	Procurement subset only.
NBS supervised entities	official central bank / regulator	Financial-sector regulated-entity enrichment.	NBS terms	Sector-specific and not a national company register.
Industrial Property Office of Slovakia	official IP authority	Trademark, patent and IP-owner enrichment.	industrial property office terms	IP layer only.
Financial Administration of Slovakia	official tax authority	Tax and VAT context for known entities and compliance workflows.	financial administration terms	Tax visibility is not marketing permission.
Slov-Lex legal publication portal	official legal publication	Company, public-sector, tax and disclosure law context.	Slov-Lex terms	Legal context, not current company status.
Slov-Lex legal acts	official legal publication	Primary-law context for company-data interpretation.	Slov-Lex terms	Legal-publication layer, not entity-level data.
Ministry of Justice registers	official registry / Ministry of Justice	Directory context for justice-sector registers.	Ministry of Justice terms	Directory layer, not a single data export.
Ministry of Justice commercial register service page	official registry / Ministry of Justice	Commercial-register service context and official register guidance.	Ministry of Justice terms	Service guidance, not a bulk licence.
GLEIF LEI records for Slovakia	global LEI authority	LEI cross-checks for Slovak entities with legal entity identifiers.	GLEIF open data terms	LEI coverage is not a national registry.

Slovakia's company-data workflow should start with RPO and ORSR, then add Registeruz financial statements, RPVS open data/API, statistics APIs, national open data, procurement, supervised-entity, industrial-property, tax, legal-publication and LEI layers. All public linked sources in this Slovakia draft passed live QA from this node, so Slovakia is the cleanest current Wave27 candidate for a deep publication.

FAQ

Is there a single free official bulk company database for Slovakia?

Not always. Slovakia has official company-data sources, but bulk access, API access, paid extracts and web search can be separate products. Do not assume a complete free bulk file unless the specific source proves it.

What is the best first source for Slovakia company data?

The best first source is RPO Register of Legal Entities, ORSR Commercial Register, Register of Financial Statements, Slovak statistics API, RPVS open data and API, data.slovensko.sk, Public Procurement Office, NBS supervised entities, Industrial Property Office, Financial Administration, Slov-Lex, Ministry of Justice register pages and GLEIF LEI records. It should then be combined with statistics, procurement, IP and regulator sources.

Can public company data be reused commercially?

Often yes, but only under the conditions of the specific source. Attribution, update-date preservation, no-endorsement wording and GDPR controls may apply.

Can I use registry data for cold email marketing?

No automatic conclusion follows from public registry access. Marketing requires a separate lawful basis, suppression handling and contact-data compliance review.

Why use CompaniesData instead of manually collecting Slovakia sources?

Manual collection is slow because identifiers, formats, languages and coverage differ by source. CompaniesData adds normalization, matching, deduplication, provenance and practical delivery formats.

How often should Slovakia company data be refreshed?

Refresh cadence depends on the source. Registry searches and APIs can support frequent checks, while gazettes, procurement portals, statistical releases and paid extracts may update on different schedules. A reliable dataset should store retrieval dates and source-specific update notes.

What should be audited before publishing or selling an enriched dataset?

Audit source authority, licence terms, personal-data exposure, contact-data lawful basis, field provenance, suppression rules, update dates and whether any official source prohibits automated reuse or resale.

Sources

• RPO Register of Legal Entities – official statistics / legal-entity register
• RPO organization record with history – official statistics / legal-entity register
• ORSR Commercial Register – official registry / Ministry of Justice
• Register of Financial Statements – official financial statements register
• Slovak Statistics API help – official statistics
• RPVS open data – official registry / Ministry of Justice
• RPVS OpenData v2 Swagger – official registry / Ministry of Justice
• Slovakia national open-data portal – official open data
• Justice Ministry datasets on data.slovensko.sk – official open data / Ministry of Justice
• Public Procurement Office – official procurement
• NBS supervised entities – official central bank / regulator
• Industrial Property Office of Slovakia – official IP authority
• Financial Administration of Slovakia – official tax authority
• Slov-Lex legal publication portal – official legal publication
• Slov-Lex legal acts – official legal publication
• Ministry of Justice registers – official registry / Ministry of Justice
• Ministry of Justice commercial register service page – official registry / Ministry of Justice
• GLEIF LEI records for Slovakia – global LEI authority