Poland KRS New Company Registrations Feed

What does Poland KRS New Company Registrations Feed do?

Get a list of Polish companies, foundations and associations that were just registered in the official KRS court register. Every row carries the KRS number, name, legal form, registered address, PKD activity code, share capital and, when the entity published them, an email address, a website, NIP and REGON. It is built for B2B sales teams, accountants, banks, insurers, KYB analysts and service providers who follow new Polish companies from their first days.

Instead of looking up companies one by one by KRS number, you pick a date window and the Actor returns everything first registered in it. You can narrow the feed by legal form, voivodeship, city, activity code, name keyword, share capital, published email and published website.

What you can use it for

• New-company prospecting: accounting, banking, insurance, office space, web design, legal and payroll providers see newly registered sp. z o.o. companies while they are still choosing suppliers.
• KYB and onboarding checks: confirm that a counterparty exists in KRS, see its registration date and share capital, and tell a company that is three days old from one that is ten years old.
• Market monitoring: count new companies per voivodeship, city or PKD sector, week after week.
• Change tracking: switch to the all-changes mode to see which existing entities filed new entries (address, board, capital, activity) in a period.

Example output

Each row is a flat JSON object. A shortened example of one result:

{
  "krs": "0001269391",
  "register": "P",
  "name": "LEARNLY SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ",
  "legalFormType": "llc",
  "registrationDate": "2026-09-29",
  "isNewRegistration": true,
  "city": "SZCZECIN",
  "voivodeship": "ZACHODNIOPOMORSKIE",
  "mainPkdCode": "85.59.B",
  "shareCapital": 5000,
  "capitalCurrency": "PLN",
  "email": "kontakt@example.pl",
  "website": "example.pl",
  "boardMembersCount": 2,
  "shareholdersCount": 2,
  "sourceUrl": "https://api-krs.ms.gov.pl/api/krs/OdpisAktualny/0001269391?rejestr=P&format=json"
}

The full field list, with a description of every column, is in the dataset schema of the Actor. Board members and shareholders are returned only as counts; the email and website are whatever the entity entered in the register.

Pricing

You pay per entity returned. Pricing depends on your Apify plan: a small fee when a run starts, then a price per result that is lower on paid plans. The Apify free plan includes monthly credit you can use to try the feed on real data. Duplicates and status rows for runs without results are never charged. Set a maximum spend in the run options and the Actor stops when it is reached.

Input

• Mode: new registrations (default) or all changes.
• Working days back or From/To date: the window. Working days skip weekends and Polish public holidays, because registry courts do not register on those days; the default of 2 means today and the previous working day, so a run on a Sunday covers Thursday to Sunday. Explicit dates can span up to 31 days, a limit of this Actor; the KRS API serves bulletins from January 2020 onwards.
• Registers: P for companies and other entrepreneurs, S for associations and foundations, or both.
• Scan depth: complete (default) or recent numbers only.
• Filters: legal forms, voivodeships, cities, PKD prefixes (main activity or any), name keywords, minimum and maximum share capital, only with email, only with website.
• Only new since last run: for schedules, so each entity is returned once per settings combination.
• Maximum companies: the run stops at this number.

FAQ

How does it work?

The Actor reads the official public API of the Polish Ministry of Justice. It downloads the daily KRS bulletin (the list of KRS numbers with an entry on a given day), then reads the current extract of each entity and keeps those whose registration date falls in your window. It does not log in anywhere and does not scrape web pages.

Does it find every new company?

A new registration gets a KRS number close to the newest ones, so in new-registrations mode the complete depth reads the entities whose number is within the newest 100,000 numbers of the window's bulletins; the rest of the bulletin is almost entirely changes to long-registered entities. Measured on 2026-09-30 against full reads of the bulletins: on 2026-09-29 all 267 registrations (248 in register P, 19 in register S) were within the newest 16,431 numbers; on 2026-09-25, 308 of 309 were within the newest 9,776, and the one missed entity had a number more than 500,000 below the newest and 21 register entries. The complete depth therefore returned 575 of the 576 registrations of those two days. The recent depth reads only the newest 3,000 numbers and returned 261 of the 267 registrations of 2026-09-29. In all-changes mode the complete depth reads every entity in the bulletin.

How long does a run take and what are the limits?

Measured locally on 2026-09-30: one full weekday (2026-09-29, registers P and S) meant 1,158 lookups and took 95 seconds; the recent depth took 41 seconds. A window of the whole of September 2026 means about 13,300 lookups in new-registrations mode, roughly 18 minutes at that speed, and about 62,500 lookups in all-changes mode. The API answers more slowly at busy hours. This Actor accepts windows of up to 31 days and up to 15 working days back.

How often should I run it?

Once a day is enough. Schedule the Actor with "Only new since last run" enabled and 2 working days back: the windows of consecutive runs overlap, and every entity is delivered once. The remembered entities are stored per combination of mode, registers, scan depth and filters in a key-value store named krs-feed-state in your account (45 days, 35 in all-changes mode). Only entities actually returned to you are remembered, so two schedules with different filters, or a manual test run with other settings, do not take results from each other. Numbers whose registration date is already known to be outside the window are not read again, which makes daily runs faster.

What personal data does the output contain?

KRS is a public register and the Actor uses its official API. The register itself masks the names and PESEL numbers of board members and shareholders, and the Actor returns only their counts. The email and website fields are copied as the entity published them; for small companies an email address can contain the name of a natural person. How you use the data, including for contacting companies, is your decision and your responsibility under the rules that apply to you.

Why is REGON or NIP sometimes empty?

Numbers are assigned after the court entry. For entities registered in the last hours or days the register may not yet show them. Email and website are optional in KRS, so only part of the entities publish them; the run summary tells you for how many.

What happens when the register changes?

The run summary reports in how many extracts the registration date and the fields used by your filters were present. If the API stops returning bulletins, the registration date drops below 90% of extracts, a field your filter relies on disappears, or more than 20% of lookups fail, the run fails with an explicit message instead of returning an empty dataset that looks like success.

Related Actors

Look up one company by KRS number, NIP or REGON with a lookup Actor when you already know the entity. Use this feed when you want to discover entities you do not know yet.