Institutional Markets
Rakuten Reports Unchanged XRP ETF Share Count in Q3
Rakuten reported the same 6,690 Bitwise XRP ETF shares in June and September. A $33,250 valuation increase does not establish a new purchase or current ownership.

What Rakuten’s November 13 XRP ETF filing establishes
Rakuten Group reported 6,690 Bitwise XRP ETF shares at September 30, 2026, exactly matching its June 30 count. Its November 13 SEC filing values the position at $111,255, compared with $78,005 previously. The new disclosure confirms a repeated quarter-end share count, not a newly established position or a current XRP purchase.
The distinction matters for readers using institutional filings to judge demand. U.Today independently reported the September position on November 13; CryptoTuts compared it with June on November 14. The SEC records supply the underlying evidence. Their useful new information is agreement between two reported endpoint counts, while the dollar amount attached to the shares changed.
This answers a specific question left open by AllAboutXRP’s August review of institutional Bitwise holdings: what would the same managers report next quarter? For Rakuten, the new record supplies a comparison. It does not settle what happened between those observations or after the latest measurement date.
Match Rakuten’s security and dates before calculating change
Both SEC information tables identify Bitwise XRP ETF and CUSIP 09174F107. CUSIP is the security identifier. Matching that field reduces the risk of comparing different products with similar XRP names. The unit is fund shares, so the count should not be presented as a number of XRP tokens.
The compact comparison below keeps the position date separate from the document’s publication date. That separation prevents a November filing from becoming a November trading claim. These are the amounts Rakuten reported, not independently reconstructed account balances or a valuation refreshed for publication.
For someone maintaining an institutional-holdings dataset, the practical unit of evidence is a dated row with its original filing attached. Keep the old observation when adding the new one. Overwriting June with September destroys the very comparison needed to evaluate the headline. Store an amendment as a versioned correction rather than an unexplained change to history.
A practical research sheet would separate the position date, the filing date and the date on which someone retrieved the document. If it also contains a later market estimate, give that estimate its own date and label. This allows another reader to reproduce the historical comparison without assuming that every number on the sheet describes the same moment. It also makes an old filing resurfacing in the news easier to recognize.
| Position date | Shares reported | Reported value | SEC filing date |
|---|---|---|---|
| June 30, 2026 | 6,690 | $78,005 | August 12, 2026 |
| September 30, 2026 | 6,690 | $111,255 | November 13, 2026 |
| Source: Rakuten’s SEC information tables [1] and [2], with filing dates from their EDGAR records. Values are U.S. dollars at the stated quarter end, not current prices. | |||
Why a $33,250 value increase is not a purchase amount
Calculation: subtracting the June value from September gives $33,250. Dividing that difference by $78,005 produces approximately 42.6%. This is the change between two reported position values. CryptoTuts independently reports the same arithmetic. There is no increase in reported shares in that calculation, and it should not be described as $33,250 of fresh capital invested by Rakuten.
A useful reconciliation separates two questions: how many units were recorded, and what value was assigned to those units? Here the first answer is equal at both endpoints. The second differs. Keeping those questions separate avoids turning a mark-to-market comparison into an account of cash entering an investment.
Unresolved: the documents do not supply a transaction-by-transaction history. Consider a hypothetical manager that sells part of a position and later restores it before quarter end. Its final count can match the starting count despite trading activity. Another manager could make no trades and report that same ending count. These are examples of different possible paths, not claims about Rakuten.
For that reason, “no net change in reported quarter-end shares” is more defensible than “Rakuten never sold.” Nor can this comparison establish Rakuten’s realized profit, acquisition cost, investment return after expenses, or motive. Those questions require account records or an explicit company explanation that the two rows do not provide.
Rakuten’s combination report has a limited reporting perimeter
The November cover page identifies a 13F combination report. SEC guidance explains that this format places some reportable securities in the filing and others in another manager’s report. Interactive Brokers independently describes the same reporting arrangement. A combination report therefore needs to be read with its cover page, not only its headline table total.
That affects a common follow-up calculation: dividing an XRP position by a purported company portfolio. A percentage needs a denominator with an explicit scope and the same measurement date. A selected information-table total, a consolidated balance sheet and company market capitalization answer different questions. Substituting one for another can produce a precise-looking number with an unclear meaning.
Our interpretation: a reliable comparison should state the reporting entity, the security, the measurement date and the covered set of assets before discussing allocation size. If the intended claim concerns the whole corporate group, additional reports must be reconciled first. Simply adding every affiliated filing is not a substitute for checking whether the same exposure appears more than once.
For this story, the narrow matched XRP row is sufficient. It supports the share-count comparison without assuming that the table describes every Rakuten investment, every subsidiary’s exposure or a group-wide treasury policy.
Rakuten’s ETF shares and Bitwise’s fund issuance are separate records
Bitwise states that investing in its XRP ETF differs from directly investing in XRP. It also says shares trade at market prices and are not individually redeemable from the fund. The Investment Company Institute explains the broader market structure: investors can trade existing ETF shares with each other, while authorized participants handle creations and redemptions with a fund.
The implication is specific. A manager’s reported position is evidence about its disclosed shares. A fund’s issuance records address whether new shares were created or existing shares redeemed. Even if a future Rakuten filing reports a higher count, that alone would not identify which mechanism supplied those shares or establish a matching purchase of underlying XRP.
An analyst can keep separate records for manager holdings and fund activity, then compare their dates. The test is whether the available evidence connects the two. An increase in a holder’s shares and an increase in fund issuance during the same quarter would still leave trade timing and attribution unresolved. Coincidence across a broad reporting period is weaker evidence than a linked transaction record.
How XRP readers should update the institutional-demand thesis
For readers tracking institutional participation, the constructive finding is that Rakuten’s disclosed position appears at both quarter ends. The limitation is equally concrete: this particular comparison offers no evidence of a larger reported share position. Neither observation establishes whether buying the ETF was a good decision, and neither resolves the direction of XRP prices.
For editors and researchers, the next update should identify a changed field rather than refresh the same headline. A different share count would change the endpoint comparison. A corrected filing could change the historical baseline. An explicit Rakuten explanation could clarify purpose. Fund-level creations would answer a separate supply question. Each would add information that this disclosure lacks.
A current-value estimate would introduce another assumption: that the September position still exists. This article therefore retains the dated filing values. Readers can assess what was actually disclosed without mistaking a later market quote for a newly verified account balance. The watch list below identifies the records that could justify a substantive follow-up.
What to watch next
- • Rakuten’s next Form 13F for December 31, 2026: compare the same Bitwise XRP ETF CUSIP and share unit with September.
- • Any 13F-HR/A amendment affecting the June or September XRP row, with the original and corrected versions retained.
- • A dated Rakuten statement identifying the purpose or current status of the position, rather than an inference from its size.
- • Bitwise fund reports showing creations and redemptions for the relevant period, assessed separately from manager holdings.
- • A reconciled set of reporting-manager records before making a claim about Rakuten’s total group allocation.
Sources and verification
We prioritize primary records and label supporting coverage. Dates reflect each source’s publication record.
- [1]SEC EDGAR, Rakuten Q3 2026 information tableprimary
- [2]SEC EDGAR, Rakuten Q2 2026 information tableprimary
- [3]SEC EDGAR, Rakuten Q3 cover and summary pagesprimary
- [4]U.Today, Rakuten’s disclosed Bitwise XRP ETF positionsupporting
- [5]CryptoTuts, Rakuten’s June and September share-count comparisonsupporting
- [6]SEC, Frequently Asked Questions About Form 13Fprimary
- [7]Interactive Brokers, Form 13F reporting by institutional investment managerssupportingUndated reference
- [8]Bitwise XRP ETF, product disclosuresprimaryUndated reference
- [9]Investment Company Institute, ETF Basics and Structure FAQssupporting
- [10]Disclosery, Rakuten Q3 Form 13F filing and reporting scopesupportingUndated reference