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 16 September 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.
Growth
15 measurements spanning 50 days, net +449. 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,882–2,467 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
26 Sept 2026, 06:36
2,399
+189
15 Sept 2026, 06:39
2,210
+14
11 Sept 2026, 18:39
2,196
+21
7 Sept 2026, 09:36
2,175
+90
2 Sept 2026, 13:26
2,085
-10
30 Aug 2026, 12:09
2,095
-5
27 Aug 2026, 03:22
2,100
-4
24 Aug 2026, 03:44
2,104
+14
20 Aug 2026, 10:14
2,090
+52
17 Aug 2026, 16:35
2,038
+36
14 Aug 2026, 17:16
2,002
+53
11 Aug 2026, 01:11
1,949
-3
7 Aug 2026, 15:02
1,952
no change
7 Aug 2026, 14:47
1,952
+2
7 Aug 2026, 12:30
1,950
first reading
Engagement
11 posts held, back to 28 March 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
161 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 55.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
90
55.9%
👍
19
11.8%
🎉
17
10.6%
❤🔥
13
8.07%
🖕
6
3.73%
🤡
6
3.73%
🤮
4
2.48%
💩
3
1.86%
💋
2
1.24%
😢
1
0.621%
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 8 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 161 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 28 March 2026 to 3 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.
У нас плохие новости, разработчики раст хотят урезать функции Rust+ убрав из него магазины и маркеры событий. 😭
Что это значит для нас? После выхода обновы перестанут работать уведомления о спавне карго, нефтевышки, торговца, появлении нового магазина.
А еще все это время мы разрабатывали новую фичу чтобы предоставить удобный поиск по магазинам на сервере. Теперь этот функционал не будет работать вовсе.
Да, неприят…
Поздравляем всех победителей! 🥳
Сегодня-завтра вам напишет менеджер с тг который указан в описании этого канала и попросит ТОЛЬКО ТРЕЙД ССЫЛКУ или стим ид если вы выиграли подписку. Если вам кто-то будет писать, сверяйте тг.
rustradar.gg ❤️
🔔 Уведомление о рейде без электрики? — С RustRadar это возможно
Теперь вы можете активировать звонок в телеграм когда вас убьют в оффлайне. Например, вы можете лечь перед дверью, тем самым не пропустить рейд и не проснуться утром на пляже.
Мы назвали это БИЧ NOT RICH 😎
..ой мне за эту разработку такую премию дадут... или уволят
🎁 СКИДКА 60%
В связи с тем, что отслеживание игроков сейчас недоступно, но мы уже реш…
👁 RustRadar – Bug Fix
Недавно пользователи нашли баг связанный с задержкой получения уведомлений об игровых ивентах на сервере, мы нашли проблему и исправили, сейчас задержки минимальны.
Продолжаем улучшать сервис и добавлять новые функции для удобства игры. Если вы нашли баг или у вас есть предложение по развитию проекта то мы с радостью пообщаемся с вами в нашем дискорде
👁 RustRadar
RustRadar — HotFix направленный на улучшение работы сервиса
Теперь уведомления приходят в чат игры даже если владелец подписки оффлайн.
Для команд добавлен альтернативный префикс «.» — можно писать .pop | .help и т.д., на некоторых серверах префикс «!» уже занят другими плагинами
Добавили подсказку по использованию команд прямо в интерфейсе, !help/.help в чат.
Исправили обнаружение глубокого моря, раньше сервис…
👁️RustRadar — это веб‑платформа для мониторинга Rust‑серверов и активности игроков.
Возможности сервиса:
Оповещения о рейде
RustRadar сообщает тебе, когда тебя приходят рейдить: прилетают моментальные уведомления в игру и в Telegram/Discord, чтобы ты успел зайти и задефаться.
Это решает проблему «оффлайн рейда» — бот звонит почти сразу после первого взрыва.
Таймеры нефтевышек
Сервис отслеживает активацию нефтевышек…
Всем привет, как вас тут уже много.🫡
Поиск игроков и серверов временно не работает, решаем проблему.
Функционал касаемый уведомлений о ивентах, звонки при рейде работает.😄
Исправили: когда срабатывает уведомление о рейде, в чат, дс и тг пишет название аларма который вы задали в настройках.
https://rustradar.gg
🔔Мы запускаем розыгрыш на 50 ТЫСЯЧ РУБЛЕЙ в честь открытия RUST RADAR!
⭐️35 призовых мест:
1 место: AK Alien Red
2 место: After Death AR
3 место: AK-47 Victoria
4 место: AK Royale
5 место: AK Brass Lion
6 место: Phantom AK
7 место: Polymer SMG
8 место: Raven
9 место: Paint Rush SAP
10 место: Comics AR
11 место: Blackout Bow
12 место: Kiss AR
13 место: Cold Hunter LR 300
14 место: Comics SAR
15 место: Tempered AK47
1…
Showing the 11 most recent of 11 posts we hold for @rustradargg. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 6 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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@rustradargg named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@geowcv named in 1 post, 8 August 2026 – 8 August 2026
@marzekazka named in 1 post, 8 August 2026 – 8 August 2026
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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“RustRadar” (@rustradargg), 2,399 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/rustradargg.
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.