Security record · archived quarter
RSSS
name pending profile ingest
3Tracked holders
—Δ holders
330.35KShares held
$842,519Reported value
+0New positions
−0Exits
All ownership figures: tracked 13F managers only, common-stock positions, reporting period Q2 2024
Ownership over time
| Quarter | Holders | Δ | Shares | Reported value | New | Exits |
|---|---|---|---|---|---|---|
| Q2 2026 | 15 | 0 | 2.14M | $4.96M | +2 | −2 |
| Q1 2026 | 15 | -4 | 2.26M | $5.10M | +1 | −5 |
| Q4 2025 | 19 | 0 | 2.47M | $7.27M | +1 | −1 |
| Q3 2025 | 8 | 0 | 1.96M | $7.30M | +1 | −1 |
| Q2 2025 | 6 | 0 | 1.90M | $5.44M | — | — |
| Q1 2025 | 4 | -2 | 571.83K | $1.49M | — | −2 |
| Q4 2024 | 6 | +2 | 596.60K | $2.48M | +2 | — |
| Q3 2024 | 3 | 0 | 376.11K | $1.03M | — | — |
| Q2 2024 | 3 | — | 330.35K | $842,519 | — | — |
Who holds it · Q2 2024
| # | Manager | Shares | Δ shares | Value | Their weight | Held | ||
|---|---|---|---|---|---|---|---|---|
| 1 | Geode Capital Management ✦ (passive) | 174.88K | — | $446,078 | 0.0% | n/c | 1 | SEC ↗ ×2 |
| 2 | Renaissance Technologies ✦ | 117.10K | — | $298,605 | 0.0% | n/c | 1 | SEC ↗ |
| 3 | Citadel Advisors ✦ | 38.37K | — | $97,836 | 0.0% | n/c | 1 | SEC ↗ |
“Their weight” = the position's share of that manager's reported 13F equity value — the conviction measure. ✦ = curated manager.
New buyers
| No new tracked buyers this quarter. |
Exited
| No tracked exits this quarter. |
Full-market context: across ALL 13F filers (SEC structured data, Q1 2026): 39 holders, 11.60M shares, $26.08M 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: Q2 2024 ·
Methodology ·
Get this via the API