STRASMORE/EXPLORE 3,256 QUERIES

Apple: implied volatility and the expected move at six horizons, one session

Answered against 22 years of US equities and 12 years of US options data and published with the query that produced it. This result is stored as of 2026-09-26, from Expected Move From Implied Volatility.

as of table 6×7read in context →
Apple: implied volatility and the expected move at six horizons, one session — 6 rows by 7 columns, computed from US exchange, SIP and OPRA data.
horizonavg_daysiv_pctexpected_move_pctexpected_move_usdunderlying_priceas_of
1 week5283.1710.41327.8Jul 15, 2026
2 weeks1225.14.4714.65327.8Jul 15, 2026
1 month2729.58.0826.49327.8Jul 15, 2026
3 months7927.412.7341.74327.8Jul 15, 2026
6 months16527.718.6261.05327.8Jul 15, 2026
1 year29228.425.4483.39327.8Jul 15, 2026
Rows × columns
6 × 7
Computed
Completeness
No missing values
Source
US exchange, SIP and OPRA market data
Licence
Strasmore terms · free, no signup
Formats
JSON · CSV · the SQL below

What each column holds

Column definitions for Apple: implied volatility and the expected move at six horizons, one session, derived from the stored result.
ColumnTypeRangeNotes
horizon text 6 distinct values (1 month, 1 week, 1 year…)
avg_days number 5 to 292
iv_pct number 25.1 to 29.5 percent
expected_move_pct number 3.17 to 25.44 percent
expected_move_usd number 10.41 to 83.39 US dollars
underlying_price number every row is 327.8 US dollars
as_of text 1 distinct value (Jul 15, 2026)

Computed from Strasmore's warehouse of US exchange, SIP and OPRA market data. Equity prices are delayed; options greeks and implied volatility are end-of-day. This result is stored, not recomputed on load — it is exactly the numbers that were returned on , and the query below is what returned them.

Run it yourself

This is the exact query behind the result above. Change a ticker, a date or a column and run it against the warehouse — no account, no key. The no-signup tier is smaller than the one this page was computed on; a query that reaches past it comes back saying which plan runs it.

SELECT multiIf(days_to_expiry <= 7, '1 week',
               days_to_expiry <= 14, '2 weeks',
               days_to_expiry <= 45, '1 month',
               days_to_expiry <= 120, '3 months',
               days_to_expiry <= 240, '6 months',
               '1 year') AS horizon,
       round(avg(days_to_expiry), 0) AS avg_days,
       round(100 * avg(toFloat64(implied_volatility)), 1) AS iv_pct,
       round(100 * avg(toFloat64(implied_volatility)) * sqrt(avg(days_to_expiry) / 365), 2) AS expected_move_pct,
       round(avg(toFloat64(underlying_close)) * avg(toFloat64(implied_volatility))
             * sqrt(avg(days_to_expiry) / 365), 2) AS expected_move_usd,
       round(avg(toFloat64(underlying_close)), 2) AS underlying_price,
       formatDateTime(max(date), '%b %e, %Y') AS as_of
FROM global_markets.options_greeks
WHERE underlying_symbol = 'AAPL'
  AND date = (SELECT max(date)
              FROM global_markets.options_greeks
              WHERE underlying_symbol = 'AAPL'
                AND date <= toDate('2026-07-15'))
  AND iv_converged = 1
  AND volume > 0
  AND days_to_expiry BETWEEN 1 AND 400
  AND abs(toFloat64(strike_price) / toFloat64(underlying_close) - 1) < 0.05
GROUP BY horizon
HAVING count() >= 3
ORDER BY avg_days
⌘/Ctrl + Enter

Work with this data in your AI assistant

Opens ready to query, with this page's data. Free, no account.

More from this analysisExpected Move From Implied Volatility
Implied vs realized: median 30-day expected move and what six stocks did next table 6×5 → NVDA after its late-May 2023 report: implied volatility and where the stock went series 12×6 → Implied versus realized earnings moves, large caps scored print by print table 13×8 → The ten widest overshoots: realized versus implied ranking 10×4 → NVDA: implied move both ways versus the realized move, report by report series 7×5 → Where the realized move landed relative to implied ranking 6×4 → See all 3,256 queries →