Channel
@unions_thoma
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
4subscribers
+1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003848429953 |
|---|---|
| Type | Channel |
| Username | @unions_thoma |
| Created | 26 May 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/unions_thoma |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 18:34 | 4 | +1 |
| 13 Aug 2026, 17:46 | 3 | no change |
| 9 Aug 2026, 06:16 | 3 | first reading |
5 posts held, back to 26 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 26 May 2026. An engagement rate over an empty window would be a number about nothing.
❌❌❌𝖥𝖠𝖬𝖨𝖫𝖸 :: О1 ! 1. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 2. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 3. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 4. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 5. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 6. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 7. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 8. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 9. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: 10. 𝗂𝗇𝖿𝗈 :: 𝗅𝗂𝖿𝖾 :: 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 ::
𝖥𝖱𝖨𝖤𝖭𝖣𝖫𝖸 :: О2 ! 21. °•.>𝑴𝒐𝒐𝒏 𝑺𝒕𝒂𝒓𝒔<.•° 𝗂𝗇𝖿𝗈 :: @MoonStars_Infooo 𝗅𝗂𝖿𝖾 :: @MoonStars_Life 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @Miss_joke_1 22. 𝐄𝐋𝐔𝐍𝐎𝐗 𝗂𝗇𝖿𝗈 :: @InfoOfElunox 𝗅𝗂𝖿𝖾 :: @LifeOfElunox 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @Iquswiiii 23. ʜᴀᴠᴇɴ ᴏғ ᴛʜᴇ ᴍᴏᴏɴ 𝗂𝗇𝖿𝗈 :: @hvm_info 𝗅𝗂𝖿𝖾 :: @hvm_life 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @ttayww 24. 𝑃𝑒︩︪𝑎𝑟𝑙 ¡ 𝗂𝗇𝖿𝗈 :: @PL_IN 𝗅𝗂𝖿𝖾 :: @Pl_lI1 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @Re_nAiq 25. 𝅄 ֺ ℰst𝑒𝘭𝘭𝖺ꪚ ִ 𝅄 𝗂𝗇𝖿𝗈 :: @estellarinf 𝗅𝗂𝖿𝖾 :: @estellarlife 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @s…
𝖥𝖱𝖨𝖤𝖭𝖣𝖫𝖸 :: О1 ! 1. 𝑅𝑒𝑛𝑑𝑒𝑧-𝑣𝑜𝑢𝑠 𝑎 𝑃𝑎𝑟𝑖𝑠 𝗂𝗇𝖿𝗈 :: @randezvousaparis 𝗅𝗂𝖿𝖾 :: @randezvousaparislife 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @ttigeerr 2. 𝗯𝗲𝗿𝗹𝗶𝗴𝗵𝘁 𝗂𝗇𝖿𝗈 :: @berligh 𝗅𝗂𝖿𝖾 :: @lifeberlight 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @q_werafk 3. ⎯۫ ︎ ︎ 𝜗ৎ ︎𝐀𝖀ℝ𝕺𝐑𝐀 .ᐟ 𝗂𝗇𝖿𝗈 :: @AURA_INF0 𝗅𝗂𝖿𝖾 :: @AURA_L1FE 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @freezinqs_bot 4. ₊ ˚⊹♡ 𝐺𝑜𝑙𝑑𝑒𝑛-𝐵𝑟𝑜𝑤𝑛 ♡⊹ [☀️] ˚₊ 𝗂𝗇𝖿𝗈 :: @Golden_Browwn1 𝗅𝗂𝖿𝖾 :: @GoldenBrovnLife 𝗍𝗋𝖺𝖼𝗄𝖾𝗋 :: @NordYoisa 5. 𝐌𝐎𝐎𝐍 𝐅𝐀𝐍𝐆 𝗂𝗇𝖿𝗈 :: @moonfangrp …
ᅠ𒀭 ⋮ 𝐔𝐍𝐈𝐎𝐍𝐒 . 𖥔 𓈒 ⎯ ੭୧ ⎯ ꒱ 𝄄𝄭 𝗧𝗥𝒜𝗖𝗞𝗘ℛ ‹ @fishvakame & т𝐨м𝐚 𓐇۪ۜܵ۫ ٫٫ усл𝐨в𝐮я для з𝐚ключ𝐞н𝐮я б𝐨т для з𝐚ключ𝐞н𝐮я ˖ . 𓈒 ⎯ ੭୧ ⎯ ꒱ ࿔ сп𝐮с𝐨к с𝐨юзн𝐮к𝐨в : ◂ ◂ друж𝐞ск𝐮е 𝐎𝟭 ‹ › 𝐎𝟮 ࣪ 𓈒 28 ╱ 40 𓆪 ◂ ◂ с𝐞м𝐞йны𝐞 𝐎𝟭 ࣪ 𓈒 0 ╱ 10 (?) 𓆪
Channel created
Showing the 5 most recent of 5 posts we hold for @unions_thoma. 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 — 545,382 of 1,548,671entries 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 2 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.
@unions_thoma named 16 handles 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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐋𝐈𝐒𝐓 𝐎𝐅 𝐔𝐍𝐈𝐎𝐍𝐒” (@unions_thoma), 4 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/unions_thoma.
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.