Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 the other topics.
Growth
87 measurements spanning 96 days, net +3,887. 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 7,783–12,955 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 87
Measured (UTC)
Subscribers
Change
11 Nov 2026, 01:27
12,267
+6
10 Nov 2026, 13:48
12,261
-2
9 Nov 2026, 08:35
12,263
no change
9 Nov 2026, 03:16
12,263
+1
7 Nov 2026, 23:56
12,262
no change
7 Nov 2026, 20:59
12,262
+7
6 Nov 2026, 22:08
12,255
no change
6 Nov 2026, 21:20
12,255
+2
5 Nov 2026, 21:20
12,253
no change
5 Nov 2026, 18:41
12,253
-12
4 Nov 2026, 22:00
12,265
+3
4 Nov 2026, 16:11
12,262
+10
4 Nov 2026, 00:00
12,252
+2
3 Nov 2026, 17:47
12,250
+14
3 Nov 2026, 00:48
12,236
+3
2 Nov 2026, 14:26
12,233
no change
2 Nov 2026, 02:47
12,233
+15
1 Nov 2026, 12:25
12,218
+17
1 Nov 2026, 04:29
12,201
+6
31 Oct 2026, 13:28
12,195
first reading
Engagement
11 posts held, back to 1 September 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 49 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
37.1%
avg views ÷ 12,267 subscribers
Avg views / post
4,550
1 post measured
Reaction rate
0.088%
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 30 October 2026
Posts held
11 (1 September 2025 – 30 October 2026)
Views total
4,550
Reactions total
4
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 08:45 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
Photos
8
Links
9
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
547 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 53.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👎
294
53.7%
👍
153
28.0%
🎉
42
7.68%
🗿
33
6.03%
😁
25
4.57%
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 10 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 547 reactions 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 1 September 2025 to 30 October 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🎁 Еженедельные розыгрыши Stark Helper!
Теперь каждую субботу мы будем разыгрывать 10 ключей Stark Helper на 15 дней среди участников дискорд-сервера!
Как принять участие?
Просто нажмите кнопку «Участвовать» в канале розыгрыши. Никаких дополнительных условий!
🏆 Итоги каждую субботу в 17:00 по МСК. Бот случайным образом выберет 10 победителей и отправит им ключи в личные сообщения.
Первый розыгрыш уже завтра, 31 окт…
🏆 Итоги конкурса идей
Конкурс завершён! Спасибо всем, кто отправлял свои предложения - часть из них уже принята и будет реализована в Stark Helper.
Первые 3 места получат ранее оговорённые призы:
🥇 место - Stark Helper на 365 дней + 1000 коинов
🥈 место - Stark Helper на 90 дней + 500 коинов
🥉 место - Stark Helper на 30 дней + 200 коинов
Также решили наградить всех остальных участников, у которых была принята хотя …
💡 Предлагай идеи - получай баллы
Теперь предложить идею для Stark Helper можно прямо через бота - раздел находится в главном меню. За каждую принятую идею вы будете получать баллы. В будущем они автоматически конвертируются в валюту на сайте.
А пока система баланса ещё готовится, запускаем конкурс идей!
До конца 31 августа топ-3 пользователей по количеству принятых идей получат:
🥇 место - Stark Helper на 365 дней +…
💰 Premium-роль в Discord
Для всех игроков с активной лицензией Stark Helper теперь доступна роль Premium на нашем Discord сервере
Как получить роль:
1. Привяжите Discord на сайте: Профиль → Настройки → Публичность
2. Введите команду /verify в чате Discord сервера
⭐️ Что даёт Premium?
Владельцам роли доступна приоритетная техническая поддержка в Discord.
Отдельный текстовый и голосовой канал.
Роль автоматически пр…
✨ Проблемы с антивирусом
С момента открытия многие пользователи сталкиваются с жалобами антивируса и удалением файлов во время установки Stark Helper.
Мы уже направили основные силы на решение этой проблемы. В ближайшее время количество ложных срабатываний должно сократиться.
До выхода исправления рекомендуем добавить файлы мода в исключения антивируса. В крайнем случае антивирус можно временно отключить на время ус…
✨ Обновление
1. HolyWorld Helper
В связи с изменением правил сервера HolyWorld мы добавили новую возможность в функцию HolyWorld Helper - отображение нимба над игроками, находящимися под эффектом невидимости.
Функция не нарушает правил сервера, игроков под невидимостью сквозь блоки вы не увидите.
2. Event Notifier
С вайпом на сервере HolyWorld добавили новый ивент Куб, который уже доступен в Event Notifier. Отображ…
🔒 Stark Helper - Старт проекта!
😭 Не исключаем возможность появления различных багов, о которых сообщить вы можете в нашу тех. поддержку. На открытии мод доступен только на версии Fabric 1.16.5. Приятной игры!
🔗 Полезные ссылки:
∟ Бесплатная версия мода
∟ ТГК Stark Helper
∟ Сайт РФ | Сайт СНГ
∟ Discord (Тех. поддержка)
#starkclient #starkhelper
🔒 Stark Helper - Закрытое бета тестирование уже в это воскресенье!
🔎 Проверим все ключевые функции и убедимся, что Ваш игровой помощник работает стабильно. Исправим возможные ошибки и подготовим продукт к полноценному запуску.
🔗 Полезные ссылки:
∟ Телеграм Бот
∟ ТГК Stark Helper
∟ Сайт РФ | Сайт СНГ
∟ Discord (Тех. поддержка)
#starkclient #starkhelper
Showing the 11 most recent of 11 posts we hold for @stark_client. 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.
Posts edited after publishing
@stark_client edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
19 August 2026
Most recent edit
19 August 2026
Mentions
Named by 4 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 11 November 2026 — this
entry's latest reading, not the date you are reading this.
“Stark Client” (@stark_client), 12,267 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/stark_client.
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.