Security record · archived quarter
EWS
name pending profile ingest
2Tracked holders
0Δ holders
207.51KShares held
$6.84MReported 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 | 207.51K | $6.84M | n/a | n/a |
| Q2 2026 | 43 | -1 | 11.55M | $342.04M | +3 | −4 |
| Q1 2026 | 45 | +1 | 9.69M | $273.12M | +7 | −6 |
| Q4 2025 | 44 | +1 | 5.23M | $143.78M | +1 | n/a |
| Q3 2025 | 6 | -2 | 3.14M | $89.06M | n/a | −2 |
| Q2 2025 | 6 | +2 | 2.79M | $72.60M | +3 | −1 |
| Q1 2025 | 2 | -1 | 557.99K | $13.26M | n/a | −1 |
| Q4 2024 | 3 | -1 | 613.12K | $13.40M | n/a | −1 |
| Q3 2024 | 4 | +2 | 571.70K | $12.66M | +3 | −1 |
| Q2 2024 | 2 | n/a | 508.57K | $9.76M | n/a | n/a |
Who holds it · Q3 2026
| # | Manager | Shares | Δ shares | Value | Their weight | Held | ||
|---|---|---|---|---|---|---|---|---|
| 1 | TD Waterhouse Canada Inc. | 170.34K | +6.3% | $5.66M | 0.0% | ▲ Add | 4 | SEC ↗ |
| 2 | Wealth Enhancement Advisory… | 37.17K | +264.9% | $1.18M | 0.0% | ▲ Add | 3 | 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): 140 holders, 14.73M shares, $358.31M 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