KRZ Scraper — Poland National Debtors Register (Bankruptcy & Restructuring)

Search KRZ (Krajowy Rejestr Zadłużonych), Poland's official National Debtors Register run by the Ministry of Justice. Look up a company by name, KRS (court register number), or NIP (tax ID) and get every bankruptcy, restructuring, debt-enforcement, and business-prohibition proceeding on file against it — the court or bailiff handling it, the official case number, the proceeding type, its current status, and its start/end dates. No login, no account, no API key — the actor uses the same public "guest" search the Ministry of Justice exposes on the portal itself.

KRZ is the authoritative source for whether a Polish company is or has been in financial distress. This actor turns a company name or identifier into a clean, structured list of proceeding records you can drop into a KYC/AML due-diligence workflow, a counterparty risk check, or a credit-control process — without clicking through a government portal by hand.

How to scrape KRZ data

This actor talks to the same backend API the public KRZ portal itself uses. It returns one structured record per proceeding found (a single company can have several — a bankruptcy filing, a related enforcement case, a restructuring proceeding), with the same information the portal shows — just structured and bulk-exportable via the Apify API, CSV/Excel/JSON export, or scheduled runs.

Search by company name

Enter a company name (full or partial, Polish spelling) in Company Name, e.g. Getin or

Kowalski Budownictwo

Search by KRS or NIP

Set KRS or NIP Identifier to an exact KRS (Polish court register number, e.g. 0000304735) or NIP (tax ID, e.g. 1080004850) to look up one specific company directly. This also avoids KRZ's 550-result cap on broad name searches.

Result limit

Max Results caps how many proceeding records the actor pushes per run (default 50). Since a company can have multiple proceedings, this is a cap on rows, not on companies — a narrow search that matches one company with 8 proceedings on file can still return up to 8 rows.

What data does KRZ Scraper extract?

Input parameters

Example output

{
    "companyName": "Getin Noble Bank S.A.",
    "krs": "0000304735",
    "nip": "1080004850",
    "legalForm": "Spółka akcyjna",
    "city": "Warszawa",
    "proceedingType": "postępowanie upadłościowe dla przedsiębiorcy",
    "proceedingTypeCode": "GUp-p",
    "caseNumber": "WA1M/GUp/44/2023",
    "authority": "",
    "status": "w toku",
    "startDate": "2023-07-20",
    "endDate": "",
    "folderCategory": "Postępowania upadłościowe lub wtórne upadłościowe",
    "proceedingId": "f451214a-6474-44ec-b35e-094fd6e0b635",
    "url": "https://krz.ms.gov.pl/#!/application/KRZPortalPUB/1.9/KrzRejPubGui.WyszukiwaniePodmiotow?params=JTdCJTdE&itemId=item-2&seq=0",
    "scrapedAt": "2026-08-02T09:27:42.187Z"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Common use cases

• Counterparty due-diligence — check whether a prospective supplier, customer, or partner has an active or historical bankruptcy, restructuring, or enforcement proceeding before signing a contract.
• KYC / AML pre-checks — pull official court case numbers and proceeding status for a Polish company in one pass instead of searching the government portal by hand.
• Credit control — monitor existing customers for newly opened enforcement or bankruptcy proceedings.
• Portfolio screening — batch-check a list of Polish company names or KRS numbers for debtor-register hits.

Cost estimate

Each run makes one headful browser page-load to complete KRZ's guest login handshake (needed once per run, not once per company), then plain HTTP API calls for the search and each company's proceeding detail — no browser rendering per result. A run matching 6 companies with 20 total proceedings typically makes 1 browser load + 7 API calls.

Limitations

• Poland-only. KRZ is geo-fenced — it blocks non-Polish IPs outright. The actor forces a Polish residential proxy regardless of what proxy settings are supplied; there is no way around this requirement.
• 550-result cap on broad name searches. A very generic name (e.g. a 3-letter fragment) can match over a thousand companies, but KRZ itself only returns the first 550. Use a fuller name or an exact KRS/NIP for exhaustive coverage of a specific target.
• No stable per-record deep link. KRZ's public portal is a hash-routed single-page app with no guessable permalink per company or proceeding — the url field points to the public search tool itself, not a specific record.
• Company-entity scope only. This actor searches KRZ's "non-natural-person entity" register (companies, associations, foundations) — it deliberately does not cover the sibling registers for sole traders' personal proceedings or private individuals' consumer bankruptcies, which involve personal data of natural persons.
• Some proceedings do not have an authority on file (e.g. certain court-filed bankruptcy openings list the court elsewhere in the case folder rather than in this field) — this is a genuine gap in KRZ's own data, not a scraping error.

Related scrapers

• German Insolvency Announcements Scraper — Germany's official insolvency-proceedings gazette.
• Belgisch Staatsblad Scraper — Belgian official gazette, company registrations and legal notices.
• North Data Scraper — European company data across 16 countries.
• eInforma Scraper — Spanish company register data.
• Registro Imprese Scraper — Italian company register data.

Data source and legality

This actor reads publicly available proceeding data from KRZ, the Polish Ministry of Justice's own public debtors register — the same "guest" search anyone can use on the portal without an account. It does not access any login-protected area. Use the data in line with KRZ's terms and applicable data-protection rules.