North Data Company & Register Extractor avatar

North Data Company & Register Extractor

Pricing

from $3.00 / 1,000 results

Go to Apify Store
North Data Company & Register Extractor

North Data Company & Register Extractor

Extract German/EU public-register (Handelsregister) data from northdata.com: company name, register number & court, address, officers, founding date, LEI, industry, and the full register/financial event feed with insolvency & liquidation events flagged. URL or company-name search.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

Farhan Febrian Nauval

Farhan Febrian Nauval

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

North Data Company & Register Scraper

Extract German / EU public commercial-register data from northdata.com: official company name, register number and court, registered address, officers, founding date, LEI, industry, and the full public-record event history — including publicly listed insolvency and liquidation events. Clean public-register data for KYC, B2B due diligence, and lead research.

This actor reads public-record data only — company-register entries exactly as they are published. See the note at the bottom.

Why use this actor

  • No account, no login, no API key — paste a company link or a company name and run.
  • Official register data: legal name, register number and registering court, registered address, founding date, LEI code, business purpose, and industry.
  • People on the record: the officers (managing directors, board members) as listed in the public register.
  • Full event history: every published register and financial event over the company's life — capital changes, mergers, role changes, annual reports — with insolvency and liquidation events flagged for quick risk screening.
  • Two ways to work: paste company-page links directly, or search by company name and let the actor find the matching companies.
  • Clean, structured output, automatic retries, runs on a schedule, exports to JSON / CSV / Excel. No scrapers or browsers to babysit.

How it works

  1. Pick a mode: paste company-page links (url), or search by company name (search).
  2. In search mode, the actor looks up each name and picks the top matching companies.
  3. For each company it reads the public register page and pulls the official details, the officers, and the full event history.
  4. Each company becomes one row in your dataset, with insolvency / liquidation events flagged.

You never manage scrapers, browsers, or blocks — just provide companies and read the results.

Input

Mode: Company URLs

{
"mode": "url",
"startUrls": [
"https://www.northdata.com/Google+Germany+GmbH,+Hamburg/HRB+86891"
],
"maxItems": 100,
"maxConcurrency": 3,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"],
"apifyProxyCountry": "DE"
}
}

Mode: Company-name search

{
"mode": "search",
"queries": ["Wirecard AG"],
"countries": "DE",
"maxResultsPerQuery": 5,
"maxItems": 100,
"maxConcurrency": 3
}
FieldModeTypeDescription
modestringurl (paste company links) or search (search by name). Default url.
startUrlsurlarray of stringsNorth Data company-page links, e.g. https://www.northdata.com/Google+Germany+GmbH,+Hamburg/HRB+86891.
queriessearcharray of stringsCompany-name searches, e.g. Wirecard AG.
countriessearchstringOptional country codes to focus the search (DE, or DE AT CH). Blank = all countries.
maxResultsPerQuerysearchintegerHow many top matches to scrape per search (default 5).
maxItemsintegerOverall cap on rows. 0 = no cap.
maxConcurrencyintegerHow many companies to process in parallel. Default 3.
proxyConfigurationobjectGerman residential proxy support, set by default.

Output

One row per company (real sample, Google Germany GmbH — event list truncated):

{
"_input": "https://www.northdata.com/Google+Germany+GmbH,+Hamburg/HRB+86891",
"_source": "S1-ldjson",
"_scrapedAt": "2026-07-09T11:09:46Z",
"url": "https://www.northdata.com/Google+Germany+GmbH,+Hamburg/HRB+86891",
"name": "Google Germany GmbH",
"headerLine": "Google Germany GmbH, Hamburg, Germany",
"isDefunct": false,
"statusFlags": null,
"registerType": "HRB",
"registerNumber": "86891",
"register": "HRB 86891",
"court": "District Court of Hamburg",
"courtEnglish": "District Court of Hamburg",
"foundingDate": "2001-04-06",
"leiCode": "529900H4SBHKV7XQXK22",
"purpose": "arranging the sale of online advertising and other products and services; in addition, all commercial, industrial or financial transactions relating to movable or immovable property that directly or indirectly serve the foregoing purpose.",
"industry": "Computing infrastructure, data processing, hosting and related activities",
"address": {
"streetAddress": "ABC-Str. 19",
"postalCode": "20354",
"city": "Hamburg",
"region": null,
"country": "DE"
},
"officers": [
{ "name": "Manicle, Paul Terrence", "givenName": "Paul Terrence", "familyName": "Manicle", "role": "Managing Director", "url": "https://www.northdata.com/Manicle,%20Paul%20Terrence,%20Baudour/zxd" },
{ "name": "Sebastian, Liana Yvonne", "givenName": "Liana Yvonne", "familyName": "Sebastian", "role": "Managing Director", "url": "https://www.northdata.com/Sebastian,%20Liana%20Yvonne,%20Cupertino/15da" }
],
"officerCount": 4,
"events": [
{ "date": "2025-11-10", "source": "Eb", "topicTypes": ["AnnualFinancialReport", "Balance", "Earnings", "Relation"], "summary": "Annual report for the year ending 31/12/2024 · Balance sheet for 31/12/2024 · Earnings statement for 31/12/2024 …", "detailUrl": "/?id=5111838758666240", "isInsolvencyRelated": false },
{ "date": "2003-04-01", "source": "Hrcdd", "topicTypes": ["Entry", "Role", "Relation", "Capital", "Headquarters", "LegalForm", "Name"], "summary": "Registration · MD (1) · Capital: €25,000 · Seat: Hamburg · Legal form: GmbH · Name: Google Germany GmbH …", "detailUrl": "/?id=4736277570650112", "isInsolvencyRelated": false }
],
"eventCount": 61,
"insolvencyEvents": [],
"hasInsolvencyEvents": false,
"pageTitle": "Google Germany GmbH, Hamburg, Germany, District Court of Hamburg HRB 86891: Network, Financial information"
}
FieldTypeDescription
namestringOfficial company name.
headerLinestringName, city, and country as shown on the page.
isDefunct / statusFlagsboolean / arrayWhether the company is closed / liquidated, and any status markers.
registerType / registerNumber / registerstringRegister category, number, and the combined register string.
court / courtEnglishstringRegistering court (native and English).
foundingDatestringFounding date (ISO).
leiCodestringLegal Entity Identifier, when present.
purposestringStated business purpose.
industrystringIndustry / activity classification.
addressobjectRegistered address (street, postal code, city, region, country).
officersarrayPeople on the register: name, given/family name, role, and their North Data link.
officerCountintegerNumber of officers listed.
eventsarrayFull published event history: date, source, topics, summary, detail link, and an insolvency flag.
eventCountintegerNumber of events.
insolvencyEventsarrayThe subset of events flagged as insolvency / liquidation related.
hasInsolvencyEventsbooleanQuick risk signal — whether any insolvency / liquidation event exists.
pageTitlestringThe page title (name, city, court, register number).

In search mode each company row also carries a searchMatchTitle field with the matched name as shown in search. On failure the actor writes a row with _error and _errorDetail rather than silently skipping.

Notes & limits

  • German residential proxy support is set by default and recommended for volume.
  • The public page exposes the public-register events themselves (registrations, capital changes, mergers, role changes, liquidations, financial publications). Full-text insolvency-register announcements are a separate paid North Data feature and are not included; this actor flags the insolvency / liquidation events that appear in the public event feed.
  • Officers and event history vary in length by company; large companies can have dozens of events.

Legality note

This actor collects public commercial-register data (Handelsregister and equivalent EU registers) exactly as published on northdata.com. Officers appear because they are recorded in the public register, and are passed through with no enrichment beyond the page. This is legitimate public-record / KYC / B2B due-diligence data, not private-data harvesting. Respect North Data's terms and applicable data-protection law for your use case.