Bilateral evidence profiles
Relationship studio
Compare two profiles through their documented relationships and shared records. An indirect connection is not evidence of a direct relationship.
Current declared routeNCFederal Deposit Insur...1 shortest paths / 100 common neighbors / 201 supporting edges
Comparable nodes5,478canonical nodes
Declared edges19,193auditable links
Relationship layers4kept separate
Inferred endpoint links0from path proximity
Route contractEvery line is declared. Multi-hop proximity never becomes a direct endpoint claim.Evidence standard
Bilateral query
Build an exact profile-to-profile route
3,158 profiles directly connected to Federal Deposit Insur...
105 profiles directly connected to NC
Relationship familyMeasurementMarkets, participants, industries, places, indicators, and sources
Declared route sets
Declared bilateral profile
NC Federal Deposit Insur...
Measurement / 1 hop- Shortest route
- 1declared hop
- Shortest paths
- 1deterministic routes
- Common neighbors
- 100exact intersections
- Packet edges
- 2011 cited sources
high199medium0bounded2low0
- Insurance HHI
- 3,255
- Selected-layer neighbors
- 106
- Total neighbors
- 106
- Latest year
- 2025
Connection fingerprint
Measurement106
Organization0
Enforcement0
Research0
Places99Indicators4Sources3
Open canonical profileMeasurementOrganizationEnforcementResearch
Route 01 / 1 hop
- Access date
- 2026-07-19
- Selected-layer neighbors
- 3,159
- Total neighbors
- 3,162
- Latest year
- 2026
Connection fingerprint
Measurement3159
Organization0
Enforcement0
Research3
Places3155Indicators4Publications3
Open canonical profileSupporting edge ledger
Every bridge remains an inspectable declaration
201 exact edges support the shortest paths and common-neighbor intersections in this layer.
Antitrust Radar sums positive June 30, 2025 branch deposits within each state, groups branches to the FDIC-reported top bank holding company when RSSDHCR is available and otherwise to the insured institution certificate, then calculates shares and HHI from those grouped balances.
Antitrust Radar sums positive June 30, 2025 branch deposits within each state, groups branches to the FDIC-reported top bank holding company when RSSDHCR is available and otherwise to the insured institution certificate, then calculates shares and HHI from those grouped balances.
Antitrust Radar sums positive June 30, 2025 branch deposits within each state, groups branches to the FDIC-reported top bank holding company when RSSDHCR is available and otherwise to the insured institution certificate, then calculates shares and HHI from those grouped balances.
Alamance (37001) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Alexander (37003) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Alleghany (37005) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Anson (37007) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Ashe (37009) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Avery (37011) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Beaufort (37013) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Bertie (37015) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Bladen (37017) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Brunswick (37019) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Buncombe (37021) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Burke (37023) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Cabarrus (37025) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Caldwell (37027) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Camden (37029) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Carteret (37031) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Caswell (37033) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Catawba (37035) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Chatham (37037) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Cherokee (37039) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Chowan (37041) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Clay (37043) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Cleveland (37045) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Columbus (37047) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Craven (37049) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Cumberland (37051) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Currituck (37053) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Dare (37055) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Davidson (37057) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Davie (37059) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Duplin (37061) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Durham (37063) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Edgecombe (37065) carries the exact North Carolina (NC) geography fields in its 2025 FDIC county row.
Showing 36 of 201 exact supporting edges. The complete bilateral ledger remains available in JSON and CSV.
Bilateral graph contract
A route is not a finding about its endpoints
Each hop keeps its own evidence label, confidence, source custody, and edge-specific limitation.
A bilateral atlas route preserves a sequence of declared edges for navigation and audit. A direct edge, common neighbor, or multi-hop path does not make the endpoints equivalent, establish ownership or control, assign liability, define an antitrust market, make unlike measures comparable, or show causation.
Reusable bilateral packet
Carry the exact route into analysis
JSON preserves endpoints, shortest paths, common neighbors, nodes, and edge metadata. CSV flattens the complete supporting ledger.