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.

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

Zuger Kantonalbank · active

{ "city": "Zug", "confidence": "authoritative", "country_code": "CH", "entity_type": "swiss_bank_master", "id": 641091, "identifiers": [ { "type": "bic", "value": "KBZGCH22XXX" }, { "type": "iid", "value": "30787" }, { "type": "sic_iid", "value": "307872" } ], "name": "Zuger Kantonalbank", "postal_code": "6301", "record_type": "bank", "source_id": "six_bank_master", "source_record_id": "sic:307872:319", "status": "active", "valid_from": "2026-08-31" }
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.