Microsoft's press release moved MSFT -0.16%

MSFT moved -0.31% in five minutes and -0.16% by market close — about 1.4× Microsoft's median close-day move.

· PR Web · Press release · Realized reaction, point-in-time, zero look-ahead.

Source headline

vGrubs Ranks No. 106 on the Inc. 5000, No. 10 Software Company in America

Via PR Web

The quantified answer

How MSFT reacted after the announcement.

-0.31%
5-min
First measured reaction, five minutes after the news
-0.16%
To close
Where the stock settled by the closing bell
1.4×
Magnitude
MSFT's median close-day move (-0.11%) — versus its typical close-day move
MSFT reaction to this newsMSFT reaction to this news across 9 horizons: 30 sec -0.10%, 1 min -0.20%, 5 min -0.31%, 10 min -0.37%, 30 min -0.62% (median +0.02%), 60 min -0.64%, 90 min -0.11%, 120 min -0.62%, to close -0.16% (median -0.11%).30 sec1 min5 min10 min30 min60 min90 min120 minto close30 sec: -0.10%1 min: -0.20%5 min: -0.31%10 min: -0.37%30 min: -0.62% · median +0.02%60 min: -0.64%90 min: -0.11%120 min: -0.62%to close: -0.16% · median -0.11%-0.10%-0.20%-0.31%-0.37%-0.62%-0.64%-0.11%-0.62%-0.16%-0.64%0+0.02%
median MSFT reaction at the same horizon
MSFT realized reaction to this news, by horizon. A dash is a horizon the tape did not measure — never a zero.
HorizonReactionMSFT median
30 sec-0.10%
1 min-0.20%
5 min-0.31%
10 min-0.37%
30 min-0.62%+0.02%
60 min-0.64%
90 min-0.11%
120 min-0.62%
to close-0.16%-0.11%
How fast it got thereFrom the price at the news · 120-minute window
+1%
never traded
+2%
never traded
+3%
never traded
+5%
never traded
-1%
18 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.

What it was worth if you heldPoint-in-time return from the news · not cumulative
Held forReturn
D+1-0.57%
D+2-2.81%
D+3-1.94%
D+4-2.23%
D+5-5.20%
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, MSFT had moved -0.31%; by the close it stood at -0.16% — the two readings agree in direction.

Impact: Neutral. Reaction = percent move vs. the price at the news timestamp. Sources below.

Which window

MSFT’s news landed in the pre-market window; the main session closed -0.16%.

When it landed
  1. Mainprior session
  2. After-hours4:00 – 8:00 PM
  3. Overnightno tape
  4. Pre-market4:00 – 9:30 AM
  5. 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.

Which window the move landed in2 of 4 windows measured
WindowWhat it answersAnchor priceResultvs S&P 500
AllFrom the news to the first main-session close, across every session in between.506.69re-anchored to the first print after the news-0.57%
After-hoursThe move between the closing bell and the overnight halt.not measured
Pre-marketThe move between the pre-market open and the opening bell.not measured
MainThe move inside the regular session, from the news to the close.504.60the price at the news-0.16%+0.36%

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
MSFT reaction across all sessionsMSFT reaction across all sessions across 8 horizons: 30 sec +0.01%, 1 min -0.02%, 5 min -0.02%, 10 min -0.05%, 30 min -0.31%, 60 min -0.41%, 90 min -0.45%, 120 min -0.34%.30 sec1 min5 min10 min30 min60 min90 min120 min30 sec: +0.01%1 min: -0.02%5 min: -0.02%10 min: -0.05%30 min: -0.31%60 min: -0.41%90 min: -0.45%120 min: -0.34%+0.01%-0.02%-0.02%-0.05%-0.31%-0.41%-0.45%-0.34%-0.45%0+0.01%
MSFT reaction measured across every session, by horizon.
HorizonReaction
30 sec+0.01%
1 min-0.02%
5 min-0.02%
10 min-0.05%
30 min-0.31%
60 min-0.41%
90 min-0.45%
120 min-0.34%
What happened

Where this MSFT event came from, and what the tape did with it.

Microsoft issued a press release, carried via PR Web, on Aug 11, 2026. It was one of 3 Microsoft headlines News Quantified labeled that day, so its measurement window overlaps with the others on a shared tape. The same session also carried Microsoft's "MSFT DEADLINE - FINAL REMINDER: Bronstein, Gewirtz and Grossman, LLC…" and 1 other Microsoft headline, each measured on its own clock.

Against the price at the news timestamp, MSFT moved -0.31% after five minutes and -0.16% by the close — about 1.4× Microsoft's median close-day move of -0.11% across 2,000+ events. Because several releases shared that day, their measurement windows overlap and no single headline cleanly owns the move.

What you get

This is the alert you’d have received.

Track MSFT 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 MSFT’s baseline. Nothing else.

Set up MSFT alerts
Context

How this compares to MSFT’s usual reaction.

Across 2,000+ labeled events, MSFT’s median 30-minute reaction to all news is +0.02% (53% up); by the close it is -0.11%.

Where this MSFT event landedvs 2,000+ measured MSFT reactions
MSFTMiddle 50% · -0.33% to +0.40%Zero: 0.00%Median: +0.02%Median +0.02%This event: -0.62%This event -0.62%-1.00%0+1.00%
Middle 50% of MSFT reactions-0.33% to +0.40%
Median reaction (30-min)+0.02%
This event-0.62%
Measured reactions2,000+
Point-in-time · zero look-ahead

Half of all Microsoft news events land between -0.33% and +0.40% at 30 minutes; this one is a single draw from that distribution.

That’s the median — get an email the next time MSFT moves on news

You just saw one reaction. There are 26M+ more.

See the full MSFT reaction history
The record

MSFT’s session ranged -1.00% to +0.14% against the price at the news.

Relative volume
0.6×

15.6M shares against a 30-day average of 28.4M.

Volume-weighted average price
502.80+0.20% at the close

What the average share actually traded at across the session, rather than at any one print.

The session’s range, against the price at the news
Session high
505.33
+0.14% from the news price
Session low
499.55
-1.00% from the news price
High and low across the whole main session — not only the part after the news

The close moved -0.16% against a 20-day average true range of 16.22. MSFT carries no market-cap or price-to-earnings figure on this record, and no short interest, so none is shown.

Next time, know first

Email me when MSFT moves on news.

One email per qualifying move — the headline, the measured reaction, and how it compares to MSFT's baseline. Nothing else.

MSFT Free · unsubscribe anytime
26M+ news records Operating since 2012 Methodology on SSRN ↗
Similar MSFT events

How comparable MSFT events have landed.

Across 5 other recent Microsoft press release events, the median close-day reaction was +1.23%. Each is measured the same way, from its own news timestamp.

Go deeper

8 more MSFT events, each measured the same way.

Recent MSFT events, each with its measured reaction8
That same day, across the market5
Peer tickers, measured the same way4
The same day

MSFT carried 2 other records that day.

Each was measured the same way, from its own timestamp.

Method

How the numbers are made.

How was MSFT's -0.31% reaction measured?

From the news timestamp, not the trading day: News Quantified takes the last trade before this press release as the base price and measures the move five minutes of trading later — point-in-time, zero look-ahead. The same clock produced the -0.16% to-close figure.

What is Microsoft's median reaction, and how does this event compare?

Microsoft's median is drawn from 2,000+ labeled events; at 30 minutes it sits at +0.02%, and -0.11% by the close. This event's move is one draw from that distribution — ordinary or outlier, the chart's median ticks show which.

3 Microsoft headlines shared Aug 11, 2026. Whose reaction is this?

Each of the 3 same-day Microsoft 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 -0.16% predict Microsoft's next reaction?

No. -0.16% is a realized fact about Aug 11, 2026, not a forecast. Past reactions describe a distribution; they say nothing certain about any future move.

Cite this data

How to cite this reaction.

News Quantified. "vGrubs Ranks No. 106 on the Inc. 5000, No. 10 Software Company in America." MSFT realized price reaction, Aug 11, 2026. Retrieved from https://newsquantified.com/tickers/msft/news/vgrubs-ranks-no-106-on-5000-no-10-software-company-america-2026-08-11

Canonical URL: https://newsquantified.com/tickers/msft/news/vgrubs-ranks-no-106-on-5000-no-10-software-company-america-2026-08-11

Query this dataset via the API & MCP →
Stop guessing what the event means

You just saw one reaction.
There are 26 million more.

For investors

Know the next move, measured.

Ticker alerts with the realized reaction — not the headline spin.

Free · no credit card · unsubscribe anytime
For builders

The dataset, one command away.

claude mcp add news-quantified

Then ask Claude: “how does MSFT react to downgrades?” — or pull it raw via REST.

60-second signup on the NQ portal · 1,000 free credits/mo
26M+ news records, 2006–2026 Operating since 2012 Point-in-time, zero look-ahead Peer-reviewable methodology (SSRN) ↗