3 measurements spanning 15 days, net +1. 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 24–25 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 23:56
25
+1
11 Aug 2026, 11:02
24
no change
7 Aug 2026, 15:58
24
first reading
Engagement
10 posts held, back to 1 June 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
684.0%
avg views ÷ 25 subscribers
Avg views / post
171
1 post measured
Reaction rate
0.585%
reactions ÷ views · ER floor
Posts in window
1
of 10 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 1 August 2026
Posts held
10 (1 June 2026 – 1 August 2026)
Views total
171
Reactions total
1
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Aug 2026, 11:02 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
35 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 57.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
20
57.1%
💋
4
11.4%
🔥
4
11.4%
🕊
4
11.4%
🤝
2
5.71%
🤗
1
2.86%
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 9 of the 10 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 35reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 1 June 2026 to 1 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.
Отчет за июль
Много что произошло в ирл. Время торговле не удалось уделить достаточно. В начале месяца бегал по врачам, потом куча дней рождений и поездка. Только последнюю неделю месяца удалось отсидеть не выходя из дома
Несмотря на это по цифрам месяц неплохой. Удалось лутануться на уровне рекордного мая. К сожалению довольно активно выводил деньги, поэтому деп с начала лета стоит на месте.
Что касается самой то…
Отчет за последние 2 недели
Июль идет пободрее, чето удается крабить. В начале месяца получилось забрать на алгосе по TA. Ну а в остальном продолжают подкармливать листинги акций
Со здоровьем вроде чуть подразрулилось. Конечно еще надо будет побегать по врачам. Однако судя по всему заболевание не особо страшное
Отчет за июнь
В первый день месяца была хорошая активность и удалось что-то взять. Дальше активность потихоньку начала скатываться и в середине месяца совсем сдохла. Что-то снова ходить начало к концу месяца, но я совсем выпал из ритма и до сих пор не могу нормально вернутся в торговлю. Пока что продолжаю кликать на лоу пачку
В июне также навалились проблемы со здоровьем, из-за чего весь месяц бегал по врачам. Пока…
Отчет за последние 2 недели
Рынка особо не было сидим в пиве. Те немногочисленные ситуации с алгосами, которые всё-таки были, ебали жестко. К тому же у меня началась какая-то хуйня со здоровьем, из-за чего приходится бегать по врачам, что очень сильно сбивает концентрацию с рынка
Финрез: -73$ (с кб+OKX)
Отчет недели
В основном лутал акции, алгосов. Вола на LAB получилась средне, но в общем и целом в плюс. Отдал почти 50 баксов на листинге BTW
Финрез с кб где-то 260$
Отчет за май
Пробил косарь на депе, и по сути удалось выполнить намеченную цель на месяц
Первая половина мая прошла довольно спокойно, рынок не радовал ситуациями. Основной порфит налутал за две последние недели. В основном продолжаю выдрачивать алгосов и локальные темки. Однако и глобальные инплеи удалось в общем закрыть в стабильный плюс. Единственное что не получалось в этом месяце это ножи и заточки, правда в э…
Отчет недели
Достаточно активная неделя. В основном торговля алгосов и акций. Также были масштабные ситуации по типу ESPORTS и GUA. GUA я пропустил, ESPORTS отторговал средне
Больше половины профита сделал на OKX на акциях. Благодаря чему удалось поставить рекорд за неделю
Финрез: 230$ бин с кб + 257$ ОКХ = 487$
❤5
Showing the 10 most recent of 10 posts we hold for @goodboy1300s. 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 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“Крипта Goodboy” (@goodboy1300s), 25 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/goodboy1300s.
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.