LEI 549300OBO7DOF2KOP535 · Nashville, US-TN, US · one of 3,428,529 GLEIF LEI records on the directory
549300OBO7DOF2KOP535Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
ND93RA0007448663Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-07-13). 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.
5493000B2LD2C2A6C435 · ACTIVE · from 2018-01-075493000B2LD2C2A6C435 · ACTIVE · from 2018-01-07Verbatim 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-20.
FBNVUS42XXX · USCross-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.
2 ISINs loaded for this LEI so far in GLEIF's ISIN-to-LEI file.
US35471TBQ40 · US · 1-of-1 editionUS35471TBT88 · US · 1-of-1 editionWaiting for the first complete refresh of GLEIF's ISIN-to-LEI file. Until one finishes, links for this LEI may not be loaded yet, so an empty list is not a negative. Each ISIN doubles as a CNXT 1-of-1 edition address on the network.
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.
#://CNXTTHePeoPLe/ORG/GLEIF/549300OBO7DOF2KOP535web+usd://org-gleif-549300obo7dof2kop535 — 1-of-1 edition · universal linkweb+usd://org-gleif-549300obo7dof2kop535 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/549300OBO7DOF2KOP535 — JSONThis 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.
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.
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.