Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Views per post sit far below this size band
1.9 average views per post against 2,589 subscribers — an engagement rate of 0.075%. Across the 54,164 registered channels in the same cohort — 1,000–3,162 subscribers, posting mainly in Russian — the middle half sit between 10.5% and 35.6%, with a median of 20.1%.
What this was computed from
Window
30 days (13 July 2026 – 12 August 2026)
Posts measured
16 of 16 published in the window (16 exact, 0 rounded by Telegram)
Views totalled
31
Mature posts only
0.073% over 9 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_low, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Growth
3 measurements spanning 4 days, net -22. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,586–2,614 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 13:18
2,589
-20
8 Aug 2026, 05:52
2,609
-2
7 Aug 2026, 13:33
2,611
first reading
Engagement
16 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
0.075%
avg views ÷ 2,589 subscribers
Avg views / post
1.9
16 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
16
of 16 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
16 (5 August 2026 – 7 August 2026)
Views total
31
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 13:33 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
✔️ Увидели продолжение снижения по INJ и пришли к третьей цели, закрываю сделку полностью!
ORDI — первую цель пробили! Зафиксировал 50% позиции
⚡️ Ещё одна ракета PUMP — забрали две цели! Фиксирую 75% позиции.
Забирай💵за регистрацию с KYC:
✖️ BingX 💰 Bybit
✔️ По JTO уверено пробили первую цель, закрыл 50% позиции. По INJ наблюдаем отличное снижение, думаю сегодня можем увидеть пробитие третьей цели.
Забирай💵за регистрацию с KYC:
✖️ BingX 💰 Bybit
BTCUSDT 💸
Прошлые ожидания реализовались точно по плану. Цена дошла до зоны 64 400 - 65 200$ и именно тут жду реакцию.
Покупатель показал свою слабость. Каждая попытка роста быстро поглощается продавцами. Нисходящий канал сохраняется и давление продолжается.
Сейчас жду продолжение снижения. Первая остановка в зоне имбаланса 63 200 - 63 600$. После отработки этой зоны ожидаю продолжение движения к основной цели 61 …
Showing the 12 most recent of 16 posts we hold for @Pro_Trading8. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 11 August 2026 — this
entry's latest reading, not the date you are reading this.
“Crypto Tiger | Тагир Каримов” (@Pro_Trading8), 2,589 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Pro_Trading8.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.
