Channel
@whereundr
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
13subscribers
-1 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003785636203 |
|---|---|
| Type | Channel |
| Username | @whereundr |
| Created | Between 1 February 2026 and 5 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 3 September 2026 |
| On Telegram | t.me/whereundr |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 00:17 | 13 | -1 |
| 12 Aug 2026, 00:46 | 14 | no change |
| 11 Aug 2026, 22:47 | 14 | first reading |
19 posts held, back to 5 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 19 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
56 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 32.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5226460133868990366 | 18 | 32.1% | |
| custom 5397712342660183497 | 14 | 25.0% | |
| custom 5469942693167670762 | 11 | 19.6% | |
| custom 5224654439423442117 | 8 | 14.3% | |
| custom 5357302799258393828 | 5 | 8.93% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 14 of the 19 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 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 5 July 2026 to 20 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.
🔤🔤🔤🔤🔤🔤 🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠 1️⃣🇷🇺Tess 2️⃣🇷🇺UndeR 3️⃣🇷🇺god complex 4️⃣🇷🇺m0nesy 5️⃣🇷🇺voll1 6️⃣ 🔠🔠🔠🔠🔠🔠 •🇷🇺Tanechka 🔠🔠🔠🔠🔠🔠🔠 •🇷🇺Kkosmos •🇷🇺Tess •🇷🇺Trevel •🇷🇺Traktor 🛫🔠🔠🔠🔠🔠 🔤🔤🔤➖@Teqline ➖➖➖➖@skostyukov
custom 52246544394234421172custom 52264601338689903661custom 54699426931676707621
прак в 3 ночи? - похуй газ ⚡️
custom 53573027992583938281custom 54699426931676707621
Channel name was changed to «UndeR | tkdd»
🤩🤩🤩🤩 🤩 PITCH -> Takeda eSports 🤩 🤩 Мы переходим под новый тег - tkdd 🤩 🤩 Pitch eSports объявляется закрытым. 🔓
custom 53573027992583938282
🤩🤩🤩🤩 🤩 Takeda eSports подписывает игроков Pitch! 🤩 1️⃣🇷🇺Tess 2️⃣🇷🇺UndeR 3️⃣🇷🇺m0nesy 4️⃣🇷🇺Voll1 5️⃣🇷🇺Aoyame
custom 52246544394234421172custom 52264601338689903662custom 54699426931676707621
Положение дел на данный момент - хуево 🔴я морально убит Начнем по порядку: 🟢15.07 играли квалы против команды 8BX, до игры я был максимально готов, но я узнал то, чего не должен был знать и моя менталка нахуй улетела перед игрой. Проиграли со счётом 10:13, моя стата - 8 21 (ебаный позор), после этого из-за нарушения правил с обоих сторон - дали переигровку. 🟠16.07 целый день был занят, приехав домой заебанный в 20…
custom 53977123426601834972custom 52246544394234421171custom 52264601338689903661
🤩🤩🤩🤩🤩🤩 Open Qualification #4 VT Tournament 1/2 🤍 🔴8BX ESports 🟢Time: 21:00 ⏰️ 🟠Map: Rust 🗺 (🤩) Не имеем никаких представлений на этот матч, придется очень непросто для нас, но будем стараться как только можем. 🤩 Time To Win Pitch 🤩
ждём некст день и играем уже против команды вк комы
Командa Mellow Esports - ТП;Причина: нарушение пункта 6. Команда Northen Dragons - ТП;Причина: нарушение пункта 6. PITCH Esports,free x win - 1/2
🤩 сегодня наконец-то играем квалы против каких-то nothern dragons, будем вырываться в group stage
custom 53977123426601834972custom 52264601338689903661custom 54699426931676707621
🤩 немного красивых моментов с сегодняшнего прака ⚡️ резкие движения - просадки по фпс, некст откаты будут на стабильном фпсе, извиняюсь 🤩
custom 53573027992583938282custom 52264601338689903661custom 53977123426601834971custom 54699426931676707621
⚡️ладно, вылетели с первых квалов, ждём закрытия, вернёмся сильнее во вторых квалах #PitchTimeToWin 🤩
custom 52264601338689903663custom 53977123426601834971
Showing the 12 most recent of 19 posts we hold for @whereundr. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“UndeR | tkdd” (@whereundr), 13 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/whereundr.
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.