Telegram RegisterThe public register of Telegram
Telegram profile photo for TM CODER

Channel

TM CODER

@not_prob2022

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

206subscribers

-420 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001468355978
TypeChannel
Username@not_prob2022
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/not_prob2022

Topic

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 34% 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

2066944507 August 2026 — 626 subscribers8 August 2026 — 626 subscribers16 August 2026 — 633 subscribers24 August 2026 — 657 subscribers31 August 2026 — 689 subscribers10 September 2026 — 694 subscribers26 September 2026 — 686 subscribers7 October 2026 — 206 subscribers7 August 20267 October 2026
8 measurements spanning 61 days, net -420. 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 133–767 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 12:20206-480
26 Sept 2026, 02:36686-8
10 Sept 2026, 09:39694+5
31 Aug 2026, 15:09689+32
24 Aug 2026, 14:27657+24
16 Aug 2026, 17:13633+7
8 Aug 2026, 01:26626no change
7 Aug 2026, 09:18626first reading

Engagement

20 posts held, back to 4 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 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥466.7%
👍233.3%

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 4 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 6 reactions 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 4 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.

Recent posts

6 Aug 2026, 20:10 UTC5 viewsread 7 August 2026

👌Практически все хай-тир подарки растут в цене! 🎁Plush Pepe +0.84%📤 🎁Heart Locket -1.29%📥 🎁Durov’s Cap +3.94%📤 🎁Precious Peach +2.47%📤 🎁Heroic Helmet +4.72%📤 🎁Nail Bracelet +5.17%📤 🎁Loot Bag +10.77%📤 🎁Mini Oscar +4.76%📤 📈Рыночная капитализация всех подарков так же выросла на +10% и составляет $155 846 288

3 Aug 2026, 22:39 UTC12 viewsread 7 August 2026

На бот доступно распродажа до 05.08.26 17:00

3 Aug 2026, 22:39 UTC12 viewsread 7 August 2026

На бот распродажа всего за 99 руб в месяц 🛡

2 Aug 2026, 07:50 UTC19 viewsread 7 August 2026
Photo

Друзья узнайте Boss VPN 🤝 С дешёвым ценам 54 руб на месяц и без нормальной скорости до 1мб/с🙁 Мне после это многих написал что вернись деньги впн плохо работает но я ва сказал ещё мы работаем над этом вот мы исправили с @spidervpnn_bot ⚔️ Скорость до 60мб/с с лучший ценам обход белый список лучший подключение и лучший скорость попробуйте с нашей впн и скажите свой мнение @I_am_Muslim_boy всем спасибо ❤️

30 Jul 2026, 20:01 UTC26 views1 reactionsread 7 August 2026

Друзья хочу вам сказать теперь доступно с 1 подписка можно использовать 4 человек 🛡 Оплачивай 200 рублей и используй с родителями 😉

🔥1

25 Jul 2026, 10:18 UTC36 views1 reactionsread 7 August 2026
Photo

👨‍💻 Новое обновление в @Bosstmbot! 😎 Теперь доступны новые способы оплаты: 📱Steam 😵‍💫 Roblox ⚡️ Быстро, удобно и безопасно. Пополняйте любимые сервисы без лишних сложностей! 🤖 @Bosstmbot

🔥1

21 Jul 2026, 17:38 UTC36 viewsread 7 August 2026
Photo

🌡 Теперь доступно ещё больше способов подключения в SpiderVPN! 🕷 Подключение через Happ 🦂 Подключение к другим Proxy-серверам 🕸Быстрое подключение по QR-коду 🕷 Простая настройка всего за несколько секунд 🌿 Стабильное, быстрое и безопасное соединение 😎 Подключайтесь удобным для вас способом уже сегодня! 💻 @Spidervpnn_bot

21 Jul 2026, 15:17 UTC25 viewsread 7 August 2026
Photo

🔒 VPN-и зуд ва боэътимод ✔️ Дастрасии бемаҳдуд ба ҳамаи сомонаҳо ва барномаҳо 🤕 Суръати баланд ва пайвасти устувор 🛠Маълумоти шахсии шумо боэътимод муҳофизат карда мешавад 👉Дастгирии Android, iPhone, Windows ва дигар дастгоҳҳо 🛡 Пайвастшавии осон ва дастгирии 24/7 🌍 Аз интернет озодона ва бехатар истифода баред! @Spidervpnn_bot 🕸

20 Jul 2026, 12:30 UTC30 viewsread 7 August 2026
Photo

🧸 Чемпионат мира по футболку закончился — а мишка остался! В честь чемпионата мира по футболу в США вышел новый подарок. Он доступен к покупке в нашем боте. ⭐️ Покупайте звёзды на 30% дешевле, чем в Telegram! Пропишите /start для покупки.

18 Jul 2026, 03:11 UTC27 views2 reactionsread 7 August 2026

На Регион Санкт-Петербург ещё не доступно интернет🙂 Но с нашей впн все отлично работает @Spidervpnn_bot 🛰

👍2

Showing the 12 most recent of 20 posts we hold for @not_prob2022. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“TM CODER” (@not_prob2022), 206 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/not_prob2022.

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.