Channel
@unionsESD
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
25subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003987352734 |
|---|---|
| Type | Channel |
| Username | @unionsESD |
| Created | 8 May 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/unionsESD |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 09:17 | 25 | no change |
| 8 Aug 2026, 11:00 | 25 | first reading |
7 posts held, back to 8 May 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 7 (8 May 2026 – 5 August 2026) |
| Views total | 76 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 09:17 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Следящий — @hasqxh 1️⃣⏺໒ 𝐅𝐀𝐕✶𝐑𝐈𝐒 𝆭 𝆹𝅥 Инфо: @favoris_roleplay_info Лайф: @favoris_roleplay_life 2️⃣⏺⎯ 𝐄𝗌𝖼𝖺𝗉𝗂𝗌𝗆 . ⧽ ♟️ Инфо: @ESC4P1SM_INF Лайф: @ESC4P1SM_LIF 3️⃣⏺𝗤𝘂𝗶𝗲𝘁 𝗢𝗰𝗲𝗮𝗻 𝗙𝗹𝗼𝗼𝗿 Инфо: @QOF_flood Лайф: @QOF_Life 4️⃣⏺ℬ𝒍𝒐𝒐𝒅𝒚 ℬ𝒖𝒕𝒕𝒆𝒓𝒇𝒍𝒚 Инфо: @BloB_info Лайф: @BloB_life 4️⃣⏺𝘁𝖺𝗺𝖻𝗈𝗿 Инфо: @tamborinfo Лайф: @
ЛИСТ 2 Следящий — @Daitokomeo 1️⃣3️⃣⏺ ࣪૮₍⏝⋮𝑮𝑬𝑨𝑺 𝑭𝑳𝑶𝑶𝑫 ͡꒱ᩙִ⸼࣪ Инфо: @Geasflood1nfo Лайф: @Geasflo0d_life 1️⃣4️⃣⏺੭ৎ 𝕰𝐌𝕭𝐄𝕽𝐋𝖄𝐍 𖥔 Инфо: @emb1nf Лайф: @embl1f 1️⃣5️⃣⏺ Инфо: Лайф: 1️⃣6️⃣⏺ 𝐂𝐀𝐑𝐏𝐄 𝐃𝐈𝐄𝐌 Инфо: @CarpeDiemINFO Лайф: @CarpeDiemLifeFlood 1️⃣7️⃣⏺ Инфо: Лайф: 1️⃣8️⃣⏺ Ин…
Следящий — @Daitokomeo 1️⃣ ⏺˚˚.↲⊹݃𝖶⍺ִ𝐤ᧉẜ࡙ꭎֺlִ 𐨌⃟ʾᵐ░҉░csִֺᧉrყֺ·﹆ Инфо: @WM_inf0 Лайф:@WM_l1fe 2️⃣⏺ Инфо: Лайф: 3️⃣⏺𝐋۪𝐀𝕰۫𝐕𝐈𝐌 Инфо: @laevim Лайф: @laevimhub 4️⃣⏺⾕┃𝗘𝗠𝗘𝗥𝗔𝗟𝗗𝂅ׄ . ۫ 𝗘𝗖𝗟𝗜𝗣𝗦𝗘 ִֺ۪ ִ ⃙𖦹 𝅄 Инфо: @EME_INFOS Лайф: @EME_LIFES 5️⃣⏺ 𝑴𝖠𝐑݁𝗟𝖡𝕺𝐑𝖮 Инфо: @MLB1INF Лайф: @MLB1LIF 6️…
✨💘СЕМЕЙНЫЕ СОЮЗЫ💘 🫵🍰🍰🍰🍰🍰🍰🍰🍰🍰🍭 Следящий — Дайтока 1️⃣⏺ 2️⃣⏺ 3️⃣⏺ Следящий — Шиншилла 1️⃣⏺ 2️⃣⏺ 3️⃣⏺
Следящий — Ксанакс @UnionESD_bot 💘СЕМЕЙНЫЕ СОЮЗЫ💘 🫵🍰🍰🍰🍰🍰🍰🍰🍰🍰🍭 1️⃣⏺𝗛𝗔𝗧𝗥𝗘𝗗 — @hatr3q (Сын) 2️⃣⏺𝗖𝗵𝗮𝗿𝗹𝗶𝗲’𝘀 𝗪𝗲𝗯 𝗡𝗲𝘀𝘁 𝗳𝗼𝗼𝗱 — @dermoog (Сестра) 3️⃣⏺Noctelle — @nerusfa (Жан) 4️⃣⏺𝗟𝗨𝗠𝗜𝗦 𝗙𝗟𝗢𝗢𝗗 — @Kaf1505 (Бародар) 5️⃣⏺Overdose — @sat0sczx (Муж) 6️⃣⏺𝘈𝘶𝘳𝘶𝘮 𝘝𝘦𝘪𝘭 — @cherrywixxv (Шашлык)
❕РЕКВИЗИТЫ Название в моно 𝗕𝗟𝗘𝗦𝗦𝗘𝗗 Инфо — @inf0ESD // https://t.me/inf0ESD Лайф — @blessslife // https://t.me/blessslife Следящий — Наши условия Для заключения союза писать @hasqxh / @Daitokomeo
Channel created
Showing the 7 most recent of 7 posts we hold for @unionsESD. 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.
Citation-graph rank — 1,046,036 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@unionsESD named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“𝗨𝗻𝗶𝗼𝗻𝘀 || #𝙀𝙎𝘿” (@unionsESD), 25 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/unionsESD.
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.