Telegram RegisterThe public register of Telegram
Telegram profile photo for BET-M 33

Channel

BET-M 33

@team33_official

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

259subscribers

+68 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003180457696
TypeChannel
Username@team33_official
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/team33_official

Growth

1912592256 August 2026 — 191 subscribers7 August 2026 — 191 subscribers14 August 2026 — 196 subscribers21 August 2026 — 220 subscribers28 August 2026 — 225 subscribers5 September 2026 — 232 subscribers12 September 2026 — 259 subscribers6 August 202612 September 2026
7 measurements spanning 37 days, net +68. 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 181–269 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 19:42259+27
5 Sept 2026, 11:40232+7
28 Aug 2026, 15:34225+5
21 Aug 2026, 11:17220+24
14 Aug 2026, 20:04196+5
7 Aug 2026, 07:03191no change
6 Aug 2026, 14:37191first reading

Engagement

20 posts held, back to 26 May 2026the 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 28 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

103 reactions across 17 posts, in 16 distinct kinds. The most used accounts for 27.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2827.2%
2019.4%
😭1413.6%
👍87.77%
👀76.80%
👏65.83%
🤯43.88%
👌32.91%
👎32.91%
😁32.91%
😱21.94%
10.971%
🗿10.971%
😈10.971%
🤡10.971%
🥴10.971%

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 17 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 103 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 26 May 2026 to 28 July 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

28 Jul 2026, 19:22 UTC114 views3 reactionsread 7 August 2026
Photo

🤬 Не удается одолеть BAKS — уступаем со счетом 0:2 и падаем в нижнюю сетку Сразу же играем против TDK за выход в плей-офф. Права на ошибку больше нет. Прямая трансляция: ➡️ twitch.tv/mpkbk

😭3

28 Jul 2026, 17:10 UTC111 viewsread 7 August 2026
Photo

Уже в эфире матч против BAKS за выход в плей-офф MPKBK CIS LAN Season 6, залетай скорее: ➡️ twitch.tv/mpkbk

28 Jul 2026, 15:42 UTC108 views4 reactionsread 7 August 2026
Photo

✅ Забираем игру без особых сложностей! Теперь ждем матч за выход в плей-офф против победителя пары TDK — BAKS. ⏰ Старт — в 21:00 МСК

🔥3😈1

28 Jul 2026, 14:07 UTC112 views5 reactionsread 7 August 2026
Photo

🔥 Йоооу! Да-да, мы снова в турнирной гонке! ▶️ Летим играть групповой этап MPKBK CIS LAN Season 6. Прямо сейчас стартуем матчем против HTX — заходи на трансляцию и поддержи парней! ➡️ twitch.tv/kartash0v

4🤡1

19 Jun 2026, 20:34 UTC240 views5 reactionsread 7 August 2026
Photo

🫠 Пупупу… Уступаем Acend со счетом 0:2 и вылетаем с квалификаций Будем продолжать оттачивать свою отыгровку, вернемся сильнее

👌3🥴1😁1

19 Jun 2026, 17:36 UTC258 viewsread 7 August 2026
Photo

🔥 Врываемся в плей-офф закрытых квалификаций Stake Ranked Episode 3 матчем против Acend! 🗺 Мап-вето: 1. Acend removed Nuke 2. BET-M removed Overpass 3. Acend picked Inferno 4. BET-M picked Dust2 5. Acend removed Ancient 6. BET-M removed Anubis 7. Mirage was left over 👀 После небольшой турнирной паузы наконец-то возвращаемся на сервер и пробуем новые наработки ▶️ Залетай на трансляцию: ➡️ kick.com/watchfultv

15 Jun 2026, 19:04 UTC188 views3 reactionsread 7 August 2026
Photo

Пока в турнирном расписании небольшое затишье — разминаем голову интерактивами 🧠 ❓ Угадаешь карту по фрагменту?

3

27 May 2026, 20:01 UTC255 views9 reactionsread 7 August 2026
Photo

🚫 Отдаем болото и падаем от VP 2:0, вылетая с MPKBK CIS LAN Season 5

😭7👎1🗿1

Showing the 12 most recent of 20 posts we hold for @team33_official. 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

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.

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 12 September 2026 — this entry's latest reading, not the date you are reading this.

“BET-M 33” (@team33_official), 259 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/team33_official.

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.