🔔 Spain CNMC Numbering Assignments

One record per telephone-numbering allocation from the official CNMC bd-num.zip, with record_type preserving WHICH numbering table it came from and the original values retained verbatim — every table processed, none silently dropped.

Public, robots-honoured, keyless.

Output is one cnmc_geograficos 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: numeracionyoperadores.cnmc.es.

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

Real rows from run HwEvoaTX7C8YBWUQu 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):

numbering_table	values	raw	field_count
geograficos	["815", "00", "Madrid", "Asignado", "AVATEL MÓVIL, S.L. UNIPERSONAL",	815#00#Madrid#Asignado#AVATEL MÓVIL, S.L. UNIPERSONAL#30/04/2021	6
geograficos	["815", "01", "Madrid", "Asignado", "ORANGE ESPAGNE, S.A. UNIPERSONAL"	815#01#Madrid#Asignado#ORANGE ESPAGNE, S.A. UNIPERSONAL#08/03/2024	6
geograficos	["815", "02", "Madrid", "Asignado", "ORANGE ESPAGNE, S.A. UNIPERSONAL"	815#02#Madrid#Asignado#ORANGE ESPAGNE, S.A. UNIPERSONAL#08/03/2024	6
geograficos	["815", "03", "Madrid", "Asignado", "ORANGE ESPAGNE, S.A. UNIPERSONAL"	815#03#Madrid#Asignado#ORANGE ESPAGNE, S.A. UNIPERSONAL#08/03/2024	6
geograficos	["815", "04", "Madrid", "Asignado", "ORANGE ESPAGNE, S.A. UNIPERSONAL"	815#04#Madrid#Asignado#ORANGE ESPAGNE, S.A. UNIPERSONAL#21/07/2025	6
geograficos	["815", "05", "Madrid", "Asignado", "ORANGE ESPAGNE, S.A. UNIPERSONAL"	815#05#Madrid#Asignado#ORANGE ESPAGNE, S.A. UNIPERSONAL#21/07/2025	6
geograficos	["815", "06", "Madrid", "Asignado", "ORANGE ESPAGNE, S.A. UNIPERSONAL"	815#06#Madrid#Asignado#ORANGE ESPAGNE, S.A. UNIPERSONAL#21/07/2025	6
geograficos	["815", "07", "Madrid", "Asignado", "ORANGE ESPAGNE, S.A. UNIPERSONAL"	815#07#Madrid#Asignado#ORANGE ESPAGNE, S.A. UNIPERSONAL#21/07/2025	6

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

✅ 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. cnmc_geograficos
• numbering_table (string/null) — e.g. geograficos
• values (array/null) — e.g. ["815", "00", "Madrid", "Asignado", "AVATEL MÓVIL, S.L. UNIPERSONAL", "30/04/202
• raw (string/null) — e.g. 815#00#Madrid#Asignado#AVATEL MÓVIL, S.L. UNIPERSONAL#30/04/2021
• field_count (integer/null) — e.g. 6
• source (string/null) — e.g. spain-cnmc-numbering-assignments
• release_date (string/null) — null in every sample row
• source_url (string/null) — e.g. https://numeracionyoperadores.cnmc.es/bd-num.zip
• observed_at (string/null) — e.g. 2026-09-18T06:18:45Z
• 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, reconciliation counts, and delivered/duplicate totals.

⚙️ Sample inputs

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

{
  "maxRecords": 50
}

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

2. A smaller, narrowed run

{
  "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

{
  "maxRecords": 50000
}

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

🧾 JSON sample record

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

{
  "record_type": "cnmc_geograficos",
  "numbering_table": "geograficos",
  "values": [
    "815",
    "00",
    "Madrid",
    "Asignado",
    "AVATEL MÓVIL, S.L. UNIPERSONAL",
    "30/04/2021"
  ],
  "raw": "815#00#Madrid#Asignado#AVATEL MÓVIL, S.L. UNIPERSONAL#30/04/2021",
  "field_count": 6,
  "source": "spain-cnmc-numbering-assignments",
  "release_date": null,
  "source_url": "https://numeracionyoperadores.cnmc.es/bd-num.zip",
  "observed_at": "2026-09-18T06:18:45Z"
}

🔧 How it works

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

The official ZIP is fetched and every '#'-delimited .txt table parsed, tagged by table, values verbatim. A table set differing from the known manifest is flagged loudly; a non-ZIP shell or decode failure fails loud and charges nothing.

Source

https://numeracionyoperadores.cnmc.es/bd-num.zip

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

💰 Pricing example

Event	Free	Bronze	Silver	Gold
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:

• 8 registry records: $0.02 start + 8 × $0.02 = $0.18
• 25 registry records: $0.02 start + 25 × $0.02 = $0.52
• 100 registry records: $0.02 start + 100 × $0.02 = $2.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: 50 unique rows (0 duplicates collapsed). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by numeracionyoperadores.cnmc.es. 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 (numeracionyoperadores.cnmc.es) 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 50000). 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 numeracionyoperadores.cnmc.es. 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.

🔗 Related Actors

• Slovakia Public-Sector Partners Register — Slovakia Public-Sector Partners Register
• Spain AEMPS Medicines Registry (CIMA) — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• Spain BORME Company Acts — One structured registryrecord per record from the boe.es open-data BORME daily summary (JSON) → per-province section XML chain, logged-out. Public, l…
• UK Licensed Sponsor Register (Workers) — One structured sponsorrecord per row of the Home Office official versioned CSV of every organisation licensed to sponsor Worker and Temporary Worker…
• 🏢 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.