Security record · archived quarter
SPHB
name pending profile ingest
3Tracked holders
+1Δ holders
44.69KShares held
$3.96MReported value
+1New positions
−0Exits
All ownership figures: tracked 13F managers only, common-stock positions, reporting period Q4 2024
Ownership over time
| Quarter | Holders | Δ | Shares | Reported value | New | Exits |
|---|---|---|---|---|---|---|
| Q2 2026 | 40 | +2 | 2.66M | $414.04M | +4 | −2 |
| Q1 2026 | 39 | -1 | 2.13M | $247.26M | +5 | −6 |
| Q4 2025 | 40 | 0 | 2.53M | $295.35M | — | — |
| Q3 2025 | 7 | 0 | 1.52M | $167.22M | — | — |
| Q2 2025 | 4 | 0 | 128.44K | $12.53M | — | — |
| Q1 2025 | 3 | 0 | 79.47K | $6.22M | — | — |
| Q4 2024 | 3 | +1 | 44.69K | $3.96M | +1 | — |
| Q3 2024 | 2 | -1 | 48.24K | $4.30M | — | −1 |
| Q2 2024 | 3 | — | 119.97K | $10.13M | — | — |
Who holds it · Q4 2024
| # | Manager | Shares | Δ shares | Value | Their weight | Held | ||
|---|---|---|---|---|---|---|---|---|
| 1 | Renaissance Technologies ✦ | 18.30K | New | $1.62M | 0.0% | New | 1 | SEC ↗ |
| 2 | D. E. Shaw & Co. ✦ | 15.39K | -57.5% | $1.36M | 0.0% | ▼ Trim | 3 | SEC ↗ |
| 3 | Citadel Advisors ✦ | 11.00K | -9.0% | $974,884 | 0.0% | ▼ Trim | 3 | SEC ↗ |
“Their weight” = the position's share of that manager's reported 13F equity value — the conviction measure. ✦ = curated manager.
New buyers
| Renaissance Technologies | $1.62M | 0.0% |
Exited
| No tracked exits this quarter. |
Full-market context: across ALL 13F filers (SEC structured data, Q1 2026): 134 holders, 3.26M shares, $353.36M reported. This is a different, older period than the tracked-universe figures above and the two are never mixed.
Frequently co-owned
What else this security's tracked holders most often hold — shared-ownership counts, not fundamental relationships.
Provenance: Ownership from parsed 13F common-stock positions (tracked universe, comparable sets for changes); insider rows from Forms 3/4/5; stakes from Schedules 13D/13G; every filing links to its original on SEC EDGAR.
Reporting period: Q4 2024 ·
Methodology ·
Get this via the API