Channel
@unionneverdie
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
94subscribers
-11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002156762068 |
|---|---|
| Type | Channel |
| Username | @unionneverdie |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/unionneverdie |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 07:16 | 94 | -1 |
| 29 Aug 2026, 23:07 | 95 | -7 |
| 22 Aug 2026, 00:38 | 102 | -4 |
| 14 Aug 2026, 17:55 | 106 | +1 |
| 9 Aug 2026, 09:01 | 105 | no change |
| 7 Aug 2026, 17:17 | 105 | first reading |
20 posts held, back to 3 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
32 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 28.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5366408336084328521 | 9 | 28.1% | |
| custom 5420247868558575300 | 6 | 18.8% | |
| custom 5420502435565175128 | 4 | 12.5% | |
| custom 5422587285705096904 | 4 | 12.5% | |
| custom 5368296996413135424 | 3 | 9.38% | |
| custom 5422810246047366757 | 3 | 9.38% | |
| custom 5420093928340750259 | 2 | 6.25% | |
| custom 5377688401967336790 | 1 | 3.13% |
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 10 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 32 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 3 July 2026 to 8 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.
ㅤ ㅤ ㅤ 《 ♟ 》. ᛝ репост тайм 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » . если вы обнаружите ошибки в рп тайме, касаемо своих флудов, просим сказать об этом!! @Plumeriaa_life — видео // видео // видео @moonfanglife — видео. @LifeOfElunox — поиск админов // результаты чистки. @lif3_AML — видео // результаты чистки.
custom 54202478685585753001
Signed union flood assistant // U23
ㅤ ㅤ 《 ♟ 》. ᛝ репост тайм 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » . если вы обнаружите ошибки в рп тайме, касаемо своих флудов, просим сказать об этом!! @LUNARX_LIFE — видео. @amesllif — видео. @snakeproekt_life — видео // результаты чистки // видео. @moonfanglife — видео (с прошедшим др!!). @EMBL1F — видео. @Plumeriaa_life — видео // результаты чистки // поиск участников // видео // видео. @LifeOfElunox — результаты чистки.
Signed union flood assistant // U23
ㅤ ㅤ 《 ♟ 》. ᛝ репост тайм 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » . если вы обнаружите ошибки в рп тайме, касаемо своих флудов, просим сказать об этом!! @LUNARX_LIFE — поиск союзов // видео // видео // видео // видео. @snakeproekt_life — выход из реста // видео // рест следящего. @moonfanglife — игра. @amesllif — видео // видео. @CS_lif — появление нового админа // появление нового админа // поиск союзов и нью // поиск админов. @…
Signed union flood assistant // U23
ㅤ ㅤ 《 ❌ 》. ᛝ 𝔘𝗇𝗂𝗈𝗇𝗌 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » 🕰 . 𝔘𝗇𝗂𝗈𝗇 𝔉𝗅𝗈𝗈𝖽 вступил в дружеский союз с 𝐄𝐋𝐔𝐍𝐎𝐗
Signed (!) грёза грёзовна U23
разрыв
Signed (!) грёза грёзовна U23
ㅤ ㅤ 《 ♟ 》. ᛝ репост тайм 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » . если вы обнаружите ошибки в рп тайме, касаемо своих флудов, просим сказать об этом!! @CS_lif — поиск нью // поиск администраторов. @Loonfloodd — поиск нью // поиск союзов // видео. @amesllif — видео // видео. @LUNARX_LIFE — видео // видео // результаты чистки. @snakeproekt_life — видео // результаты чистки. @Plumeriaa_life — видео // видео // результаты чистки. @l…
Signed union flood assistant // U23
ㅤ ㅤ 《 ❌ 》. ᛝ 𝔘𝗇𝗂𝗈𝗇𝗌 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » 🕰 . 𝔘𝗇𝗂𝗈𝗇 𝔉𝗅𝗈𝗈𝖽 вступил в дружеский союз с ░⃝ℂ𝚑𝗮✶꯱⊹𝐒𝗖𝐫𝕚ᑭᎿֺ𓈒⁅
custom 54202478685585753001custom 54228102460473667571
Signed (!) грёза грёзовна U23
ㅤ ㅤ 《 ❌ 》. ᛝ 𝔘𝗇𝗂𝗈𝗇𝗌 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » 🕰 . 𝔘𝗇𝗂𝗈𝗇 𝔉𝗅𝗈𝗈𝖽 вступил в дружеский союз с 𝗟𝗨𝗡𝗔𝗥𝗫 𝗠𝗢𝗢𝗡𝗥𝗜𝗦𝗘
Signed (!) грёза грёзовна U23
ㅤ ㅤ 《 ❌ 》. ᛝ 𝔘𝗇𝗂𝗈𝗇𝗌 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » 🕰 . 𝔘𝗇𝗂𝗈𝗇 𝔉𝗅𝗈𝗈𝖽 вступил в дружеский союз с â𝗆𝖾𝗌 𝗅𝗂é𝖾𝗌
Signed (!) грёза грёзовна U23
список союзов обновлен!
custom 53664083360843285211custom 53776884019673367901custom 54205024355651751281
Signed (!) грёза грёзовна U23
на всех, кто отметился на чистке подписались, список союзов будет скорректирован позже. если захотите перезаключить союз – лс нашего ассистента всегда открыт!
custom 53682969964131354241custom 54200939283407502591custom 54205024355651751281custom 54225872857050969041
Signed (!) грёза грёзовна U23
ㅤ ㅤ 《 ♟ 》. ᛝ репост тайм 〟· [ 𝖥𝖫𝖮𝖮𝖣 ] » . если вы обнаружите ошибки в рп тайме, касаемо своих флудов, просим сказать об этом!! @Plumeriaa_life — видео // видео // видео. @lifevanillahaze — видео // видео. @snakeproekt_life — видео // видео. @Loonfloodd — нью эра // видео // видео // видео // поиск нью // поиск союзов.
Signed union flood assistant // U23
Showing the 12 most recent of 20 posts we hold for @unionneverdie. 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.
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.
Named by 9 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.
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“ЛАЙФ ЗАМОРОЖЕН 𝔘𝗇𝗂𝗈𝗇 𝔉𝗅𝗈𝗈𝖽” (@unionneverdie), 94 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/unionneverdie.
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.