Security record · archived quarter
BBJP
JPMorgan BetaBuilders Japan ETF · Financial Services · Asset Management - Global
2Tracked holders
0Δ holders
11.85KShares held
$929,508Reported 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 | 11.85K | $929,508 | n/a | n/a |
| Q2 2026 | 58 | -1 | 149.17M | $11.22B | +2 | −3 |
| Q1 2026 | 60 | 0 | 150.71M | $10.07B | +3 | −3 |
| Q4 2025 | 59 | +2 | 143.50M | $9.46B | +2 | n/a |
| Q3 2025 | 7 | -1 | 275.26M | $18.25B | n/a | −1 |
| Q2 2025 | 6 | +2 | 208.16K | $12.86M | +2 | n/a |
| Q1 2025 | 2 | +2 | 32.98K | $1.85M | +2 | n/a |
| Q3 2024 | 3 | +1 | 31.14K | $1.85M | +2 | −1 |
| Q2 2024 | 2 | n/a | 95.42K | $5.38M | n/a | n/a |
Who holds it · Q3 2026
| # | Manager | Shares | Δ shares | Value | Their weight | Held | ||
|---|---|---|---|---|---|---|---|---|
| 1 | Wealth Enhancement Advisory… | 11.65K | +15.8% | $913,826 | 0.0% | ▲ Add | 4 | SEC ↗ |
| 2 | TD Waterhouse Canada Inc. | 200 | 0.0% | $15,682 | 0.0% | Held | 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): 256 holders, 20.29M shares, $1.36B 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