Broadcom's SEC filing (Form SD) moved AVGO -1.37%
AVGO moved -0.75% in five minutes and -1.37% by market close — about 23.3× Broadcom's median close-day move.
· SEC EDGAR · SEC filing · Form SD · Realized reaction, point-in-time, zero look-ahead.
Form SD Broadcom Inc.
Via SEC EDGAR
How AVGO reacted after the announcement.
| Horizon | Reaction | AVGO median |
|---|---|---|
| 30 sec | -1.17% | — |
| 1 min | -0.82% | — |
| 5 min | -0.75% | — |
| 10 min | -1.78% | — |
| 30 min | -1.42% | -0.39% |
| 60 min | -1.88% | — |
| 90 min | -1.70% | — |
| 120 min | -1.63% | — |
| to close | -1.37% | -0.06% |
- +1%
- never traded
- +2%
- never traded
- +3%
- never traded
- +5%
- never traded
- -1%
- 0 min
- -2%
- 11 min
- -3%
- 282 min
- -5%
- never traded
A hatched rung is a threshold the price never touched inside the measured window — not a missing measurement. Most news never moves a large-cap by 5% either way, so a mostly empty ladder is the finding, not a gap in the data.
| Held for | Return |
|---|---|
| D+1 | +4.50% |
| D+2 | +3.99% |
| D+3 | -9.10% |
| D+4 | -16.30% |
| D+5 | -13.94% |
| 1M | -19.86% |
| 3M | -19.78% |
| 6M | |
| 12M |
Each row is measured from the price at the news to that horizon independently, so the ladder is not cumulative and a later row can sit above an earlier one. “Available” is a date, not a gap: that horizon has not elapsed yet for this event, and it is computed from the event’s own timestamp rather than from the data. An em dash is the other case — the horizon passed and no return was recorded.
Five minutes after the news, AVGO had moved -0.75%; by the close it stood at -1.37% — the two readings agree in direction.
Impact: Negative. Reaction = percent move vs. the price at the news timestamp. Sources below.
AVGO’s news landed in the after-hours window; the main session closed -1.37%.
- Mainprior session
- After-hours4:00 – 8:00 PM
- Overnightno tape
- Pre-market4:00 – 9:30 AM
- Main session9:30 AM – 4:00 PM
Segment widths are fixed, so two events on different days sit in comparable places. Hatched segments are real elapsed time with no tape to measure — the overnight halt is not a gap in the data. This event carries no intraday receipt time, so it is not pinned to a minute.
| Window | What it answers | Anchor price | Result | vs S&P 500 |
|---|---|---|---|---|
| All | From the news to the first main-session close, across every session in between. | 460.85re-anchored to the first print after the news | +4.50% | — |
| After-hours | The move between the closing bell and the overnight halt. | — | not measured | — |
| Pre-market | The move between the pre-market open and the opening bell. | — | not measured | — |
| Main | The move inside the regular session, from the news to the close. | 488.28the price at the news | -1.37% | -1.69% |
The main-session result is measured upstream against the price at the news; the all-sessions result is computed here from its own anchor and close, so the two can differ in the last decimal. The adjusted column subtracts the S&P 500’s move over the same main-session span — there is no index anchor for the all-sessions span, so that cell stays empty rather than borrowing this one. After-hours and pre-market are measured upstream but populate on a small minority of events, so this page does not request them. Those rows are unmeasured, not empty.
The same event measured across every session8
| Horizon | Reaction |
|---|---|
| 30 sec | -0.00% |
| 1 min | -0.00% |
| 5 min | +0.01% |
| 10 min | +0.28% |
| 30 min | +1.42% |
| 60 min | +3.17% |
| 90 min | +2.79% |
| 120 min | +2.74% |
Where this AVGO event came from, and what the tape did with it.
Broadcom made an SEC filing on Jun 1, 2026. It was one of 2 Broadcom headlines News Quantified labeled that day, so its measurement window overlaps with the others on a shared tape. The same session also carried Broadcom's "Broadcom Connects the AI Edge with Comprehensive Multi-Gig Broadband…", each measured on its own clock.
Against the price at the news timestamp, AVGO moved -0.75% after five minutes and -1.37% by the close — about 23.3× Broadcom's median close-day move of -0.06% across 2,000+ events. Because several releases shared that day, their measurement windows overlap and no single headline cleanly owns the move.
This is the alert you’d have received.
Form SD Broadcom Inc.
Track AVGO and you’ll get one email like this the next time it moves on news — the headline, the measured reaction, and how it compares to AVGO’s baseline. Nothing else.
Set up AVGO alerts →How this compares to AVGO’s usual reaction.
Across 2,000+ labeled events, AVGO’s median 30-minute reaction to all news is -0.39% (37% up); by the close it is -0.06%.
| Middle 50% of AVGO reactions | -1.06% to +0.33% |
|---|---|
| Median reaction (30-min) | -0.39% |
| This event | -1.42% |
| Measured reactions | 2,000+ |
Half of all Broadcom news events land between -1.06% and +0.33% at 30 minutes; this one is a single draw from that distribution.
You just saw one reaction. There are 26M+ more.
See the full AVGO reaction history →AVGO’s session ranged -3.65% to +0.11% against the price at the news.
27.7M shares against a 30-day average of 14.7M.
What the average share actually traded at across the session, rather than at any one print.
The close moved -1.37% against a 20-day average true range of 16.94. AVGO carries no market-cap or price-to-earnings figure on this record, and no short interest, so none is shown.
Email me when AVGO moves on news.
One email per qualifying move — the headline, the measured reaction, and how it compares to AVGO's baseline. Nothing else.
How comparable AVGO events have landed.
Across 5 other recent Broadcom SEC filing events, the median close-day reaction was +0.18%. Each is measured the same way, from its own news timestamp.
| Date | Headline | 5-min | To close |
|---|---|---|---|
| Form EFFECT Broadcom Inc. | -0.85% | +1.10% | |
| Form 10-Q Broadcom Inc. For: Aug 02 | -0.42% | +0.11% | |
| Form S-4 Broadcom Inc. | -0.45% | -0.85% | |
| Form 8-K Broadcom Inc. For: Sep 02 | -1.08% | +1.51% | |
| Form 8-K Broadcom Inc. For: Jul 06 | +2.14% | +0.18% |
8 more AVGO events, each measured the same way.
Recent AVGO events, each with its measured reaction8
That same day, across the market8
Same measurement, same clock, different names — each headline measured from its own news timestamp, point-in-time.
Peer tickers, measured the same way4
Every US ticker is measured the same way, from its own news timestamp. Browse all tickers →
AVGO carried 1 other record that day.
Each was measured the same way, from its own timestamp.
| Record | Event | 5-min | To close |
|---|---|---|---|
| Broadcom Connects the AI Edge with Comprehensive Multi-Gig Broadband and Wi-Fi 8 Innovations | Press release | -0.75% | -1.37% |
How the numbers are made.
How was AVGO's -0.75% reaction measured?
From the news timestamp, not the trading day: News Quantified takes the last trade before this SEC filing (Form SD) as the base price and measures the move five minutes of trading later — point-in-time, zero look-ahead. The same clock produced the -1.37% to-close figure.
What is Broadcom's median reaction, and how does this event compare?
Broadcom's median is drawn from 2,000+ labeled events; at 30 minutes it sits at -0.39%, and -0.06% by the close. This event's move is one draw from that distribution — ordinary or outlier, the chart's median ticks show which.
2 Broadcom headlines shared Jun 1, 2026. Whose reaction is this?
Each of the 2 same-day Broadcom events is measured from its own timestamp, but their windows overlap on one tape, so we show the cluster rather than pretending a single headline owns the move.
Does -1.37% predict Broadcom's next reaction?
No. -1.37% is a realized fact about Jun 1, 2026, not a forecast. Past reactions describe a distribution; they say nothing certain about any future move.
How to cite this reaction.
News Quantified. "Form SD Broadcom Inc.." AVGO realized price reaction, Jun 1, 2026. Retrieved from https://newsquantified.com/tickers/avgo/news/form-sd-broadcom-2026-06-01
Canonical URL: https://newsquantified.com/tickers/avgo/news/form-sd-broadcom-2026-06-01
Query this dataset via the API & MCP →