Security record · archived quarter
DIVO
Amplify CWP Enhanced Dividend Income ETF · Financial Services · Asset Management - Income
2Tracked holders
0Δ holders
1.84MShares held
$86.11MReported 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 | 1.84M | $86.11M | n/a | n/a |
| Q2 2026 | 52 | +3 | 52.85M | $2.42B | +5 | −2 |
| Q1 2026 | 50 | +3 | 49.45M | $2.22B | +8 | −5 |
| Q4 2025 | 47 | 0 | 45.16M | $2.01B | n/a | n/a |
| Q3 2025 | 5 | +1 | 2.54M | $113.15M | +1 | n/a |
| Q2 2025 | 2 | +1 | 44.77K | $1.90M | +1 | n/a |
| Q4 2024 | 1 | -1 | 6.90K | $279,312 | n/a | −1 |
| Q3 2024 | 2 | -1 | 31.95K | $1.32M | n/a | −1 |
| Q2 2024 | 3 | n/a | 95.71K | $3.70M | n/a | n/a |
Who holds it · Q3 2026
| # | Manager | Shares | Δ shares | Value | Their weight | Held | ||
|---|---|---|---|---|---|---|---|---|
| 1 | Wealth Enhancement Advisory… | 1.83M | +4.1% | $85.88M | 0.1% | ▲ Add | 4 | SEC ↗ |
| 2 | TD Waterhouse Canada Inc. | 5.00K | 0.0% | $232,350 | 0.0% | Held | 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): 379 holders, 78.94M shares, $3.52B 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