Channel
@d1mitsquad
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
15subscribers
-4 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003982121292 |
|---|---|
| Type | Channel |
| Username | @d1mitsquad |
| Created | Between 1 April 2026 and 20 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 13 October 2026 |
| On Telegram | t.me/d1mitsquad |
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 1 October 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 04:35 | 15 | -1 |
| 18 Aug 2026, 00:42 | 16 | -3 |
| 11 Aug 2026, 17:46 | 19 | no change |
| 11 Aug 2026, 10:18 | 19 | first reading |
18 posts held, back to 20 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 18 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
12 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 58.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 58.3% | |
| 😢 | 3 | 25.0% | |
| ❤🔥 | 2 | 16.7% |
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 9 of the 18 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 20 July 2026 to 2 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.
Сыграли турнир , проиграли против J4E😫! Очень обидно было проиграть ,особенно когда твоя команда взяла 8:11 и проиграла . Типы правда были очень сильными ,к тому же это опыт ,но 2 карта дала о себе знать против кого мы играем . Ну ,что ж нт парням и надеемся в следующем турнире мы дойдем до 1/2, но для этого нужна командная игра ,которой у нас не было опять(. MVP: D1fyz #GgD1mit
😢1
Завтра команда пойдет на турнир , пожелаем им удачи и надеемся на то,что мы хотя-бы дойдем до 1/4)
Сыграли прак против академии 12kbr ( основа у них TYMIN ).Мы выиграли даже не потея ,им нужно было тренировать аим и распик ,но наши ребята все равно взяли вверх над ними. MVP: Nort1s #GgD1mit
❤1
Клан D1mit Squad ищет праки на : 17:00 мск (Бо1 бриз)✅ 18:00 мск (Бо1 дюна)✅ 19:00 мск (Бо1 сенд)✅ ✅-свободно ❌-занято
❤2
Они решили взять реванш , собрали сильный состав ,даже показалось ,что там софт🫥. Если б ихний лд не собрал состав из лег мы бы выиграли снова этот прак ,но мы проиграли из-за того,что не было командной игры . MVP: D1fyz #GGD1mit
😢2
Сыграли прак против TWMIN , они очень были агрессивными в чате:/,но им не помогло это выиграть ,а даже придало нам сил сыграть еще лучше . Надеюсь у нас получиться сделать беспроигрышную серию побед) MVP: OpenStar , Nort1s #GGD1mit
Сыграли прак против LXRP! Очень тяжелая игра была поначалу мы брали по 1-2 раунда ,но после смены сторон мы начали комбекать, но чего-то не хватило 😅! И еще 1 дебютный матч для Openstar, он неплохо разыгрался ,но силы истекли и начал медленнее забирать противников .Нам не хватило сил,чтобы забрать прак ,но мы даже забрали больше планированого раунда 5, а выиграли 7) MVP: Tv1n, Openstar #GGD1mit
❤1
POV: попросил тимейтов скинуть хае🤣
Решили взять реванш у них , в отличии от того матча мы брали раунды в начале даже шли чуть ли не вплотную . Но чет пошло не так мы начинали разваливаться . Отдельно хочу сказать про игрока D1fyz, он отлично отыграл дебютный матч против них достойно ,но не хватило сил чтобы вывести команду на выигрыш😫. Надеемся на-то ,что мы не будем повторять ошибки ,чтобы выиграть надо учиться на них) MVP: D1fyz #GGD1mit
❤🔥2
+ Новый игрок D1fyz Надеемся на его будущие и верность команде
- Игрок Am1rxon • Сыграл только один дебютный матч и он думал ,что он всех сильнее ,хотя оказалось все наоборот ! Жалько ,что он покинул клан #GGD1mit
❤1
Отыграли прак против клана T1-68, начало было плохое много ошибок ! Но после смены раундов почти сделали комбек , но силы команды чуть-чуть ну хватило ,чтобы выиграть😣. Еще сегодня был дебютный матч игрока Am1rxon , он в начале неплохо отыгрывал , но чего-то не хватило до выигрыша и мвп под конец! MVP: D1es #GGD1mit
Showing the 12 most recent of 18 posts we hold for @d1mitsquad. 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.
Named by 1 registered channel — 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“D1mit Squad” (@d1mitsquad), 15 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/d1mitsquad.
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.