Apple, Tesla, NVIDIA and Microsoft stocks: real bars and the 25 October 2026 snapshot
AAPL, TSLA, NVDA and MSFT: real OHLC, a 9 October replay cutoff, latest available bars and conditional scenarios without an invented complete count.
Published: (UTC+3)
Русский · English · Deutsch · Español · Français · Italiano · 繁體中文 · 日本語 · 한국어
Apple/AAPL, Tesla/TSLA, NVIDIA/NVDA and Microsoft/MSFT identify four separate stocks here, not eight markets. We use real Yahoo Finance daily rows for 1–23 October 2026. The historical replay stops at 9 October; later observations are revealed separately. The 25 October snapshot uses the latest available completed bars of 23 October. This is a dated source study with conditional scenarios, not a recommendation or a demonstrated complete wave count, and it does not update automatically.
Instrument, source and corporate adjustments
All four series are Nasdaq equities in USD; the provider timezone is America/New_York. O/H/L/C mean open/high/low/close from the daily quote array, not current regularMarketPrice or after-hours prices. Yahoo labels Close as split-adjusted and Adj Close as also incorporating dividends/distributions. We do not substitute Adj Close into individual OHLC fields or apply old splits again. Source binary floats are normalized to 0.01 using ROUND_HALF_UP, with no other price transformation; original JSON is retained.
The events in the table are verifiable historical references outside the October 2026 window. They explain why a series basis needs checking, but do not replace actual bars or automatically explain their moves. With another provider, reconcile its entire OHLC and volume methodology. The fragment and boundaries were selected retrospectively: this is neither a forecast published on 9 October nor a trading backtest. Table V is provider-reported volume, not established participant identity or aggressor direction.
| Issuer / stock | Instrument | Currency | Historical event outside the window |
|---|---|---|---|
| Apple | AAPL | USD | 2020: 4:1 split |
| Tesla | TSLA | USD | 2022: 3:1 split |
| NVIDIA | NVDA | USD | 2024: 10:1 split |
| Microsoft | MSFT | USD | 2004: special cash dividend 3 USD; ex-date 15 November, paid 2 December |
Should October AAPL prices be divided by 4 again because of the 2020 split?
No. Establish the source basis first; adjusting already comparable data again would distort it. A historical event is not a new event in this window.
Apple / AAPL: real history with a separate later reveal
For Apple (AAPL), the historical replay ends at completed row 2026-10-09, C=336.64. Only earlier rows 2026-10-01–2026-10-08 define U=341.57 and L=325.81: U is their highest H and L their lowest L. The cutoff close remains inside that selected range. The selected local anchor H=341.57 on 2026-10-08 becomes checkable only after row 2026-10-09: our convention requires one completed neighboring bar on each side and a strictly more extreme value. This is a local price check, not a wave-number assignment.
Later rows are revealed separately without changing those historical boundaries. First later C>U: 2026-10-14 · C=342.96; first C<L: not observed in the retained continuation. These are observations through the last saved bar, not future promises. The window was chosen retrospectively, so the result is not a forecast genuinely published then or a trading return. Two dates matter: the 8 October H341.57 is checkable on the 9th, while the 9 October L330.70 is checkable only after the 12th. The low’s confirmation cannot be moved back to the 9th. The final H351.73 on 23 October has no completed right neighbor in our file yet.
| Instrument | Currency | Date | O | H | L | C | V | Availability relative to cutoff |
|---|---|---|---|---|---|---|---|---|
| AAPL | USD | 2026-10-01 | 330.00 | 332.48 | 325.81 | 330.32 | 36306300 | through cutoff inclusive |
| AAPL | USD | 2026-10-02 | 333.26 | 334.54 | 330.61 | 333.69 | 33278600 | through cutoff inclusive |
| AAPL | USD | 2026-10-05 | 332.82 | 336.21 | 331.65 | 332.89 | 34400900 | through cutoff inclusive |
| AAPL | USD | 2026-10-06 | 332.28 | 334.38 | 330.62 | 333.63 | 30449000 | through cutoff inclusive |
| AAPL | USD | 2026-10-07 | 336.96 | 338.67 | 332.78 | 336.67 | 34147900 | through cutoff inclusive |
| AAPL | USD | 2026-10-08 | 336.82 | 341.57 | 335.90 | 340.42 | 35332400 | through cutoff inclusive |
| AAPL | USD | 2026-10-09 | 331.70 | 338.61 | 330.70 | 336.64 | 37881200 | through cutoff inclusive |
| AAPL | USD | 2026-10-12 | 338.22 | 342.63 | 337.60 | 340.97 | 25900600 | later data separately |
| AAPL | USD | 2026-10-13 | 344.67 | 348.15 | 340.74 | 341.27 | 38983800 | later data separately |
| AAPL | USD | 2026-10-14 | 344.61 | 347.09 | 341.72 | 342.96 | 50061100 | later data separately |
| AAPL | USD | 2026-10-15 | 346.95 | 347.85 | 341.60 | 342.00 | 39767300 | later data separately |
| AAPL | USD | 2026-10-16 | 346.09 | 347.82 | 340.46 | 343.46 | 59946400 | later data separately |
| AAPL | USD | 2026-10-19 | 340.78 | 346.00 | 340.12 | 342.94 | 34573200 | later data separately |
| AAPL | USD | 2026-10-20 | 339.86 | 343.06 | 338.70 | 339.50 | 35851400 | later data separately |
| AAPL | USD | 2026-10-21 | 339.36 | 345.25 | 338.83 | 343.99 | 35614100 | later data separately |
| AAPL | USD | 2026-10-22 | 344.94 | 348.36 | 342.28 | 348.22 | 46898900 | later data separately |
| AAPL | USD | 2026-10-23 | 349.12 | 351.73 | 345.75 | 347.73 | 39496500 | later data separately |
At cutoff 2026-10-09, could a later close be used or a local anchor be treated as proof of a completed impulse?
No. Only rows through the cutoff are available; the selected anchor is known after 2026-10-09. A fixed-range break and internal 5–3–5–3–5 are different checks. Complete wave roles and degree remain unestablished.
Tesla / TSLA: real history with a separate later reveal
For Tesla (TSLA), the historical replay ends at completed row 2026-10-09, C=382.70. Only earlier rows 2026-10-01–2026-10-08 define U=383.33 and L=353.80: U is their highest H and L their lowest L. The cutoff close remains inside that selected range. The selected local anchor L=368.03 on 2026-10-08 becomes checkable only after row 2026-10-09: our convention requires one completed neighboring bar on each side and a strictly more extreme value. This is a local price check, not a wave-number assignment.
Later rows are revealed separately without changing those historical boundaries. First later C>U: 2026-10-21 · C=386.47; first C<L: not observed in the retained continuation. These are observations through the last saved bar, not future promises. The window was chosen retrospectively, so the result is not a forecast genuinely published then or a trading return. The 16 October bar has both a local H370.50 and L349.33 relative to its neighbors, checkable only after the 19th. OHLC does not reveal which extreme occurred first intraday. They cannot be joined as two supposedly ordered subwaves without finer data.
| Instrument | Currency | Date | O | H | L | C | V | Availability relative to cutoff |
|---|---|---|---|---|---|---|---|---|
| TSLA | USD | 2026-10-01 | 356.81 | 359.79 | 353.80 | 354.11 | 31080800 | through cutoff inclusive |
| TSLA | USD | 2026-10-02 | 360.08 | 374.60 | 359.41 | 370.59 | 55330100 | through cutoff inclusive |
| TSLA | USD | 2026-10-05 | 369.00 | 381.59 | 364.91 | 378.73 | 42232700 | through cutoff inclusive |
| TSLA | USD | 2026-10-06 | 381.98 | 383.33 | 378.52 | 380.68 | 27735400 | through cutoff inclusive |
| TSLA | USD | 2026-10-07 | 378.45 | 382.35 | 374.43 | 377.81 | 25594600 | through cutoff inclusive |
| TSLA | USD | 2026-10-08 | 374.12 | 375.96 | 368.03 | 375.00 | 28394900 | through cutoff inclusive |
| TSLA | USD | 2026-10-09 | 382.38 | 388.56 | 379.71 | 382.70 | 38952400 | through cutoff inclusive |
| TSLA | USD | 2026-10-12 | 382.61 | 382.70 | 377.58 | 378.03 | 20244300 | later data separately |
| TSLA | USD | 2026-10-13 | 372.33 | 377.05 | 371.30 | 375.23 | 18393000 | later data separately |
| TSLA | USD | 2026-10-14 | 371.16 | 371.39 | 363.82 | 367.16 | 31001400 | later data separately |
| TSLA | USD | 2026-10-15 | 360.57 | 363.75 | 355.23 | 362.44 | 26728300 | later data separately |
| TSLA | USD | 2026-10-16 | 369.15 | 370.50 | 349.33 | 354.72 | 62067300 | later data separately |
| TSLA | USD | 2026-10-19 | 357.50 | 369.58 | 354.47 | 368.06 | 38817900 | later data separately |
| TSLA | USD | 2026-10-20 | 370.28 | 377.59 | 363.64 | 373.71 | 32123300 | later data separately |
| TSLA | USD | 2026-10-21 | 381.43 | 388.84 | 380.51 | 386.47 | 48875800 | later data separately |
| TSLA | USD | 2026-10-22 | 374.29 | 388.86 | 373.71 | 374.58 | 51610900 | later data separately |
| TSLA | USD | 2026-10-23 | 373.20 | 377.32 | 365.27 | 372.22 | 34689700 | later data separately |
At cutoff 2026-10-09, could a later close be used or a local anchor be treated as proof of a completed impulse?
No. Only rows through the cutoff are available; the selected anchor is known after 2026-10-09. A fixed-range break and internal 5–3–5–3–5 are different checks. Complete wave roles and degree remain unestablished.
NVIDIA / NVDA: real history with a separate later reveal
For NVIDIA (NVDA), the historical replay ends at completed row 2026-10-09, C=229.28. Only earlier rows 2026-10-01–2026-10-08 define U=243.37 and L=228.16: U is their highest H and L their lowest L. The cutoff close remains inside that selected range. The selected local anchor H=243.37 on 2026-10-06 becomes checkable only after row 2026-10-07: our convention requires one completed neighboring bar on each side and a strictly more extreme value. This is a local price check, not a wave-number assignment.
Later rows are revealed separately without changing those historical boundaries. First later C>U: not observed in the retained continuation; first C<L: 2026-10-12 · C=226.32. These are observations through the last saved bar, not future promises. The window was chosen retrospectively, so the result is not a forecast genuinely published then or a trading return. The 6 October H243.37 is checkable after the 7th; the first later close below old L228.16 occurs on the 12th. In the latest snapshot C210.96 is also below the separate prior L211.26. These are two dated price facts, not proof of a completed five or the cause of the decline.
| Instrument | Currency | Date | O | H | L | C | V | Availability relative to cutoff |
|---|---|---|---|---|---|---|---|---|
| NVDA | USD | 2026-10-01 | 229.98 | 232.29 | 228.16 | 230.86 | 98591400 | through cutoff inclusive |
| NVDA | USD | 2026-10-02 | 236.06 | 237.88 | 233.60 | 233.95 | 135167800 | through cutoff inclusive |
| NVDA | USD | 2026-10-05 | 236.09 | 240.10 | 235.15 | 238.90 | 127171500 | through cutoff inclusive |
| NVDA | USD | 2026-10-06 | 242.10 | 243.37 | 238.93 | 239.24 | 101701900 | through cutoff inclusive |
| NVDA | USD | 2026-10-07 | 237.69 | 239.08 | 236.38 | 237.47 | 81772400 | through cutoff inclusive |
| NVDA | USD | 2026-10-08 | 234.92 | 237.07 | 229.85 | 230.48 | 118697400 | through cutoff inclusive |
| NVDA | USD | 2026-10-09 | 233.84 | 233.92 | 229.11 | 229.28 | 84645600 | through cutoff inclusive |
| NVDA | USD | 2026-10-12 | 228.73 | 228.86 | 224.90 | 226.32 | 70690300 | later data separately |
| NVDA | USD | 2026-10-13 | 224.34 | 228.64 | 223.06 | 228.52 | 84036900 | later data separately |
| NVDA | USD | 2026-10-14 | 225.53 | 226.00 | 219.64 | 221.30 | 118730100 | later data separately |
| NVDA | USD | 2026-10-15 | 215.30 | 218.47 | 212.85 | 217.23 | 127087900 | later data separately |
| NVDA | USD | 2026-10-16 | 216.56 | 218.68 | 213.32 | 214.13 | 121252500 | later data separately |
| NVDA | USD | 2026-10-19 | 218.10 | 219.62 | 214.70 | 217.09 | 98684700 | later data separately |
| NVDA | USD | 2026-10-20 | 215.98 | 218.46 | 212.77 | 216.47 | 79609100 | later data separately |
| NVDA | USD | 2026-10-21 | 220.96 | 222.19 | 217.66 | 221.97 | 87085700 | later data separately |
| NVDA | USD | 2026-10-22 | 217.13 | 218.88 | 211.26 | 212.21 | 125407600 | later data separately |
| NVDA | USD | 2026-10-23 | 210.99 | 213.85 | 210.18 | 210.96 | 79987200 | later data separately |
At cutoff 2026-10-09, could a later close be used or a local anchor be treated as proof of a completed impulse?
No. Only rows through the cutoff are available; the selected anchor is known after 2026-10-07. A fixed-range break and internal 5–3–5–3–5 are different checks. Complete wave roles and degree remain unestablished.
Microsoft / MSFT: real history with a separate later reveal
For Microsoft (MSFT), the historical replay ends at completed row 2026-10-09, C=535.07. Only earlier rows 2026-10-01–2026-10-08 define U=535.69 and L=512.17: U is their highest H and L their lowest L. The cutoff close remains inside that selected range. The selected local anchor L=518.79 on 2026-10-08 becomes checkable only after row 2026-10-09: our convention requires one completed neighboring bar on each side and a strictly more extreme value. This is a local price check, not a wave-number assignment.
Later rows are revealed separately without changing those historical boundaries. First later C>U: 2026-10-12 · C=541.15; first C<L: not observed in the retained continuation. These are observations through the last saved bar, not future promises. The window was chosen retrospectively, so the result is not a forecast genuinely published then or a trading return. After the first C541.15>535.69 on 12 October, price reaches H551.15 on the 13th, locally checkable after the 14th. Yet the latest C524.51 is below that early breakout level again. A historical break guarantees no lasting continuation and assigns no wave degree.
| Instrument | Currency | Date | O | H | L | C | V | Availability relative to cutoff |
|---|---|---|---|---|---|---|---|---|
| MSFT | USD | 2026-10-01 | 519.88 | 522.85 | 512.17 | 512.80 | 19731900 | through cutoff inclusive |
| MSFT | USD | 2026-10-02 | 519.39 | 522.50 | 513.66 | 517.53 | 17822300 | through cutoff inclusive |
| MSFT | USD | 2026-10-05 | 521.62 | 532.35 | 521.47 | 525.18 | 26604800 | through cutoff inclusive |
| MSFT | USD | 2026-10-06 | 531.68 | 535.69 | 528.78 | 529.30 | 21107500 | through cutoff inclusive |
| MSFT | USD | 2026-10-07 | 530.73 | 531.73 | 524.69 | 529.76 | 16790200 | through cutoff inclusive |
| MSFT | USD | 2026-10-08 | 529.81 | 533.51 | 518.79 | 522.61 | 20228700 | through cutoff inclusive |
| MSFT | USD | 2026-10-09 | 528.24 | 537.22 | 526.24 | 535.07 | 18500600 | through cutoff inclusive |
| MSFT | USD | 2026-10-12 | 537.53 | 542.74 | 535.70 | 541.15 | 18314900 | later data separately |
| MSFT | USD | 2026-10-13 | 544.64 | 551.15 | 543.06 | 543.45 | 23852000 | later data separately |
| MSFT | USD | 2026-10-14 | 545.27 | 545.75 | 532.54 | 533.69 | 22324300 | later data separately |
| MSFT | USD | 2026-10-15 | 533.32 | 541.13 | 531.22 | 539.44 | 24151200 | later data separately |
| MSFT | USD | 2026-10-16 | 541.31 | 543.82 | 524.43 | 529.05 | 24845700 | later data separately |
| MSFT | USD | 2026-10-19 | 528.70 | 535.57 | 528.06 | 533.52 | 17994900 | later data separately |
| MSFT | USD | 2026-10-20 | 533.91 | 534.21 | 525.84 | 531.87 | 14576000 | later data separately |
| MSFT | USD | 2026-10-21 | 529.44 | 533.28 | 525.02 | 532.95 | 13940100 | later data separately |
| MSFT | USD | 2026-10-22 | 533.14 | 533.60 | 520.30 | 521.08 | 21266600 | later data separately |
| MSFT | USD | 2026-10-23 | 517.75 | 525.77 | 515.70 | 524.51 | 13671500 | later data separately |
At cutoff 2026-10-09, could a later close be used or a local anchor be treated as proof of a completed impulse?
No. Only rows through the cutoff are available; the selected anchor is known after 2026-10-09. A fixed-range break and internal 5–3–5–3–5 are different checks. Complete wave roles and degree remain unestablished.
Stock rules: declare a testable count first
A ticker creates no special Elliott rules for Apple or Tesla. For the selected strict ordinary impulse on one price basis, first assign dated P0…P5 and inspect direction, internal 5–3–5–3–5 and parent context. In an advance, two does not return to P0, three exceeds P1 and is not shorter than both other motive legs, and four remains outside wave-one territory; reverse price inequalities for a decline. A diagonal has a separate definition. The table gives conditional checks, not a claim that these roles were found in the October data. Lengths here use one linear price currency; another scale requires a separate convention. L1=|P1−P0|; L3=|P3−P2|; L5=|P5−P4|.
One-neighbor local anchors do not establish subdivisions. If P5 is not yet chosen and available at the cutoff, the final length comparison is unavailable; do not invent a point. Do not adjust one convenient anchor for a corporate action while leaving others on the old basis. Compare the published real TWSE2330 case: 560>555 rejects that particular downward ordinary impulse, and a later decline cannot restore it. No complete assigned count is supplied for these four stocks: roles and degree remain unresolved despite verified prices and dates.
| Check | Up | Down | C state |
|---|---|---|---|
| 2 | P2>P0 | P2<P0 | P0…P5 roles unassigned; not established |
| 3 | P3>P1; L3≥min(L1,L5) | P3<P1; L3≥min(L1,L5) | P0…P5 roles unassigned; not established |
| 4 | P4>P1 | P4<P1 | P0…P5 roles unassigned; not established |
| 1…5 | 5–3–5–3–5 | 5–3–5–3–5 | P0…P5 roles unassigned; not established |
Can L1/L3/L5 comparison be skipped when the fifth endpoint is missing and the entire impulse marked confirmed?
No. Preserve “not established at the cutoff.” An unavailable check is not a passed check; other already observable violations can still be detected without waiting for five.
25 October 2026 snapshot: latest bars and boundary scenarios
As prepared on 25 October 2026, the last retained daily bar for these four stocks is 23 October. C comes from the OHLC array, not the changing current-quote field. Each instrument has its own U=max(H) and L=min(L) over 1–22 October, excluding the final bar. Do not transfer levels between companies. AAPL347.73, TSLA372.22 and MSFT524.51 are inside their prior ranges; NVDA210.96 is below its L211.26. These are actual states of selected price conditions, not established wave roles.
For the next completed bar retain three branches: C_new>U means investigate a developing advance; C_new<L means investigate a decline or corrective alternative; L≤C_new≤U leaves the selected range unresolved. These are boundary scenarios, not target prices or a probability forecast. Crossing U/L is no universal Elliott invalidation: a specific count needs its own anchors, degree and subdivisions. AAPL’s 23 October H351.73 exceeds U348.36, but C347.73 is below U: an intrabar breach differs from a close condition. New bars can change the picture; this saved snapshot is not rewritten retrospectively.
| Instrument | Date | C | U_(2026-10-01…22) | L_(2026-10-01…22) | C state |
|---|---|---|---|---|---|
| AAPL | 2026-10-23 | 347.73 | 348.36 | 325.81 | inside [L,U] |
| TSLA | 2026-10-23 | 372.22 | 388.86 | 349.33 | inside [L,U] |
| NVDA | 2026-10-23 | 210.96 | 243.37 | 211.26 | below L |
| MSFT | 2026-10-23 | 524.51 | 551.15 | 512.17 | inside [L,U] |
AAPL H is above U. Does that satisfy completed C>U and prove a third wave?
No: 347.73<348.36. Even a close beyond the boundary would establish only the selected price condition, not the entire structure.