Registry Time Machine

See the identifier state across time.

Resolve one supported bank or identifier record, then compare the current record with published before-and-after diffs and any source-published effective dates. Missing history stays visible as unavailable.

Inspect a targetRead API docs
Evidence boundary: this is registry and QA evidence, not live account verification, ownership proof or a prediction of future bank changes.

Inspect a source record

Use the stable source_id and record_key returned by Bank Intelligence. The lookup is bounded and read-only.

Current

Available

Askari Bank Limited · ACTIVE

{ "city": "Rawalpindi", "confidence": "authoritative", "country_code": "PK", "entity_type": "GENERAL", "id": 4151, "identifiers": [ { "type": "bic", "value": "ASCMPKKAXXX" }, { "type": "business_register_id", "value": "25364" }, { "type": "lei", "value": "254900NIUB1LTWMDVR47" } ], "name": "Askari Bank Limited", "postal_code": "46000", "record_type": "legal_entity", "region": "PK-PB", "source_id": "gleif_lei", "source_record_id": "254900NIUB1LTWMDVR47", "status": "ACTIVE", "updated_at": "2022-03-15T14:49:39.361Z" }
Previous observed

0 diffs

Published snapshot changes only. Each row carries its own snapshot ID and detected-at time.

Upcoming

0 dates

Future-validity evidence from the source, not an IBANgen forecast.

Published diffs

Before and after values are shown only when the registry published them.

2026-08-30T03:40:35.026543Z
No published snapshot diff is available for this target in the current history window.

Source-published upcoming dates

No upcoming effective date is published for this target.

Turn evidence into a repeatable test

Save this exact source/key pair to a user-scoped watchlist. When a supported diff appears, IBANgen can create a deterministic synthetic before/after migration fixture.

Watch this recordBrowse change digest