Czech ARES Company Registry avatar

Czech ARES Company Registry

Pricing

from $13.40 / 1,000 registry records

Go to Apify Store
Czech ARES Company Registry

Czech ARES Company Registry

One record per requested ICO — company name, legal form, DIC, registered address, NACE and last-updated date from the official register. Honest scope: one record per supplied ICO.

Pricing

from $13.40 / 1,000 registry records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

🔔 Czech ARES Company Registry

One record per requested ICO — company name, legal form, DIC, registered address, NACE and last-updated date from the official register. Honest scope: one record per supplied ICO.

One structured registry_record per record from the keyless ares.gov.cz REST economic-subjects API, logged-out. Public, logged-out, robots-honoured.

Output is one ares_company_record row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: ares.gov.cz.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Czech ARES Company Registry sample output — a table of real registry record rows (ico, company_name, legal_form, address) from run 8gD05uUanGoNSPN1t on build 0.1.6

Real rows from run 8gD05uUanGoNSPN1t on build 0.1.6 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

icocompany_namelegal_formaddressnacelast_updated
00006947Ministerstvo financí325Letenská 525/15, Malá Strana, 11800 Praha 1841102026-03-23
27074358Asseco Central Europe, a.s.121Budějovická 778/3a, Michle, 14000 Praha 455900, 68200, 47, 69200, 73120, 63, 181, 62, 74300, 800, 61, 711, 73202026-09-03
45317054Komerční banka, a.s.121Na příkopě 969/33, Staré Město, 11000 Praha 166190, 461, 70200, 711, 68320, 69200, 74, 649, 63, 641902026-09-09

The run finished with the status message: NORMAL: 3 unique rows (0 duplicates collapsed). billable=3

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_type (string) — e.g. ares_company_record
  • ico (string/null) — e.g. 00006947
  • company_name (string/null) — e.g. Ministerstvo financí
  • legal_form (string/null) — e.g. 325
  • dic (string/null) — e.g. CZ00006947
  • address (string/null) — e.g. Letenská 525/15, Malá Strana, 11800 Praha 1
  • nace (string/null) — e.g. 84110
  • last_updated (string/null) — e.g. 2026-03-23
  • primary_source (string/null) — e.g. ros
  • source (string/null) — e.g. czech-ares-company-registry
  • release_date (string/null) — null in every sample row
  • source_url (string/null) — e.g. https://ares.gov.cz/ekonomicke-subjekty-v-be/rest/ekonomicke-subjekty
  • observed_at (string/null) — e.g. 2026-09-18T06:12:18Z
  • terminal (string/integer/null) — null in every sample row
  • reported_total (string/integer/null) — null in every sample row
  • raw_seen (string/integer/null) — null in every sample row
  • duplicates (string/integer/null) — null in every sample row
  • unique_found (string/integer/null) — null in every sample row
  • delivered (string/integer/null) — null in every sample row
  • scope (string/integer/null) — null in every sample row
  • note (string/integer/null) — null in every sample row

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, and delivered/duplicate counts.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"ico": [
"00006947",
"27074358",
"45317054"
],
"maxRecords": 50
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 3 × $0.02 registry_record = $0.08 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
"ico": [
"00006947",
"27074358",
"45317054"
],
"maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
"ico": [
"00006947",
"27074358",
"45317054"
],
"maxRecords": 2000
}

Up to 2000 rows (the schema default for maxRecords) — about $40.02 on the Free tier ($0.02 start + 2000 × $0.02) if the source has that many.

🧾 JSON sample record

One real record from run 8gD05uUanGoNSPN1t, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "ares_company_record",
"ico": "00006947",
"company_name": "Ministerstvo financí",
"legal_form": "325",
"dic": "CZ00006947",
"address": "Letenská 525/15, Malá Strana, 11800 Praha 1",
"nace": "84110",
"last_updated": "2026-03-23",
"primary_source": "ros",
"source": "czech-ares-company-registry",
"release_date": null,
"source_url": "https://ares.gov.cz/ekonomicke-subjekty-v-be/rest/ekonomicke-subjekty",
"observed_at": "2026-09-18T06:12:18Z"
}

🔧 How it works

Source. The actor reads ares.gov.cz — endpoints: https://ares.gov.cz/ekonomicke-subjekty-v-be/rest/ekonomicke-subjekty. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Supply a list of ICO numbers; each is looked up via /ekonomicke-subjekty/{ico}. ICOs that do not resolve are not emitted and never billed. maxRecords caps the count. Duplicates, outages, and schema drift charge nothing.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Registry Record (registry_record)$0.02$0.02$0.02$0.01

Worked at the live Free-tier price:

  • 3 registry records: $0.02 start + 3 × $0.02 = $0.08
  • 25 registry records: $0.02 start + 25 × $0.02 = $0.52
  • 2000 registry records: $0.02 start + 2000 × $0.02 = $40.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 3 unique rows (0 duplicates collapsed). billable=3. maxRecords is a hard ceiling on what is delivered and billed, never a target.

This actor reads public, logged-out pages and feeds published by ares.gov.cz. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (ares.gov.cz) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 2000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers ares.gov.cz. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • CMS CLIA Laboratory Registry — One structured registryrecord per record from the CMS Provider of Services File - Clinical Laboratories dataset (data.cms.gov data-api, ~681,000 rows…
  • CMS Dialysis Facilities — A clean, structured roster of Medicare-certified dialysis facilities in the United States,
  • CMS Hospice Facilities — A clean, structured roster of Medicare-certified hospice facilities in the United States,
  • Estonia Company Registry (bulk) — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
  • Latvia Company Registry (bulk) — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
  • Latvia Annual-Report Financial Statements — Latvia Annual-Report Financial Statements
  • 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.