🔎 UK Gazette Insolvency Notices Scraper

Scrape UK Gazette insolvency notices: company, notice type, practitioner and date. Run it once and you get the current records as a dataset — that is the default. Turn on watch mode and a scheduled run returns only what changed since the last run (see Optional: run it on a schedule).

Insolvency notices published in The Gazette — the UK's official public record: notice code, category, the subject named in the notice, publication timestamp and the notice text, keyed on the Gazette's own notice id. Bounded by a publication-date window, because the archive holds over three million notices.

The Gazette accepts some filter parameters and silently ignores others. Measured against the source's own reported total (3,313,513 unfiltered):

filter	effect
publication date window	works — 24–25 July 2026 narrowed to 555
text_query	works — "winding up" narrowed to 1,137,436
edition	works — london narrowed to 3,020,737
notice code	ignored by the source — returns 200 and changes nothing

So notice_codes is applied by this actor after fetching, and the ignored parameter is never sent. You still get the filtering; you are not told the source did it.

Output is one notice_record row per result; billing is pay-per-event, the value event being one notice delta (a $0.02 start fee per run, then $0.05 per notice delta plus one $0.10 source check per run that reads the source). Source: www.thegazette.co.uk, www.w3.org.

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

Who buys this

Buyers usually search for UK insolvency notices or The Gazette insolvency.

• Compliance, KYC and AML teams checking UK insolvency notices.
• Legal and risk teams monitoring The Gazette insolvency for clients and counterparties.
• Journalists and researchers tracking regulatory action.

📊 Sample Output

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

subject	submitter_given_name	status	category	published	updated
NJ FOOD STREET LTD	Muhammad	published	Resolutions for Winding Up	2026-09-28T17:00:09	2026-09-28T17:00:09+01:00

The run finished with the status message: NORMAL: emitted 1 item(s)

✅ What you get

One row per record delivered by UK Gazette Insolvency Notice Watch; in watch mode a delta row carries delta_type, before, after and changed_fields. Field names come from the actor's real output; fields the source does not publish are null.

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_key (string/null) — e.g. gazette:5219777
• notice_id (string/number/integer/boolean/null) — e.g. 5219777
• subject (string/number/integer/boolean/null) — e.g. NJ FOOD STREET LTD
• submitter_given_name (string/number/integer/boolean/null) — e.g. Muhammad
• submitter_family_name (string/number/integer/boolean/null) — e.g. Nazir
• notice_code (string/number/integer/boolean/null) — e.g. 2441
• status (string/number/integer/boolean/null) — e.g. published
• category (string/number/integer/boolean/null) — e.g. Resolutions for Winding Up
• published (string/number/integer/boolean/null) — e.g. 2026-09-28T17:00:09
• updated (string/number/integer/boolean/null) — e.g. 2026-09-28T17:00:09+01:00
• notice_text (string/number/integer/boolean/null) — e.g. NJ FOOD STREET LTD (Company Number: 12112368 ) trading as NJ Food Street Ltd Reg
• source_url (string/number/integer/boolean/null) — e.g. https://www.thegazette.co.uk/notice/5219777
• scope_note (string/number/integer/boolean/null) — e.g. notice-code filtering is applied by this actor; the source ignores its own notic
• record_type (string) — e.g. notice_record
• delta_type (string/null) — null in every sample row
• before (object/array/string/number/integer/boolean/null) — null in every sample row
• after (object/array/string/number/integer/boolean/null) — null in every sample row
• changed_fields (array/object/string/null) — null in every sample row
• observed_at (string/null) — null in every sample row

✅ What you get

• record_key (string/null) — e.g. gazette:5215022
• notice_id (string/number/integer/boolean/null) — e.g. 5215022
• subject (string/number/integer/boolean/null) — e.g. CAROL ANN DIMAMBRO
• submitter_given_name (string/number/integer/boolean/null) — e.g. Jemma
• submitter_family_name (string/number/integer/boolean/null) — e.g. Raymond
• notice_code (string/number/integer/boolean/null) — e.g. 2509
• status (string/number/integer/boolean/null) — e.g. published
• category (string/number/integer/boolean/null) — e.g. Notice of Intended Dividends
• published (string/number/integer/boolean/null) — e.g. 2026-09-23T18:40:08
• updated (string/number/integer/boolean/null) — e.g. 2026-09-23T18:40:08+01:00
• notice_text (string/number/integer/boolean/null) — e.g. In the County Court at Bath No 429 of 2005 Bankruptcy order date: 17 October 200
• source_url (string/number/integer/boolean/null) — e.g. https://www.thegazette.co.uk/notice/5215022
• scope_note (string/number/integer/boolean/null) — e.g. notice-code filtering is applied by this actor; the source ignores its own notic
• record_type (string) — e.g. notice_record
• delta_type (string/null) — null in every sample row
• before (object/array/string/number/integer/boolean/null) — null in every sample row
• after (object/array/string/number/integer/boolean/null) — null in every sample row
• changed_fields (array/object/string/null) — null in every sample row
• observed_at (string/null) — null in every sample row

✅ What you get

• record_key (string/null) — e.g. gazette:5210824
• notice_id — e.g. 5210824
• subject — e.g. Gregory RUSSELL
• submitter_given_name — e.g. Jemma
• submitter_family_name — e.g. Raymond
• notice_code — e.g. 2509
• status — e.g. published
• category — e.g. Notice of Intended Dividends
• published — e.g. 2026-09-17T01:30:08
• updated — e.g. 2026-09-17T01:30:08+01:00
• notice_text — e.g. In the County Court at St Albans No 530 of 2007 Bankruptcy order date: 29 August
• source_url — e.g. https://www.thegazette.co.uk/notice/5210824
• scope_note — e.g. notice-code filtering is applied by this actor; the source ignores its own notic
• record_type (string) — e.g. notice_record
• delta_type (string/null) — null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

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

{
  "days_back": 2,
  "pages": 1,
  "page_size": 1,
  "edition": "all",
  "notice_codes": [],
  "watch_mode": false,
  "baseline_id": "default",
  "max_items": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.05 notice-delta = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
  "days_back": 2,
  "pages": 1,
  "page_size": 1,
  "edition": "all",
  "notice_codes": [],
  "watch_mode": false,
  "baseline_id": "default",
  "max_items": 5
}

Caps the run at 5 rows; same billing shape as the sample run above. edition narrows what the source is asked for.

3. Optional watch mode (changes only, for a schedule)

{
  "days_back": 2,
  "pages": 1,
  "page_size": 1,
  "edition": "all",
  "notice_codes": [],
  "watch_mode": true,
  "baseline_id": "default",
  "max_items": 10
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.05 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

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

{
  "record_key": "gazette:5219777",
  "notice_id": "5219777",
  "subject": "NJ FOOD STREET LTD",
  "submitter_given_name": "Muhammad",
  "submitter_family_name": "Nazir",
  "notice_code": "2441",
  "status": "published",
  "category": "Resolutions for Winding Up",
  "published": "2026-09-28T17:00:09",
  "updated": "2026-09-28T17:00:09+01:00",
  "notice_text": "NJ FOOD STREET LTD (Company Number: 12112368 ) trading as NJ Food Street Ltd Registered Office: 61 Blackdown Close , Basingstoke RG22 5BW Principal Trading Address: Unit 2, Buckskin Centre , Blackdown…",
  "source_url": "https://www.thegazette.co.uk/notice/5219777",
  "scope_note": "notice-code filtering is applied by this actor; the source ignores its own notice-code parameter",
  "record_type": "notice_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 0
}

🔧 How it works

Source. The actor reads www.thegazette.co.uk, www.w3.org — endpoints: http://www.w3.org/2005/Atom}, https://www.thegazette.co.uk/facets}, https://www.thegazette.co.uk/id/notice/5179755, https://www.thegazette.co.uk/insolvency/notice/data.feed. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Watch semantics. Snapshot mode (watch_mode: false) returns a preview capped at 25 records. Watch mode keys every record on a source-native id, stores a private baseline in a named key-value store, and on each later run emits one delta row per change (new / changed / removed). A blocked fetch is never diffed, so a source outage cannot show up as a mass removal.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each notice delta is charged at the moment it is pushed (notice-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

🔧 How it works

🔧 How it works

Subject vs submitter

subject is the party named in the notice. submitter_given_name and submitter_family_name are the Gazette submitting official — the same person appears across unrelated notices. They are never merged.

## Terminal states
    `NORMAL` · `SUCCEEDED-0: GENUINE_EMPTY` · `SUCCEEDED-0` (no change) · `PARTIAL` · `BLOCKED`.
    A zero with no evidence FAILS loud rather than exiting 0 quietly.

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

⏰ Optional: run it on a schedule

A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console → Schedules → Create new, add this actor with the watch-mode input above (watch_mode: true) so each run returns only the changes, and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Source check (source-check)	$0.10	$0.09	$0.08	$0.067
Notice Delta (notice-delta)	$0.05	$0.045	$0.04	$0.0335

Worked at the live Free-tier price (watch mode, one delta per change):

• 1 notice deltas: $0.02 start + $0.10 source check + 1 × $0.05 = $0.17
• 25 notice deltas: $0.02 start + $0.10 source check + 25 × $0.05 = $1.37
• 500 notice deltas: $0.02 start + $0.10 source check + 500 × $0.05 = $25.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). 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 1024 MB.

Yield on the sample run: NORMAL: emitted 1 item(s). max_items is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www.thegazette.co.uk, www.w3.org. It collects only what the source publishes to any visitor, 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 (www.thegazette.co.uk, www.w3.org) 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 (in watch mode the first run always seeds the baseline and returns zero deltas); 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 plus one source check.

Q: How many rows can one run return?
A: Up to max_items (default 500); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. 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 company registry checks actors?
A: Same output shape and billing model; this one covers www.thegazette.co.uk, www.w3.org. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 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 (max_items) 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.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

🔗 Related Actors

• UK Food Hygiene Prospect Finder — FSA Ratings — Prospecting lists of UK food businesses from the FSA's own public ratings API: rating, scores, address and authority contact per establishment
• UK Gambling Business Licence Roster Scraper — One gambling_business_record per licensed business — Account Number and Licence Account Name — the two source columns plus provenance, sold honestly…
• UK Gambling Operator Licence Check — GC Register — Check gambling operators against the official Gambling Commission public register (gamblingcommission.gov.uk/public-register)
• UK Ofsted Provider Inspection Check — A per-identity check: submit identifiers, get one official answer each. Billed per completed official resolution — a not-found, ambiguous, or unavail…
• 🏢 About NexGen Watch — NexGen Watch is a catalog of more than 300 public data 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.