Sunday 27 September 2026 · data as of the 27 Sep · 12:30 check · all times UTCPractice only · no trades are placed

Receipts

What crypto analysts said, what the market showed when they said it, and what happened next.

All calls · @CryptoMichNL's record

@CryptoMichNL on BTC

Waiting for a price no evidence at posting latest BTC price before the post: $83,908.98 at 25 Sep · 16:41, not used

27 Sep · 09:17
Essentially, there's only one level that #Bitcoin needs to break, and then, once again, we'll continue to grind higher. That's the $84,800. If that breaks, I think that we'll see a continuation towards the $90,000 levels.
2 levels on one axis

Levels against price

$84,800trigger $90,000target
Linear price axis, $84,488.00 to $90,312.00.

2 levels stated

BTC bull

Written as
“#Bitcoin”
Conviction
firm
Kind
forward call
Status
Waiting for a price
Levels exactly as written; the reading is shown where it isn't obvious
RoleLevel as writtenTimeframe
trigger $84,800 = $84,800.00 —
target $90,000 = $90,000.00 —
2 reasons stated

Why the analyst said it

  • there's only one level that #Bitcoin needs to break, and then, once again, we'll continue to grind higher
  • If that breaks, I think that we'll see a continuation towards the $90,000 levels

Not checked: there is no priced market evidence from the moment this was posted.

snapshot 27 Sep · 09:30

At posting no evidence at posting

RYO did not return market data when the post was seen.

Snapshot
27 Sep · 09:30 (12 min after the post)
Price
unavailable
RSI (14)
unavailable
Regime
unavailable
Fear & Greed
unavailable

What failed: analyze_token: upstream data unavailable: couldn't analyze BTC right now; market_overview: cached response from 2026-09-27T09:15:07.975484+00:00, older than 120s

last check 27 Sep · 12:30

Since posting Waiting for a price

Waiting for the first observed price.

Monitoring from
—
Baseline
not yet observed
Horizon ends
11 Oct · 09:17
Last check
27 Sep · 12:30

What was observed

  1. 27 Sep · 09:30No price: RYO market data unavailable

Checked every quarter-hour; a move between checks can be missed.

sha256

Where this came from

source x_api · sha256 01c5d0fba6f70abc… · claim 2104138474291077237#0