How to Read 13F Filings for Crypto Holdings

Form 13F is a quarterly report that institutional investment managers with at least $100 million in qualifying US assets must file with the SEC. It is the single most cited source for institutional crypto exposure, and also the most routinely misread.

What a 13F actually contains

A 13F lists Section 13(f) securities held on the last calendar day of the quarter. It is a snapshot, not a ledger. Positions opened and closed inside the quarter never appear, and the filing deadline is 45 days after quarter end — so by the time you read it, the data is between 45 and 135 days old.

• Spot Bitcoin and Ether ETF shares are reportable, which is why ETF holder lists are the cleanest crypto signal in 13F data.
• Directly held coin is not a Section 13(f) security and does not appear at all.
• Equity in crypto-adjacent companies appears as ordinary stock, with no marker that it is a crypto proxy.

The three mistakes that matter

First, treating a snapshot as conviction. A manager may hold an ETF position on 31 March purely to square a hedge, and exit on 2 April. Second, reading share counts as dollar exposure without adjusting for the ETF's price move since quarter end. Third, double-counting: a fund-of-funds and its underlying manager can both report the same economic exposure.

How to build a defensible read

Anchor on change rather than level. Compare the same filer across consecutive quarters, normalise to shares rather than market value, and only then convert to dollars using the quarter-end NAV. Cross-check anything surprising against 13G/13D filings and the issuer's own disclosure.

Where a filer's identity is ambiguous — multiple CIKs, subsidiaries filing separately — resolve it before aggregating. Aggregating unresolved identities is how a $200 million position becomes a reported $600 million one.