Channel
@unionInfinitely
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
21subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003885270812 |
|---|---|
| Type | Channel |
| Username | @unionInfinitely |
| Description | Инфо: @finitysleg_info Лайф: @finitysleg Для заключения: скирк - @HH8Gd алиса - @zedhxyd Коломбина - @kiys_pipiys67 одетта - @lju1ka |
| Created | Between 1 February 2026 and 12 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/unionInfinitely |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 13:47 | 21 | no change |
| 8 Aug 2026, 07:15 | 21 | first reading |
20 posts held, back to 12 April 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 20 posts for this entry, the most recent from 5 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
Navigating through unions ⃝📌 Union Skirk & list 1 ; list 2 ; list 3 ; list 4 : Family ⃟🛑 Union Alice & list 1 ; ⃝📌 Union Odette & list 1 ; family ➤ Для союза писать в бота!! ㅤ⃟🖍 Terms of the union ㅤ⃟🔊 Requisites
Sticker, posted without a caption
ㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤㅤ
.
Sticker, posted without a caption
𝙁𝙖𝙢𝙞𝙡𝙮 𝙐𝙣𝙞𝙤𝙣𝙨 ✨✨✨1/?` ➤ 𝙏𝙧𝙖𝙘𝙠𝙚𝙧: @lju1ka 1. 𝘽𝙧𝙤𝙩𝙝𝙚𝙧 "𝘽𝙖𝙩 𝙘𝙖𝙫𝙚" 𝙛𝙡𝙤𝙤𝙙 𝙞𝙣𝙛𝙤: @Bat_cave_flood 𝙡𝙞𝙛𝙚: @lifebatcaveflood 𝙩𝙧𝙖𝙘𝙠𝙚𝙧: @re_tu_u
ㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤ
➤ Следящий Одетта: @lju1ka ───﹃﹄26/?? 1. 🥹 "𝘽𝙖𝙩 𝙘𝙖𝙫𝙚" 𝙛𝙡𝙤𝙤𝙙 𝙞𝙣𝙛𝙤: @Bat_cave_flood 𝙡𝙞𝙛𝙚: @lifebatcaveflood 𝙩𝙧𝙖𝙘𝙠𝙚𝙧: @re_tu_u 2. 🥹Ꭱift ᴏf Ꮀᴀtе 𝙞𝙣𝙛𝙤: https://t.me/infoo_RF 𝙡𝙞𝙛𝙚: https://t.me/lifee_RF 𝙩𝙧𝙖𝙘𝙠𝙚𝙧: @xxxzzhx 3. 🥹໒ 𝐅𝐀𝐕✶𝐑𝐈𝐒 𝆭 𝆹𝅥 𝙞𝙣𝙛𝙤: https://t.me/favoris_roleplay_info 𝙡𝙞𝙛𝙚: https://t.me/favoris_roleplay_life 𝙩𝙧𝙖𝙘𝙠𝙚𝙧: @Rronnynout 4.🥹◠ » 𝐁𝗅𝗈𝗈𝖽𝗒 𝐁𝗈𝗈𝗄 𝐒𝗇𝗈𝗐 ⁝ #𝐁𝐁𝐒 𝙞𝙣𝙛𝙤: https://t.me/BBS_INF0 𝙡𝙞𝙛𝙚: https://t.me/BBS_L…
Showing the 12 most recent of 20 posts we hold for @unionInfinitely. 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 — 348,591 of 1,160,990entries 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.
@unionInfinitely named 4 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Союзы 𝙞𝙣𝙛𝙞𝙣𝙞𝙩𝙮'𝙨 𝙡𝙚𝙜𝙖𝙘𝙮” (@unionInfinitely), 21 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/unionInfinitely.
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.