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

Hungary is a strong official-search and filings jurisdiction, but it should not be sold as a simple open-bulk company database. The best evidence starts with e-Cegjegyzek, e-Beszamolo and the EU e-Justice description of the Hungarian business register. Those sources support public company-information and corporate-document workflows. They also show the key boundary: core data can be free to the stated extent, while further content, copies, extracts, documents and sensitive person fields can be paid or controlled.

This refresh replaces the older Hungary page, which was useful as a source list but below the current CompaniesData depth bar. The new article adds editorial methodology, coverage and update-risk analysis, a reuse checklist, source-by-source deep dives, practical manual/API/bulk guidance, held-source findings, a recommended data model, CompaniesData normalization value and post-publication crawl/indexing controls.

The practical answer is conservative. Hungary is commercially useful because the official public search, accounts portal, statistics, open-data catalogue, procurement, IP, financial-regulator, competition and LEI layers can be joined into a high-quality business dataset. The article does not claim that Hungary offers a complete free official company-register bulk download or unrestricted API.

Key Takeaways

• Best official starting point: e-Cegjegyzek free company information, supported by EU e-Justice business-register context.
• Best filings route: e-Beszamolo, the Ministry of Justice electronic reports portal for published accounts and related filing workflows.
• Best enrichment stack: Kozadatportal, KSH, the Public Procurement Authority, EKR, HIPO, MNB, GVH and GLEIF.
• Main limitation: clean evidence supports public search and filings, not a complete free official bulk/API claim.
• Held this cycle: the government Company Information Service portal had local TLS verification failures, the old HIPO database subroute was unstable, paid extracts/documents and natural-person fields remain controlled.
• Contact-data caution: Hungarian public company visibility is not permission for email, phone, lead-list or sales-prospecting contact enrichment.

Editorial Methodology

The CompaniesData method starts with official, primary sources. For Hungary, the editorial order is e-Cegjegyzek and e-Beszamolo first, EU e-Justice for English-language official register context, then national open-data, KSH statistics, procurement, intellectual-property, financial-regulator, competition-authority and LEI sources as enrichment layers. Private data brokers are not used as evidence for official reuse rights.

Each final linked source was checked from this environment on 2026-06-14 with browser-like, Googlebot-like and Bingbot-like profiles. A source had to return real content, avoid hard 404/410 errors, avoid obvious challenge pages and pass expected semantic checks or same-domain final URL checks. Sources that are official but unstable, paid, person-sensitive or not clean enough were moved into held notes instead of being used as clean linked evidence.

Source logos in the matrix and Resource Pack are decorative favicon cues loaded through a stable proxy. They are not evidence. The evidence is the official URL, source owner, access model, reuse note and limitation recorded in the source-live artifact.

Coverage, Access and Update-Risk Analysis

Registry coverage: Hungary’s business register contains data on registered companies and corporate documents. EU e-Justice describes free online access to company data at the stated extent, including registration number, company name, registered office, activities, issued share capital, tax number and certain proceeding or disqualification indicators. It also explains that further content and document copies can be fee-controlled.

Search and filings access: e-Cegjegyzek is the clean public company-information route. e-Beszamolo is the clean filings and accounts route. These are excellent for manual verification, record checks and filings discovery, but they do not by themselves prove an unrestricted machine-readable bulk feed.

Open-data and statistics context: Kozadatportal and KSH help with public-data discovery, aggregate business statistics, business-unit methodology and market sizing. They should support coverage analysis and quality checks, not replace the legal company-register core.

Procurement, IP, regulator and LEI layers: the Public Procurement Authority and EKR support supplier-event enrichment. HIPO supports IP context. MNB identifies financial-sector participants and can include persons as well as organisations. GVH supports competition-law event context. GLEIF supports LEI-bearing entities. These layers are partial and must be matched back to the company core with confidence scores.

Update risk: company-register data, filings, reports, open-data catalogue metadata, statistics, procurement notices, IP rights, regulator records, competition decisions and LEI records update on different schedules. A trustworthy Hungary dataset should store source-specific access dates and observed update dates rather than a single generic freshness stamp.

Reuse Checklist

• Authority check: record whether each field came from e-Cegjegyzek, e-Beszamolo, EU e-Justice, Kozadatportal, KSH, procurement, HIPO, MNB, GVH or GLEIF.
• Access check: separate free public search, paid extracts, corporate documents, filings, open-data catalogue metadata, statistics, procurement notices, regulator records and LEI API data.
• Field-scope check: do not treat officers, representatives, shareholders, supervisory-board members, natural-person regulator entries or document-level personal data as ordinary company attributes.
• Fee and product check: preserve fee/product notes for further content, copies, extracts and corporate documents.
• Licence check: preserve source terms, access dates, update dates, attribution and no-endorsement wording.
• Crawler check: if a route returns TLS errors, challenge HTML, bot-profile blocks or unstable redirects, hold it until retested.
• Marketing check: public company search, filings, procurement, regulator, IP or LEI visibility is not consent for cold email, phone calls or sales-prospecting exports.

Practical Manual, API and Bulk Options

Manual verification: start with e-Cegjegyzek for company searches by name, registration number or tax number. Store the access date, search route, field scope and any mismatch notes. Manual search is a strong QA layer, but it should not be labelled as unrestricted bulk access.

Filings and reports: use e-Beszamolo for published reports and balances. Document-level ingestion should store file route, report year, filing date, source terms, personal-data flags and retention policy.

Open-data discovery: use Kozadatportal to discover public datasets and KSH data routes. Each dataset still needs publisher, licence, update, format and field-level checks before reuse.

Statistics: use KSH business-unit and methodology pages for aggregate counts, business-demography context and statistical business-register interpretation. Keep aggregate statistics outside the entity core.

Procurement enrichment: use the Public Procurement Authority and EKR for supplier events, public tenders, contracting authority context and procurement history. Procurement coverage is event-based and should not be treated as all-company coverage.

Regulator, IP, competition and LEI enrichment: use HIPO, MNB, GVH and GLEIF as partial layers. Each match should carry confidence, source owner, event or right type and a limitation note.

Source-by-Source Deep Dives

1. EU e-Justice Hungary business register overview

Owner: European e-Justice Portal / Hungary. Source type: official EU justice register context. Access model: public explanatory route for Hungarian business-register access, free core fields and paid extras. Reuse note: context source; Hungarian register, document and fee rules still control operational reuse

Business use: sets the official boundary: company data and corporate documents are electronic, core data are free, additional content can be charged In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: translation/context page, not a machine-readable bulk endpoint and not a current API contract This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

2. e-Cegjegyzek free company information

Owner: Hungarian Ministry of Justice company information service. Source type: official company-register search. Access model: free public company-information search and register route. Reuse note: official public search; bulk/API, paid extracts and document reuse need separate terms review

Business use: primary record-level verification, company name, registration number, tax number and status checks In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: public search is not proof of unrestricted free bulk access This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

3. e-Beszamolo electronic reports portal

Owner: Hungarian Ministry of Justice company information service. Source type: official financial-report and filing portal. Access model: public portal for searching and publishing annual reports, balances and related filings. Reuse note: portal terms and accounting/document rules apply; use document-level provenance and retention controls

Business use: financial-report discovery, accounts/search workflow, filing-event enrichment and document-route planning In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: document access is not the same as an all-fields company master database This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

4. National Open Data Portal

Owner: Hungarian national open-data portal. Source type: official national open-data catalogue. Access model: public data catalogue and dataset discovery route. Reuse note: dataset-specific licences and metadata apply; catalogue presence is not a blanket company-register licence

Business use: open-data discovery, KSH data access context, public-data metadata review and data-policy orientation In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: not a company register by itself; every dataset needs publisher, field and licence review This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

5. KSH business units and non-profit organisations

Owner: Hungarian Central Statistical Office. Source type: official statistics theme page. Access model: statistics and aggregate business-unit context. Reuse note: statistics reuse and source-reference terms apply; use aggregate data separately from entity facts

Business use: business-demography context, market sizing and statistical validation of entity coverage In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: aggregate statistics do not replace legal company records This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

6. KSH business-register methodology

Owner: Hungarian Central Statistical Office. Source type: official statistical methodology. Access model: methodology for registered business units, business demography and statistical business-register concepts. Reuse note: methodology source; do not treat statistical definitions as company-register reuse permission

Business use: defines statistical business-unit coverage, active-enterprise counts and aggregate QA concepts In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: methodology supports interpretation, not commercial reuse of register records This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

7. Public Procurement Authority

Owner: Hungarian Public Procurement Authority. Source type: official procurement authority. Access model: public procurement authority and procurement-context route. Reuse note: procurement notice and authority-source terms apply; use event provenance

Business use: supplier-event enrichment, public-sector demand context and tender-risk interpretation In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: procurement covers events and suppliers, not the whole company population This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

8. EKR electronic public procurement system

Owner: Electronic Public Procurement System of Hungary. Source type: official procurement portal. Access model: public procurement portal for Hungarian tender and contracting workflows. Reuse note: portal and notice-specific terms apply; cite source and event dates

Business use: supplier matching, tender tracking, contracting authority mapping and public-procurement monitoring In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: interface and language constraints mean it should be treated as enrichment, not bulk company coverage This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

9. Hungarian Intellectual Property Office

Owner: Hungarian Intellectual Property Office. Source type: official intellectual-property authority. Access model: IP authority route for patents, trademarks, designs and rights context. Reuse note: IP records and right-owner data need source-specific terms and match confidence

Business use: IP-owner enrichment, rights context and innovation-heavy company signals In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: IP ownership is partial and does not prove company operating status This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

10. MNB market participants search

Owner: Magyar Nemzeti Bank. Source type: official financial-regulator register. Access model: public register of financial service providers, licensed or supervised entities and persons. Reuse note: regulator-source terms apply; store regulatory category, authority and access date separately

Business use: financial-sector screening, regulated-entity enrichment and compliance segmentation In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: sector-specific and can include persons as well as organisations; not a general company register This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

11. Hungarian Competition Authority

Owner: Hungarian Competition Authority. Source type: official competition authority. Access model: competition, merger and consumer/market case context. Reuse note: case and authority-context source; decision reuse needs case-specific provenance

Business use: competition-law event enrichment, market-risk context and due-diligence signals In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: case-driven and not a register of all companies This source is linked as an enrichment or context layer, so terms, field scope and automated reuse must be checked before ingestion. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

12. GLEIF LEI records for Hungary

Owner: GLEIF. Source type: global legal-entity identifier data. Access model: public JSON API for LEI-bearing Hungarian entities. Reuse note: GLEIF API terms and attribution apply; use as enrichment and identifier cross-check only

Business use: LEI crosswalk, financial-entity matching, standardized entity status and registration authority metadata In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version, privacy flag and confidence before it is joined to another Hungarian source.

Limitations: partial coverage limited to entities that have LEIs This source cleared the current linked-source publication gate. Do not stretch it into contact-data permission, beneficial ownership, personal-data reuse, credit scoring, certified-document or complete-market coverage claims.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
EU e-Justice Hungary business register overview	European e-Justice Portal / Hungary	public explanatory route for Hungarian business-register access, free core fields and paid extras	context source; Hungarian register, document and fee rules still control operational reuse	Clean public source. translation/context page, not a machine-readable bulk endpoint and not a current API contract
e-Cegjegyzek free company information	Hungarian Ministry of Justice company information service	free public company-information search and register route	official public search; bulk/API, paid extracts and document reuse need separate terms review	Clean public source. public search is not proof of unrestricted free bulk access
e-Beszamolo electronic reports portal	Hungarian Ministry of Justice company information service	public portal for searching and publishing annual reports, balances and related filings	portal terms and accounting/document rules apply; use document-level provenance and retention controls	Clean public source. document access is not the same as an all-fields company master database
National Open Data Portal	Hungarian national open-data portal	public data catalogue and dataset discovery route	dataset-specific licences and metadata apply; catalogue presence is not a blanket company-register licence	Conditional context. not a company register by itself; every dataset needs publisher, field and licence review
KSH business units and non-profit organisations	Hungarian Central Statistical Office	statistics and aggregate business-unit context	statistics reuse and source-reference terms apply; use aggregate data separately from entity facts	Conditional context. aggregate statistics do not replace legal company records
KSH business-register methodology	Hungarian Central Statistical Office	methodology for registered business units, business demography and statistical business-register concepts	methodology source; do not treat statistical definitions as company-register reuse permission	Conditional context. methodology supports interpretation, not commercial reuse of register records
Public Procurement Authority	Hungarian Public Procurement Authority	public procurement authority and procurement-context route	procurement notice and authority-source terms apply; use event provenance	Conditional context. procurement covers events and suppliers, not the whole company population
EKR electronic public procurement system	Electronic Public Procurement System of Hungary	public procurement portal for Hungarian tender and contracting workflows	portal and notice-specific terms apply; cite source and event dates	Conditional context. interface and language constraints mean it should be treated as enrichment, not bulk company coverage
Hungarian Intellectual Property Office	Hungarian Intellectual Property Office	IP authority route for patents, trademarks, designs and rights context	IP records and right-owner data need source-specific terms and match confidence	Conditional context. IP ownership is partial and does not prove company operating status
MNB market participants search	Magyar Nemzeti Bank	public register of financial service providers, licensed or supervised entities and persons	regulator-source terms apply; store regulatory category, authority and access date separately	Conditional context. sector-specific and can include persons as well as organisations; not a general company register
Hungarian Competition Authority	Hungarian Competition Authority	competition, merger and consumer/market case context	case and authority-context source; decision reuse needs case-specific provenance	Conditional context. case-driven and not a register of all companies
GLEIF LEI records for Hungary	GLEIF	public JSON API for LEI-bearing Hungarian entities	GLEIF API terms and attribution apply; use as enrichment and identifier cross-check only	Clean public source. partial coverage limited to entities that have LEIs

Resource Pack

Missing-Data Gaps

Hungary’s main gap is the lack of clean evidence for a complete free official company-register bulk/API. The official source stack is strong for search, filings and enrichment, but a serious article must separate public search from bulk reuse, paid documents from open data, and person fields from company identity.

The government Company Information Service portal is official context, but local TLS certificate verification failed in this cycle. It remains held from the clean linked matrix. The old HIPO database subroute also behaved inconsistently for bot profiles, so the clean HIPO homepage is used for IP authority context while database-specific claims stay held.

Natural-person fields are also a gap. EU e-Justice describes ownership, legal representatives, powers of representation and supervisory-board membership among data that can appear in company information. Those fields may involve natural persons and need GDPR, minimisation, retention and suppression controls before commercial reuse.

Recommended Data Model

• Entity core: registration number, legal name, normalized name, tax number, legal form, status, registered office, country, source URL, access date and confidence.
• Register search layer: e-Cegjegyzek route, query type, viewed date, current/invalid field flag, free-search note and reviewer confidence.
• Filings layer: e-Beszamolo report route, report year, document type, publication date, file checksum, fee/product note and personal-data flag.
• Open-data/statistics layer: Kozadatportal dataset metadata, KSH indicator, period, geography, sector, source table and non-entity warning.
• Procurement layer: notice ID, contracting authority, supplier, procedure type, award or opportunity event, date and match confidence.
• IP and regulator layer: HIPO right or authority context, MNB category, GVH event, source URL, event date and limitation.
• LEI layer: LEI, GLEIF legal name, entity status, registration authority reference, address data and match confidence.
• Privacy controls: natural-person field flag, paid-document flag, contact-data blocked flag, suppression marker and lawful-use note.

How CompaniesData Adds Value

CompaniesData.cloud adds value by turning Hungary’s fragmented official stack into a normalized, auditable dataset. The work is not just linking to portals. It is mapping company identifiers, normalizing legal names, separating free search from filings and paid products, joining procurement, IP, regulator, competition and LEI layers conservatively, and preserving source provenance for every derived field.

For commercial teams, this supports KYB, CRM enrichment, public-sector sales research, supplier discovery, financial-sector screening and market analysis. For compliance teams, it keeps authority, source URL, access date, fee/product notes, field scope, update cadence, privacy flags and held-source risks visible. For data teams, it avoids mixing free search, paid documents, statistics, procurement events, person fields and contact-data workflows into one untraceable table.

For English and international workflows, request a CompaniesData sample for Hungary if you need a practical dataset rather than a list of portals. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the preferred owned property. Do not treat Hungarian public-source visibility as permission for direct email, phone or lead-list outreach.

Held Sources and Source-Risk Notes

The following routes were researched but are not treated as clean linked publication evidence in this cycle.

• Company Information Service government portal: official ministry context, but local TLS certificate verification failed for browser, Googlebot and Bingbot profiles; use e-Cegjegyzek, e-Beszamolo and EU e-Justice as clean evidence.
• HIPO IP database subroute: the old HIPO database route redirected or reset bot-profile connections; use the clean HIPO authority homepage as IP context and retest the database route later.
• Paid corporate documents and certified extracts: official context states that further content and copies can be charged; do not frame paid documents as unrestricted open bulk data.
• Officers, shareholders, representation and natural-person fields: these fields can involve natural persons and require GDPR, minimisation, retention and lawful-use review before commercial reuse.
• Private contact-data and outreach lists: registry, accounts, procurement, regulator, IP and LEI visibility is not consent for email, phone, lead-list or sales-prospecting contact enrichment.

FAQ

What is the best official source for Hungary company data?

Start with e-Cegjegyzek for public company-information search, then use e-Beszamolo for reports and filings. EU e-Justice provides useful English-language context for the Hungarian business register.

Does Hungary provide a complete free official bulk company database?

The clean evidence in this cycle does not support that claim. Hungary has strong public search and filings routes, but bulk/API access, paid extracts, documents and person fields need separate source review.

Are Hungarian company reports available online?

Yes. e-Beszamolo is the official electronic reports portal for published reports and balances. Report/document use should preserve document provenance, filing date, terms and privacy flags.

Can KSH data replace company-register records?

No. KSH is valuable for aggregate business statistics and methodology, but it is not a legal company master record source.

Can procurement data be used as a company database?

No. Procurement data is useful for supplier and tender-event enrichment, but it covers public-procurement activity rather than all Hungarian companies.

Can public Hungary company data be used for cold email marketing?

No automatic permission follows from public registry access. Emails, phone numbers, lead lists and outreach segmentation require separate lawful-basis, suppression and contact-data compliance controls.

Why use CompaniesData for Hungary?

Hungary has strong official sources, but useful commercial data still requires normalization, source provenance, free-search versus paid-document separation, enrichment matching and privacy controls. CompaniesData packages those layers into a practical dataset.

Official Sources

• EU e-Justice Hungary business register overview – European e-Justice Portal / Hungary
• e-Cegjegyzek free company information – Hungarian Ministry of Justice company information service
• e-Beszamolo electronic reports portal – Hungarian Ministry of Justice company information service
• National Open Data Portal – Hungarian national open-data portal
• KSH business units and non-profit organisations – Hungarian Central Statistical Office
• KSH business-register methodology – Hungarian Central Statistical Office
• Public Procurement Authority – Hungarian Public Procurement Authority
• EKR electronic public procurement system – Electronic Public Procurement System of Hungary
• Hungarian Intellectual Property Office – Hungarian Intellectual Property Office
• MNB market participants search – Magyar Nemzeti Bank
• Hungarian Competition Authority – Hungarian Competition Authority
• GLEIF LEI records for Hungary – GLEIF