SAP offering history
Every offering-related filing in SAP SE’s recent SEC record — registrations (announced capacity) kept separate from pricing documents (executed sales). Reviewed 667 filings back to Aug 8, 1996.
| Date | Filing | What it means | |
|---|---|---|---|
| Jul 7, 2014 | 424B3 → | UPDATE | Prospectus update — often a resale registration, not necessarily new capital |
| Jun 25, 1998 | 424B3 → | UPDATE | Prospectus update — often a resale registration, not necessarily new capital |
| Jun 22, 1998 | F-1 → | REGISTERED | F-1 registration — capacity to sell shares, not a sale yet |
Two honest limits. (1) A 424B takedown can price shares or notes — EDGAR’s metadata doesn’t say which, so open the document: large investment-grade filers use these mostly for bond deals (no dilution), small-caps mostly for shares. (2) At-the-market (ATM) programs sell shares gradually and individual sales are not separately filed — the visible footprint is the enabling shelf and its 424B5; actual ATM share counts surface later in the 10-Q/10-K share count. Educational information from public filings, not investment advice.
SAP offering FAQ
When did SAP last execute an offering?
No executed-offering document (424B pricing supplement or 8-K item 3.02) appears in the 667 filings EDGAR returns for SAP SE, reviewed back to 1996-08-08.
When did SAP last announce or register an offering?
The most recent registration is a F-1 filed 1998-06-22. A registration is capacity to sell shares — not a sale.
Does an offering always mean dilution?
Registered direct offerings and shelf takedowns issue new shares and dilute existing holders. Resale registrations (424B3/B7) let existing holders sell and do not create new shares. Secondary sales by insiders also do not dilute. Each row here is labeled with what it is.
Free to use. No account, no card.