Twenty-six areas and a geographic information system, against the city banks (1996)
Holding the region as a surface, not a set of branches
The heart of this decision was a regional bank’s attempt to meet nationwide city banks with a surface. The old “mini city bank” line had chased them on scale; the return home switched the thinking to binding Kanagawa into 26 areas and holding each one firmly. The geographic information system was the tool that put customer distribution — data — behind branch siting and sales work that had run on instinct and habit. It was an attempt to push the slogan of local commitment down into how the organization moved and how it used what it knew.
How much the strategy did for market share or earnings in the prefecture is, admittedly, hard to measure on its own. Behind the return home, the bad loans of the “mini city bank” years weighed heavily, and across 1998–99 the Bank of Yokohama took ¥220 billion of public funds. Even so, the idea of treating Kanagawa as a surface — binding it finely and defending it piece by piece — runs all the way to the three-bank structure created by the acquisition of the Kanagawa Bank in 2023. How does a regional bank hold its own against a nationwide network? In the mid-1990s the Bank of Yokohama offered one answer: by binding its region tightly together.
Revenue and net margin, FY1991–FY2001
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY1996 onwards — after it was taken.
Source: securities reports
Read the full dossier in Japanese →
The Japanese edition carries the complete record of this decision — the situation that forced it, the options weighed, what actually followed, and the sources behind every claim.
Other key decisions at Yokohama Financial Group
Yen amounts are converted at the average rate of each figure’s own year — not today’s rate; the revenue chart is shown in yen. Exchange rates & sources — the full ¥/US$ table →
Disclaimer
- This page is provided for general information only and is not investment advice, nor a recommendation to buy or sell any security.
- Figures are compiled independently and include our own estimates, approximations and machine-processed data; we make no warranty as to their accuracy or completeness.
- Sources are primarily each company’s securities reports and other public filings, but errors and omissions may remain.
- Any use of this information is at the reader’s own risk. Past performance does not indicate future results.
- Company names, logos and other marks belong to their respective owners.
Data API
Yokohama Financial Group’s history, financials, executives and
shareholders are published as static JSON — no key, plain GET.
Full specification →
| Method | Endpoint | Returns |
|---|---|---|
| GET | /api/companies.json | All companies |
| GET | /api/7186/manifest.json | Resource index |
| GET | /api/7186/history.json | History overview |
| GET | /api/7186/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/7186/decisions.json | Management decisions (index) |
| GET | /api/7186/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/7186/executives.json | Executives |
| GET | /api/7186/shareholders.json | Major shareholders |
| GET | /api/7186/financials.json | Financial statements |
| GET | /api/7186/financials-longterm.json | Long-term results |
| GET | /api/7186/segments.json | Business segments |
| GET | /api/7186/regions.json | Sales by region |
| GET | /api/7186/workforce.json | Workforce |