Becoming the fourth carrier: the bet on a fully virtualized network (2017)
The reckoning of a bet that joined the ecosystem to telecom
The heart of this decision was a contrarian one: that a net company earning from e-commerce and finance would take on, for itself, the most capital-hungry infrastructure of all — telecommunications. To remain an MVNO renting lines was to leave its monthly point of contact with customers forever in the grip of another company’s network; to sever that dependence, Rakuten chose the heavy fixed asset of its own base stations. Chairman and President Mikitani’s reading that a fully virtualized network could cut costs by 70 to 80 percent was the premise on which the venture’s economics rested, hinging on that single point of compressed capital spending — but the cost of building an unprecedented network and covering the whole country exceeded the initial estimates, and rebounded as more than $6.1B (¥800bn) in cumulative net losses and the burden of bond redemptions.
That the bet did not end in a swing and a miss was because, somewhere along the way, Rakuten loosened its insistence on an all-own network. Filling the indoor and underground weak spots with KDDI roaming, securing a platinum band, and thickening the financial backing through the tie-up with Mizuho — laying realistic corrections over an aggressive plan, it reached 10 million subscriber lines and EBITDA profitability in 2025. The vision of extending the ecosystem from goods to finance and on to telecommunications came at a cost that once shook the finances of the entire company, but it has, for now, made real its original aim of placing the monthly telecom contract at the centre of the ecosystem. Whether the 10 million lines that Chairman and President Mikitani called “a waypoint” will bear fruit worthy of the capital sunk into them will be answered by the ARPU and churn rate still to come.
Revenue and net margin, FY2012–FY2022
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2017 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 Rakuten 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
Rakuten 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/4755/manifest.json | Resource index |
| GET | /api/4755/history.json | History overview |
| GET | /api/4755/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/4755/decisions.json | Management decisions (index) |
| GET | /api/4755/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/4755/executives.json | Executives |
| GET | /api/4755/shareholders.json | Major shareholders |
| GET | /api/4755/financials.json | Financial statements |
| GET | /api/4755/financials-longterm.json | Long-term results |
| GET | /api/4755/segments.json | Business segments |
| GET | /api/4755/regions.json | Sales by region |
| GET | /api/4755/workforce.json | Workforce |