Hong Kong New Company Registrations Scraper
Pricing
from $13.40 / 1,000 company event records
Hong Kong New Company Registrations Scraper
Scrape newly registered Hong Kong companies: name, company number, incorporation date and type. One record per result. Pay per result.
Pricing
from $13.40 / 1,000 company event records
Rating
0.0
(0)
Developer
NexGen Watch
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
π Hong Kong New Company Registrations Scraper
Scrape newly registered Hong Kong companies: name, company number, incorporation date and type. Run it once and you get the current records as a dataset; put it on a schedule to keep the list current.
One structured company_event_record per new-company event from Hong Kong's Companies Registry β keyless, logged-out, official-register data via data.gov.hk.
Difference β this is the EVENTS feed, NOT company profiles. One record per weekly registry event: a newly incorporated or re-domiciled local company, a newly registered non-Hong-Kong company, or a change of name β with BOTH the English and the Traditional Chinese name, the BR number, the incorporation/registration date, and any change-of-name date. This is a different product from fleet-1's hk-companies-registry lookup, which resolves a single existing company's profile by name or number; this one streams the registry's weekly new-and-changed events and stacks them into the month.
Output is one hk_new_company_event row per result; billing is pay-per-event, the value event being one company event record (a $0.02 start fee per run, then $0.02 per company event record). Source: data.gov.hk, www.cr.gov.hk.
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 Wgi1h9SrkV9ylUr49 on build 0.1.5 (2026-09-18), the same input as the Quick start below β every value is as the source published it (emails masked, long text shortened):
| list_type | company_name_en | br_number | source_file_date | source_file_url | release_date |
|---|---|---|---|---|---|
| INCORPORATED_LOCAL | (Mia International) Hong Kong Company Limited | 81178624 | 20260907 | https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv | 20260907 |
| INCORPORATED_LOCAL | 112 HAMILTON PARTNERS Limited | 81177759 | 20260907 | https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv | 20260907 |
| INCORPORATED_LOCAL | 1PT DESIGN LIMITED | 81202530 | 20260907 | https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv | 20260907 |
| INCORPORATED_LOCAL | 28 Construction Engineering Limited | 81180035 | 20260907 | https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv | 20260907 |
| INCORPORATED_LOCAL | 2J Limited | 81174816 | 20260907 | https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv | 20260907 |
| INCORPORATED_LOCAL | 3 GOR CAFE COMPANY LIMITED | 79427166 | 20260907 | https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv | 20260907 |
| INCORPORATED_LOCAL | 3 Lions Limited | 77118878 | 20260907 | https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv | 20260907 |
| INCORPORATED_LOCAL | 360 International Trading Limited | 81196319 | 20260907 | https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv | 20260907 |
The run finished with the status message: NORMAL: 50 unique rows (0 duplicates collapsed) from 20260907. 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.hk_new_company_eventlist_type(string/null) β e.g.INCORPORATED_LOCALcompany_name_en(string/null) β e.g.(Mia International) Hong Kong Company Limitedcompany_name_zh(string/null) β e.g.(η±³δΊει)ι¦ζΈ―ζιε ¬εΈapproved_name_hk(string/null) β null in every sample rowbr_number(string/null) β e.g.81178624event_date(string/null) β e.g.07-09-2026date_of_change_of_name(string/null) β e.g.09-09-2026seq(string/null) β e.g.1source_file_date(string/null) β e.g.20260907source_file_url(string/null) β e.g.https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csvsource(string/null) β e.g.hk-new-companies-feedrelease_date(string/null) β e.g.20260907source_url(string/null) β e.g.https://data.gov.hk/en-data/api/3/action/package_show?id=hk-cr-crdata-list-newlyobserved_at(string/null) β e.g.2026-09-18T21:41:43Zlicense(string/integer/null) β e.g.Reuse per data.gov.hk terms (Hong Kong Companies Registry open data).attribution(string/integer/null) β e.g.Source: Companies Registry, Government of the Hong Kong SAR β RNC063 weekly listterminal(string/integer/null) β null in every sample rowreported_total(string/integer/null) β null in every sample rowraw_seen(string/integer/null) β null in every sample rowduplicates(string/integer/null) β null in every sample rowunique_found(string/integer/null) β null in every sample rowdelivered(string/integer/null) β null in every sample rowscope(string/integer/null) β null in every sample rownote(string/integer/null) β null in every sample row
β 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.hk_new_company_eventlist_type(string/null) β e.g.INCORPORATED_LOCALcompany_name_en(string/null) β e.g.(Mia International) Hong Kong Company Limitedcompany_name_zh(string/null) β e.g.(η±³δΊει)ι¦ζΈ―ζιε ¬εΈapproved_name_hk(string/null) β null in every sample rowbr_number(string/null) β e.g.81178624event_date(string/null) β e.g.07-09-2026date_of_change_of_name(string/null) β e.g.09-09-2026seq(string/null) β e.g.1source_file_date(string/null) β e.g.20260907source_file_url(string/null) β e.g.https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csvsource(string/null) β e.g.hk-new-companies-feedrelease_date(string/null) β e.g.20260907source_url(string/null) β e.g.https://data.gov.hk/en-data/api/3/action/package_show?id=hk-cr-crdata-list-newlyobserved_at(string/null) β e.g.2026-09-18T21:15:35Zlicense(string/integer/null) β e.g.Reuse per data.gov.hk terms (Hong Kong Companies Registry open data).attribution(string/integer/null) β e.g.Source: Companies Registry, Government of the Hong Kong SAR β RNC063 weekly listterminal(string/integer/null) β null in every sample rowreported_total(string/integer/null) β null in every sample rowraw_seen(string/integer/null) β null in every sample rowduplicates(string/integer/null) β null in every sample rowunique_found(string/integer/null) β null in every sample rowdelivered(string/integer/null) β null in every sample rowscope(string/integer/null) β null in every sample rownote(string/integer/null) β null in every sample row
What you get
One company_event_record per event, deduplicated on BR number + source-file date + list type. English and Traditional Chinese names are both preserved. A run_receipt row carries the weeks read, scope, license, attribution, and totals.
βοΈ Sample inputs
1. Quick start β the Store example (this is what the sample above came from)
{"maxRecords": 50,"weeks": 6}
The sample run charged exactly: 1 Γ $0.02 apify-actor-start + 50 Γ $0.02 company_event_record = $1.02 on the Free tier β every delivered row was billed.
2. A smaller, narrowed run
{"maxRecords": 5,"weeks": 6}
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,"weeks": 6}
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 Wgi1h9SrkV9ylUr49, exactly as it lands in the dataset (emails masked, long text shortened):
{"record_type": "hk_new_company_event","list_type": "INCORPORATED_LOCAL","company_name_en": "(Mia International) Hong Kong Company Limited","company_name_zh": "(η±³δΊει)ι¦ζΈ―ζιε ¬εΈ","approved_name_hk": null,"br_number": "81178624","event_date": "07-09-2026","date_of_change_of_name": null,"seq": "1","source_file_date": "20260907","source_file_url": "https://www.cr.gov.hk/docs/wrpt/RNC063/RNC063L_20260907.csv","source": "hk-new-companies-feed","release_date": "20260907","source_url": "https://data.gov.hk/en-data/api/3/action/package_show?id=hk-cr-crdata-list-newly-registered-companies-2526","observed_at": "2026-09-18T21:41:43Z","license": "Reuse per data.gov.hk terms (Hong Kong Companies Registry open data).","attribution": "Source: Companies Registry, Government of the Hong Kong SAR β RNC063 weekly lists via data.gov.hk."}
π§ How it works
Source. The actor reads data.gov.hk, www.cr.gov.hk β endpoints: https://data.gov.hk/en-data/api/3/action/package_show, https://www.cr.gov.hk/docs/wrpt/RNC063/. Public pages and feeds only; nothing behind a login.
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. Pacing: CRAWL_DELAY=0.0.
Charging. Each company event record is charged at the moment it is pushed (company_event_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.
π§ 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. Pacing: CRAWL_DELAY=0.0.
Charging. Each company event record is charged at the moment it is pushed (company_event_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.
How it behaves
The data.gov.hk dataset's CKAN package is read to find the weekly RNC063L (incorporated/local) and RNC063F (registered/non-HK) CSV files; the newest weeks files are fetched from the robots-permitted www.cr.gov.hk/docs/wrpt/RNC063/ path and normalized. Delivery is bounded to maxRecords.
Source
data.gov.hk dataset "List of Newly Incorporated / Registered / Re-domiciled Companiesβ¦" β www.cr.gov.hk/docs/wrpt/RNC063/RNC063{L,F}_{YYYYMMDD}.csv
Attribution
Source: Companies Registry, Government of the Hong Kong SAR β RNC063 weekly lists via data.gov.hk.
What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.
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 input you want, and pick a cadence:
- Daily β
0 7 * * *(07:00 UTC): catch changes within a day. - Weekly β
0 7 * * 1: a Monday digest.
Each run is independent; keep the same input on the schedule so the results stay comparable. 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 |
Company event record (company_event_record) | $0.02 | $0.02 | $0.02 | $0.01 |
Worked at the live Free-tier price:
- 8 company event records: $0.02 start + 8 Γ $0.02 = $0.18
- 25 company event records: $0.02 start + 25 Γ $0.02 = $0.52
- 100 company event 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) from 20260907. 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 data.gov.hk, www.cr.gov.hk. 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 (data.gov.hk, www.cr.gov.hk) 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 data.gov.hk, www.cr.gov.hk. 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 (CRAWL_DELAY=0.0) 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
- DOL H-2A Places of Employment (FY2026 Q3, quarter-to-date) β same family, different source
- DOL H-2A Labor Certifications (FY2026 Q3, quarter-to-date) β same family, different source
- DOL H-2B Labor Certifications (FY2026 Q3, quarter-to-date) β same family, different source
- Image Normalization API β Normalizes each supplied image β auto-rotate by EXIF, resize to a max dimension, convert format, compress, and strip unsafe metadata β and returns thβ¦
- IPEDS 12-Month Enrollment (EFFY2024) β same family, different source
- IPEDS Academic Libraries (AL2023) β same family, different source
- π’ About NexGenData β NexGen Watch is NexGenData's fleet of 281 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.
