6 measurements spanning 22 days, net +506. 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 74–737 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
29 Aug 2026, 10:06
658
-2
22 Aug 2026, 18:23
660
+1
15 Aug 2026, 16:06
659
+509
8 Aug 2026, 20:00
150
no change
8 Aug 2026, 09:55
150
-2
7 Aug 2026, 19:44
152
first reading
Engagement
11 posts held, back to 19 July 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
8.05%
avg views ÷ 658 subscribers
Avg views / post
53.0
1 post measured
Reaction rate
18.9%
reactions ÷ views · ER floor
Posts in window
1
of 11 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 6 August 2026
Posts held
11 (19 July 2026 – 6 August 2026)
Views total
53
Reactions total
10
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 20:00 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.
What this channel posts
Video runtime
17s
Average length
17s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
68 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 36.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5312416547019453223
25
36.8%
custom 5379930048478330552
17
25.0%
custom 5336775935075046915
7
10.3%
custom 5314558520224391484
6
8.82%
custom 5352833288786420388
6
8.82%
custom 5444963197733846783
4
5.88%
custom 5242313704267062371
2
2.94%
custom 5444946571915444568
1
1.47%
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 11 of the 11 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 68reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 19 July 2026 to 6 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.
Всем здравки, я живчик чуть ушел от сетей, немного отдохнул и проветрил голову на новые идеи и возможности, но пока стримы на паузе, нужно начать кайфовать от стримов и все в этом и есть залог успеха 🌟🌟
В целом за время пока был афк снова стал играть в дотку, как раз перед интом иногда был в гостях у стримеров, кто у кубахи узнавал салэмчик 😎😎
Какие-то идейки записывал в целом и по-тихоньку к этому идти по сути мне …
ебать а вы не приахуели там, как смешнявку и завозное вы хуй реакции ставите 😡
- а как МЕГА АНЛАК ТАКОГО УРОВНЯ ЧТО НИХУЯ СЕБЕ САМ БЕЗ БКШКИ МОГ СДЕЛАТЬ СЕБЕ БЕЙДЖИК НА ИНТ, а valve проебали мое письмо, так сразу смешно вам 🔫
спасибо за детство (из-за него только брал пепси)
ваще похуй кто Роналду или Месси главное они сделаю историю и всему есть конец, но, как обычно это бывает, когда заканчивается одна история, всегда начинается другая...
GOAT 🐐
нт старый 🤩
самый худший матч за чм....
пиздец скучный матч из-за стиля игры Испании играть в сухую еще и выгнали всех за кого болел. Хз кто там фанаты футбола и тд, но матч который был вчера у Франции он был прям ахуй похожее хотелось видеть на чм. Самое пиздатое 0 ударов в ворота за 120 минут у Аргентины 🥴
Испании красавцы только в том что вынесли всех на чм и забрали его по факту 😎😎
VAMOS ESPANO AND ARGENTINA
Showing the 11 most recent of 11 posts we hold for @farrwayy. 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 29 August 2026 — this
entry's latest reading, not the date you are reading this.
“FARRWAYY” (@farrwayy), 658 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/farrwayy.
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.
