Hewlett Packard Enterprise Company (HPE)

The full register, from 13F filings

The Register tab above is hand research: a dozen holders, each traced to the filing it came from. This asks the same question of the whole market for the quarter ended 31-mar-2026, where 1,092 managers reported a position. Broad where the research is deep, and shallow in the ways a 13F always is.

Built from 13F filings, which report US listed, long, US custodied positions only. A register from this source is a floor rather than a level: a holder's true position can be far larger, as BlackRock's ASML stake shows at 1.28m shares in a 13F against 26.3m in its 13G/A. Holdings held through derivatives, outside US custody, or below a manager's reporting obligation do not appear. Where a holder is marked as a family, its total sums several separate filing entities and describes something no single filing describes; the constituent entities and their share counts are listed so the total can be checked. That roll-up can legitimately exceed the family's own Schedule 13G, because a 13G is filed by one legal entity: Vanguard reports Alphabet through ten advisory entities, and The Vanguard Group Inc itself reported zero after its January 2026 disaggregation.

What a reader needs to know to read these numbers

• ACQUISITION: closed, funded entirely in cash. On 2 July 2025, HPE completed its merger with Juniper Networks, Inc. under the Agreement and Plan of Merger dated 9 January 2024 (8-K filed 2 Jul 2025). Each share of Juniper common stock was converted into the right to receive $40.00 in cash, representing total cash consideration of approximately $13.4 billion, 'paid through cash on hand, including proceeds and term loan drawdowns from the financings in fiscal 2024, and commercial paper issuances' (Q2 FY2026 10-Q, Note 7). No new HPE common shares were issued to fund or effect this deal, so the acquisition did not move HPE's share count or dilute the register basis. Because the deal was already over a year closed by the time of every source used here (fiscal Q1 and Q2 2026 13Fs, the Feb 2026 proxy, the Dec 2025 10-K), this file did not need to choose between pre- and post-close bases: everything is already post-close.
• CHINESE JOINT VENTURE: HPE has FULLY EXITED its stake in H3C Technologies Co., Limited ('H3C', the New H3C Group), a networking joint venture in China. As of today (18 Aug 2026), HPE holds 0% of H3C; this is a sourced disposal, not a gap. Per the Q2 FY2026 10-Q (Note 7, 'Divestiture of H3C Shares') and the FY2025 10-K: on 17 Nov 2025, HPE's subsidiary H3C Holdings Limited agreed to sell 10% of H3C's total issued share capital to five counterparties including Unisplendour International Technology Limited ('UNIS') for approximately $714 million; on 28 Nov 2025, three additional agreements (including one with UNIS) covered the remaining 9% for approximately $643 million. These two tranches (19% combined) were the entirety of HPE's remaining interest in H3C at that time. On 13 May 2026, HPE closed the sale of 13.8% of H3C's total issued share capital for approximately $987 million, and on 28 May 2026, HPE closed the sale of the remaining 5.2% for approximately $370 million (13.8% + 5.2% = 19%, matching the two November 2025 agreements). No holdings row is carried for H3C because the position has been sold to zero, evidenced by the closing dates and percentages in the Q2 2026 10-Q, not merely assumed absent.
• OTHER HOLDINGS: searched the FY2025 10-K (filed 18 Dec 2025, period ended 31 Oct 2025) for 'equity method', 'unconsolidated', 'joint venture', 'non-marketable', 'strategic investment', 'equity investment' and 'investments in'. Aside from H3C (now fully divested, see above), no other named equity-method investee, joint venture, or strategic equity stake was found. The 10-K's Fair Value note describes two unnamed buckets of non-marketable equity investments in privately held companies, both included in 'Long-term financing receivables and other assets' on the balance sheet: (1) investments accounted for under the fair value option: HPE 'sold its entire portfolio' of these, valued at $54 million, during fiscal 2025 (carrying amount was $88 million at 31 Oct 2024; this bucket is now effectively zero); (2) investments accounted for under the measurement alternative (cost, remeasured on observable price changes or impairment): carrying amount $61 million at 31 Oct 2025, down from $200 million at 31 Oct 2024. Neither bucket names its constituent companies, so per the brief's rule against assigning a combined balance to any one investee, no holdings rows are recorded for either; the combined figures are recorded here and in unknowns. The Q2 FY2026 10-Q (filed 2 Jun 2026, period ended 30 Apr 2026) does not repeat this note, so no more current figure was found for the measurement-alternative bucket.
• EXCLUDED: HPE Financial Services (HPEFS), HPE's captive financing arm, carries a large financing receivables and leased-equipment book (e.g. $1.3 billion and $0.4 billion respectively transferred via securitization through a special-purpose entity as of the Q2 FY2026 10-Q). This is customer lease and loan receivables, not equity stakes in other companies, and is excluded from holdings per the brief's explicit instruction.
• FISCAL PERIODS USED: HPE's fiscal year ends in late October. The FY2025 10-K (filed 18 Dec 2025, period ended 31 Oct 2025) is the latest annual report and was used for the holdings-side search. The Q2 FY2026 10-Q (filed 2 Jun 2026, period ended 30 Apr 2026) is the latest quarterly filing as of 18 Aug 2026 (the Q3 FY2026 10-Q, for the quarter ended 31 Jul 2026, had not yet been filed on EDGAR as of this research) and was used for the H3C divestiture timeline (which runs past the 10-Q's own period end, into May 2026, as a subsequent-events-style update within Note 7) and for cross-checking the Juniper funding language. Register basis is Q2 2026 13F-HR filings, period 30 Jun 2026, filed 7 to 14 Aug 2026, the freshest available. The company.shares_outstanding figure (1,324,203,521) is the dei:EntityCommonStockSharesOutstanding value from the Q2 FY2026 10-Q cover page, as of 26 May 2026, taken directly from SEC's XBRL company-concept API.
• STALE PROXY 13G/A TRAP CONFIRMED: the Feb 2026 DEF 14A's own 5%-holder table cites Schedule 13G/A filings from January and February 2024, with underlying data as of 29 Dec 2023 or 31 Dec 2023, more than two years stale relative to the Q2 2026 13Fs used here. Vanguard: proxy cites 156,075,192 shares (12.01%) vs. the fresh 13F-summed 173,634,706 shares (13.11%), a difference of 17.6 million shares. BlackRock: proxy cites 129,983,458 shares (9.99%) vs. the fresh 13F 134,059,655 shares (10.12%), a difference of 4.1 million shares. State Street: proxy cites 70,870,545 shares (5.45%) vs. the fresh 13F 68,095,481 shares (5.14%), a difference of 2.8 million shares in the OPPOSITE direction, confirming (per the brief's Baker Hughes warning) that the stale-to-fresh error does not run one way. All three register rows here use the fresh 13F, with the stale proxy figures recorded for comparison only.
• VANGUARD ROLL-UP: Vanguard Group Inc (parent CIK 0000102909) filed Form 13F-NT (a notice carrying no holdings) for Q2 2026, confirmed directly on EDGAR. Following the brief's rule, the position is reported entirely by successor entities. This project's own register file (data/registers/HPE.json) already identified 7 Vanguard entities holding HPE as of Q1 2026; re-fetching each entity's fresh Q2 2026 13F-HR confirmed the same 7 entities still hold, summing to 173,634,706 shares (13.11%). No parent-plus-successor double count risk here since the parent filed nothing to double.
• SELF-GATE (computed on this final file, exactly as the chart computes it: members roll into their container at full value, the container itself reduced to its residual, everything else at full value): 13 register rows. One member (Antonio F. Neri, 2,101,761 shares) rolls into the officers-and-directors aggregate (5,834,215 shares raw, reduced to a residual of 3,732,454). Summed total: 173,634,706 (Vanguard) + 134,059,655 (BlackRock) + 68,095,481 (State Street) + 59,597,678 (Capital Group) + 40,050,764 (JPMorgan) + 36,610,129 (Geode) + 32,271,985 (Elliott) + 39,500,289 (Bank of America) + 22,769,642 (Barrow Hanley) + 6,237,618 (Fidelity) + 2,416,327 (T. Rowe Price Associates) + 2,101,761 (Neri) + 3,732,454 (officers/directors residual) = 621,078,489 shares against 1,324,203,521 shares outstanding = 46.90%. This is somewhat above the 25-45% band the chunk prompt describes as typical, but below its 55% red-flag threshold; the concentration is plausible given HPE's unusually large activist (Elliott, 2.44%) and bank/wealth-manager (Bank of America, 2.98%) positions layered on top of the standard index/active managers, and every row above is individually sourced to a filed Q2 2026 13F or the current proxy, not to a mixed basis.
• Derivative instrument note: several Q2 2026 13F filers (BlackRock, State Street, JPMorgan, Fidelity/FMR, Bank of America) also report holdings of HPE's 7.625% Series C Mandatory Convertible Preferred Stock (CUSIP 42824C208, ticker HPEPrC) as derivative info-table lines. These were excluded from every register figure above: they are a different, separately listed instrument from HPE common stock (CUSIP 42824C109) and are not part of company.shares_outstanding.
• Market capitalization ($73.14 billion) is stockanalysis.com's reported figure as of the 18 Aug 2026 page load; no independent share-price figure was separately fetched within the time budget, so market_cap_usd is not cross-checked against shares_outstanding x price the way the Waters Corp file did.
• Company name written as 'Hewlett Packard Enterprise Company (HPE)' deliberately, not as the bare legal name. scripts/crosscheck.py reported UNMATCHABLE for this company because the slug 'hpe' does not occur anywhere inside 'Hewlett Packard Enterprise Company', so the matcher could not find the company under its own name and would have silently dropped every edge into it. That is the shape of bug 12 recorded in STATE.md, dangerous precisely because it produces a clean report while comparing nothing. This is the second instance in two chunks, after Wabtec, and follows the documented BNY Mellon workaround where company.name was written as 'BNY Mellon (The Bank of New York Mellon Corporation)' for the same reason. The durable fix is a KEY entry in crosscheck.py reading "hpe": ("hpe", "hewlettpackardenterprise"); that is a pipeline change and is reported to the maintainer rather than made here. Any company whose slug is an ACRONYM of its legal name will hit this, so it is worth checking the crosscheck summary line for UNMATCHABLE on every future chunk.