Advanced Micro Devices's SEC filing (Form 13F-HR) moved AMD -1.55%
AMD moved -0.53% in five minutes and -1.55% by market close — about 2.2× Advanced Micro Devices's median close-day move.
· SEC EDGAR · SEC filing · Form 13F-HR · Realized reaction, point-in-time, zero look-ahead.
Form 13F-HR ADVANCED MICRO DEVICES For: Jun 30
Via SEC EDGAR
How AMD reacted after the announcement.
| Horizon | Reaction | AMD median |
|---|---|---|
| 30 sec | -0.15% | — |
| 1 min | -0.60% | — |
| 5 min | -0.53% | — |
| 10 min | -0.68% | — |
| 30 min | -0.57% | +0.06% |
| 60 min | -0.45% | — |
| 90 min | +0.01% | — |
| 120 min | +0.22% | — |
| to close | -1.55% | +0.70% |
- +1%
- never traded
- +2%
- never traded
- +3%
- never traded
- +5%
- never traded
- -1%
- 2 min
- -2%
- never traded
- -3%
- never traded
- -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 | -1.57% |
| D+2 | -5.77% |
| D+3 | -9.27% |
| D+4 | -8.68% |
| D+5 | -7.94% |
| 1M | |
| 3M | |
| 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, AMD had moved -0.53%; by the close it stood at -1.55% — the two readings agree in direction.
Impact: Negative. Reaction = percent move vs. the price at the news timestamp. Sources below.
AMD’s news landed in the after-hours window; the main session closed -1.55%.
- 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. | 514.05re-anchored to the first print after the news | -1.57% | — |
| 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. | 513.96the price at the news | -1.55% | -1.10% |
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.02% |
| 1 min | -0.01% |
| 5 min | -0.03% |
| 10 min | -0.01% |
| 30 min | -0.01% |
| 60 min | +0.15% |
| 90 min | +0.31% |
| 120 min | +0.15% |
Where this AMD event came from, and what the tape did with it.
Advanced Micro Devices filed Form 13F-HR with the SEC on Aug 14, 2026. It was the only Advanced Micro Devices headline News Quantified labeled that day.
Against the price at the news timestamp, AMD moved -0.53% after five minutes and -1.55% by the close — about 2.2× Advanced Micro Devices's median close-day move of +0.70% across 2,000+ events.
This is the alert you’d have received.
Form 13F-HR ADVANCED MICRO DEVICES For: Jun 30
Track AMD 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 AMD’s baseline. Nothing else.
Set up AMD alerts →How this compares to AMD’s usual reaction.
Across 2,000+ labeled events, AMD’s median 30-minute reaction to all news is +0.06% (52% up); by the close it is +0.70%.
| Middle 50% of AMD reactions | -0.98% to +0.80% |
|---|---|
| Median reaction (30-min) | +0.06% |
| This event | -0.57% |
| Measured reactions | 2,000+ |
Half of all Advanced Micro Devices news events land between -0.98% and +0.80% at 30 minutes; this one is a single draw from that distribution.
You just saw one reaction. There are 26M+ more.
See the full AMD reaction history→AMD’s session ranged -1.84% to +0.66% against the price at the news.
12.8M shares against a 30-day average of 17.7M.
What the average share actually traded at across the session, rather than at any one print.
The close moved -1.55% against a 20-day average true range of 31.04. AMD carries no market-cap or price-to-earnings figure on this record, and no short interest, so none is shown.
Email me when AMD moves on news.
One email per qualifying move — the headline, the measured reaction, and how it compares to AMD's baseline. Nothing else.
How comparable AMD events have landed.
Across 5 other recent Advanced Micro Devices SEC filing events, the median close-day reaction was -0.61%. Each is measured the same way, from its own news timestamp.
| Date | Headline | 5-min | To close |
|---|---|---|---|
| Form 8-K ADVANCED MICRO DEVICES For: Aug 17 | +1.74% | +0.62% | |
| Form 8-K ADVANCED MICRO DEVICES For: Aug 13 | +0.07% | -0.88% | |
| Form S-3ASR ADVANCED MICRO DEVICES | +1.05% | +0.04% | |
| Form 10-Q ADVANCED MICRO DEVICES For: Jun 27 | +1.77% | -0.61% | |
| Form 8-K ADVANCED MICRO DEVICES For: Aug 04 | +1.77% | -0.61% |
8 more AMD events, each measured the same way.
Recent AMD events, each with its measured reaction8
That same day, across the market4
| Ticker | Headline | 5-min | To close |
|---|---|---|---|
| NVDA | Form 13F-HR NVIDIA CORP For: Jun 30 | +0.07% | -0.23% |
| JPM | JPMorganChase Declares Preferred Stock Dividends | +0.33% | -0.22% |
| BAC | Form 13F-HR BANK OF AMERICA CORP For: Jun 30 | +0.01% | +0.09% |
| AMZN | Form S-4/A AMAZON COM INC | -0.14% | -0.88% |
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 →
How the numbers are made.
How was AMD's -0.53% reaction measured?
From the news timestamp, not the trading day: News Quantified takes the last trade before this SEC filing (Form 13F-HR) 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.55% to-close figure.
What is Advanced Micro Devices's median reaction, and how does this event compare?
Advanced Micro Devices's median is drawn from 2,000+ labeled events; at 30 minutes it sits at +0.06%, and +0.70% by the close. This event's move is one draw from that distribution — ordinary or outlier, the chart's median ticks show which.
Only one Advanced Micro Devices headline was labeled Aug 14, 2026. How is it isolated?
It was the only Advanced Micro Devices headline labeled that day, so its window has no same-day overlap — the move is measured cleanly from its own timestamp.
Does -1.55% predict Advanced Micro Devices's next reaction?
No. -1.55% is a realized fact about Aug 14, 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 13F-HR ADVANCED MICRO DEVICES For: Jun 30." AMD realized price reaction, Aug 14, 2026. Retrieved from https://newsquantified.com/tickers/amd/news/form-13f-hr-advanced-micro-devices-for-jun-30-2026-08-14
Canonical URL: https://newsquantified.com/tickers/amd/news/form-13f-hr-advanced-micro-devices-for-jun-30-2026-08-14
Query this dataset via the API & MCP →