#://CNXTMeMBeRx — CORE-SYSTEM ALLOWANCE UPLIFTS ACROSS CNXT.
Deliver toSet location
GLEIF LEI · Organization Record

J O HAMBRO CAPITAL MANAGEMENT LIMITED

LEI 5493003TNMOKAQQ3KJ37 · LONDON, GB-LND, GB · one of 3,428,529 GLEIF LEI records on the directory

Registry record

LEI
5493003TNMOKAQQ3KJ37
Registered name
J O HAMBRO CAPITAL MANAGEMENT LIMITED
Root domain
not published by the source
Location
LONDON, GB-LND, GB
Source registry
GLEIF Legal Entity Identifier (LEI) Golden Copy
Registry entry
View at source

Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org

GLEIF golden copy

Entity status
ACTIVE
Entity category
GENERAL
Legal form
Private Limited Company · ELF H0PO
Registration status
ISSUED
Jurisdiction
GB
Initial registration
2013-09-12T11:22:03.467Z
Next renewal
2027-07-15T00:00:00Z
Registration authority
Companies Register — Companies House · RA000585
Registry number
02176004

Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-07-12). Fields the golden copy does not publish are omitted — never guessed. Legal form and registration authority names are GLEIF's own list entries for the record's codes.

Corporate family (GLEIF Level 2)

Direct parent
PERPETUAL LIMITED 549300US8OE0UQWXPO82 · ACTIVE · from 2024-07-05
Ultimate parent
PERPETUAL LIMITED 549300US8OE0UQWXPO82 · ACTIVE · from 2024-07-05
Funds managed

Verbatim from GLEIF's Level 2 relationship and reporting-exception files (CC0). Each link is an LEI pair GLEIF publishes; names come from this directory and never create a link. No ownership share or value is stated. Complete refresh: 2026-10-19.

Certified BIC↔LEI links

Cross-registry identity (LiNx) for this LEI and BIC

Verbatim rows from GLEIF's certified BIC-to-LEI mapping file (bic-registry dataset) — a certified correspondence between this LEI and SWIFT BIC codes, not an inference.

Issued securities (ISIN)

None loaded for this LEI yet. CNXT has no proven complete refresh of GLEIF's ISIN-to-LEI file yet, so this is not a negative.

Cross-registry correspondences (indicative)

Indicative correspondences from the CNXT registry-linkage layer (SEC EDGAR / BIC / FedNow families) — asserted only where the registries' own published identifiers agree; certified BIC↔LEI rows appear in their own panel above.

CNXT addressing

CNXT address
#://CNXTTHePeoPLe/ORG/GLEIF/5493003TNMOKAQQ3KJ37
Universal link
https://centralbanks.app/u/#://CNXTTHePeoPLe/ORG/GLEIF/5493003TNMOKAQQ3KJ37
Edition address
web+usd://org-gleif-5493003tnmokaqq3kj37 — 1-of-1 edition · universal link
Settlement wallet
web+usd://org-gleif-5493003tnmokaqq3kj37 reserved — activates when the edition is minted; no holder or balance until then
Machine endpoint
GET /api/orgs/gleif/5493003TNMOKAQQ3KJ37 — JSON

This record is addressable on the CNXT network. Its web+usd:// edition address doubles as the record's settlement rail — reserved, with no holder and no balance, until the 1-of-1 edition is minted. The JSON endpoint returns the same org-level fields rendered here; person-level registry contacts are never exposed on this public tier.

Activation

AddressableEnrichedReservedMintedConnectedTransacting

Stage is derived live from real rows — directory row (Addressable), source-published domain or cross-registry links (Enriched), tokenized_entities registration (Reserved) and holder (Minted), CNXTCLOUD binding (Connected), settled transfers on the rail (Transacting). Nothing here is simulated.

Trust boundary

SourceGLEIF LEI — verbatim registry projection
OwnershipReserved — registered, no holder yet
ConnectivityNone — no runtime binding
SettlementNone — no settlement history

Organization records are represented in CNXT — not operated by the listed entities. Registry identity is verbatim from the source registry's public data; CNXT issues only the disclosed token attributes and never implies affiliation or endorsement.

Nearby records from GLEIF LEI

Back to top