US Bank Locations — Branch & Bank Directory

The retail footprint of American banking, kept one door at a time. This is a commercial directory that publishes a structured record for every bank in the United States and, beneath it, a record for every branch: thousands of institutions, tens of thousands of branch pages, with JPMorgan Chase alone accounting for 5,360 offices and Wells Fargo 4,190.

Each bank page aggregates the registry facts and the money: established date, charter class, FDIC insurance date and specialization notes, then total assets, total deposits, US deposits, equity capital, net income and ROA/ROE. The branch list filters by state — the Zions Bancorporation page resolves to 412 offices across 11 states, each with its own per-state count.

Around the core sit three rings worth having: state directories spanning all 50 states plus DC, ten national ranking tables (branches, total assets, deposits, employees, net income, liabilities, equity capital, derivatives, ROA, ROE), and ABA routing-number records that flag FedACH and Fedwire participation alongside each number's registered name.

Datadory hands over the full sweep as a maintained feed: Get a sample of this dataset and we will return branch rows shaped exactly like the dictionary below, cut to the states or metros you name.

One screen, three row shapes — exactly as they arrive:

# Branch row
name            : Zions Bancorporation, N.A., 21ST SOUTH BRANCH
office_type     : Full Service Brick and Mortar Office
address         : 910 W 21st S, Salt Lake City, UT 84119
phone           : 801-974-8800
branch_deposit  : $141,077,000
fdic_cert       : #2270
established     : 11/19/1963

# Ranking row — banks by number of branches
1   JPMorgan Chase Bank     5,360
2   Wells Fargo Bank        4,190
20  Zions Bancorporation      413

# Routing row
routing_number  : 124000054
process_fedach  : Y
process_fedwire : Y
location        : Midvale, UT
registered_name : Zions Bancorporation, Na Dba Zions B

The branch row answers what regulator summaries cannot: $141 million of deposits sit behind one suburban Salt Lake City counter that opened in 1963. Group branch_deposit by county and deposit market share becomes a computed column rather than a consulting engagement; filter established and the age profile of any rival's network falls out of the sort. Join on fdic_cert and every row snaps onto regulator registries. The same shape holds whether rows land as structured payloads, flat files, or a table in your warehouse.

Thirteen spine fields, definitions verified against live records — the keys and measures that make a directory navigable instead of a wall of address strings. The complete dictionary follows in the table below.

Additional fields on request: net income with ROA and ROE including their quarterly variants, FDIC insurance date, institution specialization and concentration notes, the US-deposit split inside total deposits, client reviews carried on branch pages, and the deeper cuts of the ten ranking tables. Softer columns get confirmed against live records when we prepare your sample — which is also where column naming gets locked down for your pipeline.

Three chips summarize the footprint:

• Geography: United States, all fifty states plus DC, organized through state and city hierarchies — so a branch roster for any metro area is a filter, not a project.
• Time frame: a current snapshot whose financial figures key to a stated regulatory report date (2026-03-31 observed at review), with historical review views reaching to roughly 2013. Each record's own established date reaches back decades — the oldest charters in the directory predate living memory.
• Granularity: two tiers that stack cleanly. One record per institution with its financials; one record per physical branch with location, contact and deposit total. Ranking tables aggregate across all banks. The FDIC certificate joins the tiers.

Set against the wider Datadory catalog — where the average quality score across all 1,744 datasets is 7.81 — this slice scores 6/10, held up by verified field definitions and branch-level deposit granularity no regulator summary publishes, capped by a current-snapshot emphasis rather than a deep archive.

API, files, or your warehouse. Daily, weekly, or hourly.

You pick the channel and the cadence; the field dictionary above travels unchanged across all three. Files suit analysts who want the whole directory loaded once and joined to their own property tables. Structured payloads suit products that surface a nearest-branch result inside an app. Warehouse delivery suits teams running system-wide footprint screens in SQL. Cadence changes are a settings conversation, not a re-integration project — tighten it while a market entry is live, relax it when it is not.

Ranked by how directly the directory answers the day job:

1. Competitive intelligence & product teams. Count every rival's offices by county, watch a footprint expand or contract branch by branch, and price a market entry against the deposit base already sitting in each ZIP code.
2. Market researchers & consultants. Deposit-weighted branch density by metro and county turns "is this market saturated?" into a computed column instead of a guess.
3. Commercial real estate & site-selection teams. Branch proximity, co-tenancy and trade-area analysis around a portfolio start from the same address-and-deposit table — and the rows reconcile cleanly against supervisory registries.
4. Sales & growth teams. Branch lists double as account lists: every office carries a phone number and a location, which makes territory planning concrete.
5. Investors & quants. Deposits per branch by chain feed footprint-efficiency screens ranked nationally.
6. Journalists & academics. Consolidation stories get receipts: established dates and branch-count ranks make "banks are leaving rural counties" verifiable rather than anecdotal.

For contrast inside the same catalog: FDIC BankFind Suite owns the supervisory registry and geocoded locations with quarterly financial panels, while the Federal Reserve H.8 reads weekly credit conditions — neither packages a consumer-grade directory with routing numbers and per-branch deposits attached.

Three things worth knowing upfront. First, money fields arrive exactly as published — dollar signs, commas and hash-prefixed certificates attached — so the typed, parsed version is part of what Datadory ships, and nobody re-derives a parser mid-project. Second, financial figures reflect a stated regulatory report date rather than a rolling clock; trend work should anchor on completed quarters. Third, a directory of physical offices moves: branches open, close and rebrand continuously, so counts differ slightly between pulls taken weeks apart — pin a snapshot date if a report will be re-run later. None of that disturbs the join key: one FDIC certificate covers a bank and every one of its branches.

Notes that pair well with this page:

• Real estate operating companies data hub — the pooled industry view, from housing starts to lender registries.
• FDIC BankFind Suite — the supervisory registry this directory reconciles against, cert for cert.
• Summary of Deposits glossary entry — the mechanics behind deposit-share work.
• Best real estate operating companies datasets — the ranked shortlist this slice sits on.
• Real estate operating companies data guide — the pillar walkthrough of the whole stack.