Security record · archived quarter
ICLN
name pending profile ingest
2Tracked holders
0Δ holders
69.24KShares held
$1.18MReported value
+0New positions
−0Exits
All ownership figures: tracked 13F managers only, common-stock positions, reporting period Q3 2026
Ownership over time
| Quarter | Holders | Δ | Shares | Reported value | New | Exits |
|---|---|---|---|---|---|---|
| Q3 2026 | 2 | 0 | 69.24K | $1.18M | n/a | n/a |
| Q2 2026 | 74 | +8 | 30.26M | $618.41M | +10 | −2 |
| Q1 2026 | 67 | +3 | 24.10M | $439.78M | +9 | −6 |
| Q4 2025 | 64 | +2 | 22.29M | $366.32M | +3 | −1 |
| Q3 2025 | 6 | -1 | 5.20M | $80.48M | n/a | −1 |
| Q2 2025 | 4 | +1 | 227.71K | $2.99M | +1 | n/a |
| Q1 2025 | 1 | 0 | 89.74K | $1.02M | +1 | −1 |
| Q4 2024 | 1 | -2 | 5.37K | $61,133 | n/a | −2 |
| Q3 2024 | 3 | +2 | 492.45K | $7.23M | +3 | −1 |
| Q2 2024 | 1 | n/a | 276.75K | $3.69M | n/a | n/a |
Who holds it · Q3 2026
| # | Manager | Shares | Δ shares | Value | Their weight | Held | ||
|---|---|---|---|---|---|---|---|---|
| 1 | Wealth Enhancement Advisory… | 39.74K | +7.1% | $680,419 | 0.0% | ▲ Add | 4 | SEC ↗ |
| 2 | TD Waterhouse Canada Inc. | 29.50K | -16.2% | $496,826 | 0.0% | ▼ Trim | 4 | 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): 417 holders, 35.19M shares, $629.26M 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: Q3 2026 ·
Methodology ·
Get this via the API