Taking ¥30bn of state preferred shares under the Industrial Revitalisation Act (2009)
What the size of ¥30 billion decided
“The worst mistake was making the DBJ our lead bank for ¥30 billion. Without the DBJ, some commercial bank would have stepped up.” Eighteen months after the failure, Sakamoto Yukio named the scale of the rescue itself as the cause of it. His reading was that with borrowings on the ¥100 billion scale, as at Sharp or Renesas, the banks could not have let the company go. ¥30 billion was enough to defer the crisis and not enough to make a bank a party to it — and by taking public money, Elpida arguably closed off the space in which a private lead bank might have appeared.
Even so, one cannot say a larger cheque would have saved it. By 2009 DRAM had become an industry in which everyone except Samsung survived on their government’s or their banks’ support. Thicken the aid and you simply stay longer in that war of attrition. In fact the Taiwanese alliance written into the certification never happened, so the premise of the support collapsed in its first year. Once the state decided to keep DRAM in Japan, it had not decided how to keep it — and that is where the limit of this decision lies.
Revenue and net margin, FY2004–FY2012
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2009 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 Elpida Memory
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
Elpida Memory’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/6665/manifest.json | Resource index |
| GET | /api/6665/history.json | History overview |
| GET | /api/6665/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/6665/decisions.json | Management decisions (index) |
| GET | /api/6665/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/6665/executives.json | Executives |
| GET | /api/6665/shareholders.json | Major shareholders |
| GET | /api/6665/financials.json | Financial statements |
| GET | /api/6665/financials-longterm.json | Long-term results |
| GET | /api/6665/segments.json | Business segments |
| GET | /api/6665/regions.json | Sales by region |
| GET | /api/6665/workforce.json | Workforce |