Both positions at four moments: entry, three weeks in, the SPY high, and the June dip

Name: Both positions at four moments: entry, three weeks in, the SPY high, and the June dip
Creator: Strasmore
Published: 2026-07-31
License: https://www.strasmore.com/terms/

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-07-31, from Covered Call vs Cash-Secured Put.

as of 2026-07-31 table 4×5read in context →

Both positions at four moments: entry, three weeks in, the SPY high, and the June dip — 4 rows by 5 columns, computed 2026-07-31 from US exchange, SIP and OPRA data.
stage	spy_price	covered_call_pl	cash_secured_put_pl	gap_abs
1. Both trades opened (May 1)	720	0	0	0
2. Three weeks in (May 15)	737.34	7.32	6.44	0.88
3. SPY high (Jun 2)	759.63	15.47	13.35	2.12
4. SPY dip (Jun 10)	722.88	7.59	6.45	1.14

Rows × columns: 4 × 5
Computed: 2026-07-31
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 Both positions at four moments: entry, three weeks in, the SPY high, and the June dip, derived from the stored result.
Column	Type	Range	Notes
`stage`	text	4 distinct values
`spy_price`	number	720 to 759.63	US dollars
`covered_call_pl`	number	0 to 15.47
`cash_secured_put_pl`	number	0 to 13.35
`gap_abs`	number	0 to 2.12

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 2026-07-31, 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.

WITH entry AS (
    SELECT avgIf(option_close, ticker = 'O:SPY260618C00720000') AS call0,
           avgIf(option_close, ticker = 'O:SPY260618P00720000') AS put0,
           avg(underlying_close) AS spy0
    FROM global_markets.options_greeks
    WHERE ticker IN ('O:SPY260618C00720000', 'O:SPY260618P00720000')
      AND date = '2026-05-01'
      AND implied_volatility > 0.02
)
SELECT multiIf(g.date = '2026-05-01', '1. Both trades opened (May 1)',
               g.date = '2026-05-15', '2. Three weeks in (May 15)',
               g.date = '2026-06-02', '3. SPY high (Jun 2)',
               '4. SPY dip (Jun 10)') AS stage,
       round(avg(g.underlying_close), 2) AS spy_price,
       round(avg(g.underlying_close) - any(entry.spy0) + any(entry.call0)
             - avgIf(g.option_close, g.ticker = 'O:SPY260618C00720000'), 2) AS covered_call_pl,
       round(any(entry.put0)
             - avgIf(g.option_close, g.ticker = 'O:SPY260618P00720000'), 2) AS cash_secured_put_pl,
       round(abs((avg(g.underlying_close) - any(entry.spy0) + any(entry.call0)
                  - avgIf(g.option_close, g.ticker = 'O:SPY260618C00720000'))
                 - (any(entry.put0)
                    - avgIf(g.option_close, g.ticker = 'O:SPY260618P00720000'))), 2) AS gap_abs
FROM global_markets.options_greeks g, entry
WHERE g.ticker IN ('O:SPY260618C00720000', 'O:SPY260618P00720000')
  AND g.date IN ('2026-05-01', '2026-05-15', '2026-06-02', '2026-06-10')
  AND g.implied_volatility > 0.02
GROUP BY g.date
ORDER BY g.date

SQL to run

WITH entry AS (
    SELECT avgIf(option_close, ticker = 'O:SPY260618C00720000') AS call0,
           avgIf(option_close, ticker = 'O:SPY260618P00720000') AS put0,
           avg(underlying_close) AS spy0
    FROM global_markets.options_greeks
    WHERE ticker IN ('O:SPY260618C00720000', 'O:SPY260618P00720000')
      AND date = '2026-05-01'
      AND implied_volatility > 0.02
)
SELECT multiIf(g.date = '2026-05-01', '1. Both trades opened (May 1)',
               g.date = '2026-05-15', '2. Three weeks in (May 15)',
               g.date = '2026-06-02', '3. SPY high (Jun 2)',
               '4. SPY dip (Jun 10)') AS stage,
       round(avg(g.underlying_close), 2) AS spy_price,
       round(avg(g.underlying_close) - any(entry.spy0) + any(entry.call0)
             - avgIf(g.option_close, g.ticker = 'O:SPY260618C00720000'), 2) AS covered_call_pl,
       round(any(entry.put0)
             - avgIf(g.option_close, g.ticker = 'O:SPY260618P00720000'), 2) AS cash_secured_put_pl,
       round(abs((avg(g.underlying_close) - any(entry.spy0) + any(entry.call0)
                  - avgIf(g.option_close, g.ticker = 'O:SPY260618C00720000'))
                 - (any(entry.put0)
                    - avgIf(g.option_close, g.ticker = 'O:SPY260618P00720000'))), 2) AS gap_abs
FROM global_markets.options_greeks g, entry
WHERE g.ticker IN ('O:SPY260618C00720000', 'O:SPY260618P00720000')
  AND g.date IN ('2026-05-01', '2026-05-15', '2026-06-02', '2026-06-10')
  AND g.implied_volatility > 0.02
GROUP BY g.date
ORDER BY g.date

⌘/Ctrl + Enter

Work with this data in your AI assistant

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

Claude ChatGPT Gemini Muse Your own agent

More from this analysisCovered Call vs Cash-Secured Put

Covered call vs cash-secured put: profit and loss per share, same strike, same expiry series 29×3 → What each strike paid on May 1, 2026: SPY June 18 calls and puts side by side ranking 8×3 → Three years of total return, split into price change and distributions: July 2023 to June 2026 table 8×7 → Price path indexed to 100: two index funds and their covered call counterparts, month ends series 36×5 → Total return by calendar year: a Nasdaq index fund vs a Nasdaq covered call fund ranking 4×3 → The wheel pair at entry, the SPY peak, the dip, and the final session table 4×5 → See all 3,256 queries →