4 measurements spanning 6 days, net +344. 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 1,992–2,461 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 09:59
2,390
-17
10 Aug 2026, 10:31
2,407
+261
7 Aug 2026, 15:31
2,146
+100
6 Aug 2026, 23:16
2,046
first reading
Engagement
20 posts held, back to 26 May 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 2 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
35.7%
avg views ÷ 2,390 subscribers
Avg views / post
854
4 posts measured
Reaction rate
3.37%
reactions ÷ views · ER floor
Posts in window
4
of 20 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 4 August 2026
Posts held
20 (26 May 2026 – 4 August 2026)
Views total
3,414
Reactions total
115
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 16:55 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.
Reaction mix
547 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 35.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
193
35.3%
❤
164
30.0%
👎
98
17.9%
🌚
92
16.8%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 547reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 26 May 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🩸 #OP
По OP зона предложения начинает отрабатывать — постепенно получаем движение вниз. Поэтому пока приоритет здесь остаётся за шортом.
Цель — район 0.086, где находится наша зона спроса и ликвидность с точки №1. Доходим туда, снимаем ликвидность и уже после этого повторно оцениваем реакцию цены.
🌟JohnnieTrade
💎 #TON/GRAM
По GRAM была попытка развернуться и продолжить локальный лонг, но актив всё ещё выглядит слабо. Пришли в район 1.514, смягчили нашу зону проторговки и получили хорошую реакцию вниз. Поэтому сейчас жду продолжение шорта к 1.40, где находится ликвидность. После её сбора уже будем оценивать дальнейшую реакцию цены.
🌟JohnnieTrade
🕸 #NEAR
По NEAR по-прежнему рассматриваю исключительно сценарий продолжения снижения. Цена находится на текущих уровнях, при этом общий тренд остаётся уверенно нисходящим. Зона предложения уже частично отработана, что открывает пространство для дальнейшего движения вниз.
Пока структура не демонстрирует признаков разворота, приоритет сохраняется за шортовыми позициями.
🌟JohnnieTrade
#ZORA
По ZORA глобально сохраняется полноценное нисходящее движение, а сверху сформирована хорошая цепочка предложения. Сейчас жду небольшую коррекцию примерно к 0.0068, где цена сможет снять ликвидность с точки №1.
Уже от этой области буду рассматривать продолжение снижения. Лонги здесь пока неинтересны — приоритет остаётся исключительно за шортом.
🔻 #TRX
По TRX сценарий также отработал практически идеально: цена пришла в зону спроса, сняла ликвидность с первой отметки и постепенно начала восстанавливаться. Пока реакция выглядит сдержанной, поэтому спешить с входом не вижу смысла.
В целом глобальная структура остаётся лонговой. Сейчас в приоритете увидеть уверенное движение к 0.3270. Если в этой области получим подтверждение, тогда уже можно будет рассматрива…
#NOT
По Notcoin нисходящий тренд по-прежнему остается в приоритете — сверху уже сформировалась сильная зона предложения. Оптимальным сценарием выглядит локальный импульс вверх для снятия ближайшей ликвидности, после чего можно будет искать точку входа в шорт.
Основная цель по этому сценарию — движение ниже отметки 0.00036.
🌟JohnnieTrade
💢 #DOT
По DOT глобальная структура по-прежнему остается шортовой. В ближайшее время ожидаю локальный откат вверх — ориентировочно в диапазон 0.847–0.85, где находится зона предложения и скопление внутренней ликвидности.
Именно от этой области будет интересно наблюдать за реакцией цены. Если продавцы подтвердят контроль, следующим сценарием станет продолжение нисходящего движения. Пока план остается без изменений: с…
🪙 #BTC
По биткоину пришли в нашу зону проторговки, теперь внимательно наблюдаем за реакцией цены. Пока не спешу открывать позиции. К тому же сегодня суббота, поэтому рассчитывать на сильные движения в течение дня, скорее всего, не стоит.
🌟JohnnieTrade
🪙 #BTC
Биткоин вместе с остальным рынком уверенно отработал снижение к области 59 000, где покупатели дали заметную реакцию. Сейчас внимание сосредоточено на двух ключевых зонах, от которых может сформироваться новое движение вниз.
Первая важная область — 61 600–62 100, и в данный момент цена находится именно в этом диапазоне. Спешить с открытием позиций здесь не стоит: необходимо дождаться четкой реакции рынка. Дл…
Showing the 12 most recent of 20 posts we hold for @JohnnieTrade. 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.
Citation-graph rank
Citation-graph rank — 912,310 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 5 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
“JohnnieTrade” (@JohnnieTrade), 2,390 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/JohnnieTrade.
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.