crhk_address_history
Registered-office timeline for Hong Kong companies
Download a file
CSV and Parquet. Filtered exports.
See pricingQuery with SQL
DBeaver, DuckDB, MotherDuck, or HTTPS. Sub-second latency.
Open connection detailsConnect to AI
MCP for Claude Desktop, Cursor, ChatGPT, Goose. 1-line install.
See setupA registered-office address timeline for Hong Kong companies. Read it as a history of where a company has been on record, not yet as a current-address lookup. Three of its arms are frozen legacy captures that stopped on 2024-04-18, when the modern e-services API withdrew the address field; a live arm reading the Companies Registry's open-data portal resumed observation on 2026-09-03 and is still filling in. RECENCY THEREFORE VARIES BY COMPANY — read last_observed_at per row rather than assuming one as-of date for the dataset. Where the live sweep has not yet reached a company, its most recent address may have been superseded by a move we have not seen. Use it to reconstruct where a company was and when it moved; verify against the registry before relying on it for where a company is today. One row per company per distinct registered-office address observed on record; effective_from/effective_to are the registry's own dates where given (else null) and reach back to 1902, first/last_observed_at are our observation bounds. Coverage: 68.4% of active (non-dissolved) Hong Kong companies have at least one address on record here.
Evaluate it in full below: the evidence and a working sample are open to everyone. Buy or subscribe to unlock the complete dataset — your account is created automatically at checkout.
The evidence
Partly refreshed, and still filling in. Three arms are frozen legacy captures that stopped on 2024-04-18; a live arm resumed observation on 2026-09-03. Recency varies by company — read last_observed_at per row. A company the live sweep has not yet reached may have moved since we last saw it.
Rows over time
monthSchema & column quality (9 columns)
Scroll table sideways to see more columns →
| Column | Type | Description | Populated | Distinct |
|---|---|---|---|---|
| business_registration_number | String | The company's 8-digit Hong Kong Business Registration Number — the join key to every other CRHK dataset (companies, documents, name history) | — | — |
| address | String | Registered-office address observed on record | — | — |
| effective_from | Nullable(Date32) | Registry effective-from date for this address, where the source provides it (Plan A; null otherwise) | — | — |
| effective_to | Nullable(Date32) | Registry effective-to date for this address. NULL means the address was still open at our most recent observation of that company — it does NOT mean the address is open today. | — | — |
| first_observed_at | DateTime64(3, 'UTC') | Timestamp we first witnessed this address on record | — | — |
| last_observed_at | DateTime64(3, 'UTC') | Timestamp we most recently witnessed this address on record | — | — |
| observation_count | Int64 | Number of observations witnessing this (company, address) tuple | — | — |
| is_current | Bool | True if this is the most-recent address we OBSERVED for the company. NOT a current-address flag: how much it is worth depends on when we last looked, which last_observed_at gives per row. Sampled against the Companies Registry's live open-data API on 2026-09-02 — before the live arm landed — 11 of 52 is_current addresses (21.2%) had been superseded by a relocation we had not seen. Read it as 'last known', and re-verify against the registry before relying on it. | — | — |
| id | String | Stable unique identifier for this row — the last column of every export. Use it to deduplicate, to key an incremental load, or to reference one specific row. It is additive: the entity and join keys you already use (race_id, horse_id, and the like) are unchanged. | — | — |
500 registered-office address records, full schema. Recency varies by company — the live arm is still filling in, so read last_observed_at per row rather than assuming a single as-of date.
Choose your access
A Pass gives you freshness within a rolling window. The Full Archive gives you the full history we hold for the dataset, frozen at purchase. They solve different problems, and they work together.
Pass subscription
HK Corporate Diligence — Compliance Pass
Continuously updated, with API access.
View full package →- Access window
- Full history (no window)
- Updates
- Continuous, within hours of the source
- Delivery
- API, SQL and downloads
- Exports
- 1,000,000 rows/month included
Included Datasets
Get notified when this dataset is updated.
Questions about this data?
Our data experts are ready to help clarify any aspects of this dataset.
Contact Our Team