How this data is compiled
Every row traces to a public regulatory register or, for Switzerland and ADGM, to named public evidence. Records are fetched from the primary sources, verified against count, entity, and self-declared totals, joined company by company, adversarially re-checked before publication, and refreshed as the registers move. Records that fail verification are held back rather than published; that is why a tracker can show slightly fewer entries than its register. Exits and deregistrations stay on record.
The counting rule
Company counts and licence counts are stated separately, never conflated. One company can hold several licences through separate legal vehicles; the Licence records view lists each licence once.
Sources, regime by regime
ESMA CASP rows are per legal entity; one company can hold several.
The FCA register counts registered and formerly-registered firms separately.
VARA licences and in-principle approvals are separate lists.
MAS publishes no grant dates.
SFC lists licensed, applicant, and removed platforms, all tracked; the HKMA register holds 2 issuers from 36 applications.
JFSA self-declares its count, which the pipeline asserts on every fetch.
NYDFS splits BitLicenses and trust charters.
Switzerland is curated with per-row evidence because no filterable register exists.
ADGM is curated with per-row evidence because the FSRA register has no crypto filter.
This snapshot: July 16, 2026. Registers move weekly; for any single decision, verify against the primary source linked on the row.
Cite Meridial and link the primary registers. The registers are the authoritative record.
About
The Intelligence Hub is built and maintained by Meridial, the go-to-market intelligence and revenue infrastructure for digital asset companies. The hub is the public layer of the same system Meridial operates for clients: the intelligence that names a market, the content that builds authority in it, and the execution that converts it.
This hub is Layer 1 of the system we operate for clients. The same intelligence, pointed at your pipeline, with content and execution on top.
See how it works