Bitcoin · Closed candles only
BTC: Wyckoff markup — accumulation, distribution and phases
BTC now: 1H — distribution, phase A; 4H — no range; 1D — no range.
Scanner snapshot: . Latest event: .
Latest available closed candles: 1H: ; 4H: ; 1D: .
Instrument panel
Event history over 30 days
Instrument rows: 8. Candle close time in MSK; UTC is available in the tooltip.
| When | TF | Event | Phase | Outcome |
|---|---|---|---|---|
| 1H | LPS | D | cancelled | |
| 1H | LPS | D | cancelled | |
| 1H | SOS | D | cancelled | |
| 1H | Range closed | C | range went stale | |
| 1H | LPS | C | no result | |
| 1H | Range closed | B | range went stale | |
| 1H | Range closed | C | invalidation | |
| 1H | UTAD | C | invalidation |
Two-year statistics
Event types and timeframes are counted separately. n includes completed outcomes only; cancelled and waiting events are excluded. Shares are withheld when n < 20.
2024-10-01 — 2026-10-01. Using available scanner history; no observations does not mean zero probability.
| TF | Type | n | Target | Invalidation | No result | Cancelled / waiting |
|---|---|---|---|---|---|---|
| 1H | Spring | 22 | 27.3% | 59.1% | 13.6% | 6 / 0 |
| 1H | UTAD | 21 | 23.8% | 71.4% | 4.8% | 6 / 0 |
| 1H | Test | 31 | 32.3% | 0.0% | 67.7% | 1 / 0 |
| 1H | LPS | 7 | Insufficient data | 6 / 0 | ||
| 1H | LPSY | 6 | Insufficient data | 1 / 0 | ||
| 1H | SOS | 4 | Insufficient data | 5 / 0 | ||
| 1H | SOW | 5 | Insufficient data | 1 / 0 | ||
| 4H | Spring | 6 | Insufficient data | 0 / 0 | ||
| 4H | UTAD | 7 | Insufficient data | 1 / 0 | ||
| 4H | Test | 12 | Insufficient data | 0 / 0 | ||
| 4H | LPS | 4 | Insufficient data | 0 / 0 | ||
| 4H | LPSY | 1 | Insufficient data | 0 / 0 | ||
| 4H | SOS | 1 | Insufficient data | 0 / 0 | ||
| 4H | SOW | 1 | Insufficient data | 0 / 0 | ||
| 1D | Spring | 1 | Insufficient data | 0 / 0 | ||
| 1D | UTAD | 1 | Insufficient data | 0 / 0 | ||
| 1D | Test | 2 | Insufficient data | 0 / 0 | ||
| 1D | LPS | 0 | Insufficient data | 0 / 0 | ||
| 1D | LPSY | 0 | Insufficient data | 0 / 0 | ||
| 1D | SOS | 0 | Insufficient data | 0 / 0 | ||
| 1D | SOW | 0 | Insufficient data | 0 / 0 | ||
Reading BTC markup
Bitcoin is easier to read through changes of market regime than through attempts to nominate the next low in advance. BTC belongs to the cryptocurrency group on this page. Its market clock runs continuously, so midnight does not represent a stock exchange closing auction. A brief impulse inside a broad corridor and a departure from that corridor are different events. The hourly view exposes the sequence of tests, while four-hour candles help show whether an area survives several moves. Daily markup remains independent rather than inheriting a lower-timeframe phase.
The useful distinction for BTC is between a large price move and an actual structural transition. Acceleration on substantial volume may end in a return, whereas a modest second visit to the boundary can be more informative than the first long candle. Bitcoin is compared with its own history and its own range here. Ethereum percentages cannot be transferred to BTC merely because their charts look similar. When the current row reports no range, an old spring does not turn the present trend into accumulation. Previous events retain their timestamps and outcomes in history; a new structure starts only when the scanner conditions are met.
The server view for BTC: 1H — distribution, phase A; 4H — no range; 1D — no range. Available instrument history contains 8 rows over 30 days; 132 completions across separate two-year samples. The opening line records the snapshot state rather than a forecast. Compare its time with the latest event time: an old label does not become current merely because no newer event exists. Each Bitcoin scale keeps an independent phase, and no range does not mean distribution. Numbers can change after another close, so retain the observation date when reviewing an example.
The BTC panel reads the same candles as the general scanner. Switching scale does not change the data provider. A candle obtains its final value after it closes; later bars can finish the working area or cancel a dependent label. In the Bitcoin view, compare boundaries with the actual close rather than just a wick. An educational schematic explains phase order, but it does not depict real prices from the selected day.
BTC statistics have a separate n for each code and scale. The three shares distinguish target completion, invalidation and completion without a result. Waiting observations are not yet included in the denominator; cancellation stays in history but is excluded as well. Below twenty Bitcoin completions, insufficient data replaces percentages. Another market’s sample does not enlarge this one. Several dependent events must not be read as independent promises of a return.
Bitcoin has real market volume from this feed, not the sum of arbitrary external venues. When studying BTC, compare the same code and scale while recording the date and final status. The online chart provides Bitcoin price context; Magnitude helps describe movement size but does not independently confirm a Wyckoff phase. From this page you can return to the general scanner, open the atlas and explore the method. This route connects an explanation with an observation without turning an educational drawing into a signal.
FAQ
Why does the BTC phase differ between scales?
Each BTC timeframe is marked independently using closed candles. Available scales are 1H, 4H, 1D. A missing structure is not copied from another scale.
What does BTC volume mean?
This is real market volume from Bitcoin feed candles, not the combined activity of every external venue or network operation.
Why are BTC event percentages missing?
Each event type and timeframe requires at least 20 completed outcomes. Waiting and cancelled observations are excluded from n; a smaller sample is labelled insufficient data.