8. 𝗗𝗘𝗟𝗜𝗖𝗘 DELICE 𝗜𝗡𝗙𝗢 › 𝗟𝗜𝗙𝗘 @QU1ILLbot (Эванесса)

Channel
𝗳𝗹𝗶𝗻𝘀 › 𝘂𝗻𝗶𝗼𝗻𝘀
@GaaEdFlins_unions
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003863539148 |
|---|---|
| Type | Channel |
| Username | @GaaEdFlins_unions |
| Created | 26 July 2026 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/GaaEdFlins_unions |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 17:01 | 1 | no change |
| 8 Aug 2026, 11:19 | 1 | first reading |
Engagement
10 posts held, back to 26 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1577.8%
- avg views ÷ 1 subscribers
- Avg views / post
- 15.8
- 9 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 10
- of 10 held
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 12 August 2026 |
|---|---|
| Posts held | 10 (26 July 2026 – 12 August 2026) |
| Views total | 142 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 17:01 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.
What this channel posts
- Photos
- 1
- Links
- 9
Lifetime counters from Telegram’s own channel header, read 14 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.
Recent posts
7. 𝗙𝗿𝗮𝗶𝗹 𝗟𝗶𝗴𝗵𝘁 Frail Light 𝗜𝗡𝗙𝗢 › 𝗟𝗜𝗙𝗘 @waguri_anon_bot (Каоруко)
6. 𝗖𝗬𝗕𝗘𝗥 𝗥𝗘𝗔𝗟𝗜𝗧𝗬 CYBER REALITY 𝗜𝗡𝗙𝗢 › 𝗟𝗜𝗙𝗘 @AMOURinc (Чёрный Лебедь)
5. 𝘀𝗲𝗸𝗱𝗼𝘂𝗺𝗶𝗻 sekdoumin 𝗜𝗡𝗙𝗢 › 𝗟𝗜𝗙𝗘 @fenek_anon_bot (МейМей)
4. 𝗱𝗮𝗿𝗸 𝗺𝗶𝗿𝗮𝗴𝗲 dark mirage 𝗜𝗡𝗙𝗢 › 𝗟𝗜𝗙𝗘 @florentia_drkbot (Фиренция)
3. : 𝗜𝗡𝗞𝗜 ((𝗚𝗔𝗬𝗢)) ! : ɪɴᴋɪ ((ɢᴀʏᴏ)) ! 𝗜𝗡𝗙𝗢 › 𝗟𝗜𝗙𝗘 @ku1rpuch (Канаэ)
2. 𝗕𝗮𝘁 𝗰𝗮𝘃𝗲 Bat cave 𝗜𝗡𝗙𝗢 › 𝗟𝗜𝗙𝗘 @re_tu_u (Ремус Люпин)
1. 𝗛𝗶𝗱𝗱𝗲𝗻 𝗥𝗲𝘃𝗲𝗿𝗶𝗲 Hidden Reverie 𝗜𝗡𝗙𝗢 › 𝗟𝗜𝗙𝗘 @IquswiDetective (Тигнари)
⠀⠀⠀ 🔤𝖗𝖎𝖊𝖓𝖉𝖑𝖞 𝖚𝖓𝖎𝖔𝖓𝖘💀 🪦🪦🪦🪦 🔢 🪦🪦🪦🪦 🤩 Условия : [ Читать ] 🤩 Предложить союз : [ Бот ] 🤩 Следящий : [ Флинс ] 8 / 10 ----------------------🤩
Channel created
Showing the 10 most recent of 10 posts we hold for @GaaEdFlins_unions. 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
Citation-graph rank — 743,743 of 1,481,217entries 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.
Mentions
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.
@Bat_cave_flood · 1551 postㅤ⋮𝗖Y̸̗̝͊̆𝗕E̸͛͊̌𝗥 𝗥𝗘Æ𝗟 ̷I𝗧Y̸̗͊̆ㅤ𖤝
@cyberrealityINFO · 1241 post🄻🄸🄵🄴┃ 𝗖𝗬𝗕3𝗥 › 𝗥𝝣Ɐ𝗟1𝗧𝗬.
@cyberrealityLIFE · 1261 post𝗗𝗮𝗿𝗸 𝗠𝗶𝗿𝗮𝗴𝗲 info
@DarkMirage_info · 801 post𝗗𝗮𝗿𝗸 𝗠𝗶𝗿𝗮𝗴𝗲 || 𝒍𝒊𝒇𝒆
@DarkMirage_Life · 771 postᝰ⋅ᐟ 𝔇𝚬𝗟𝗜ℭ𑩑𝗘 . ⋮⋮ │𝗜𝗡𝗙𝗢
@DELICEinfo · 1191 postᝰ⋅ᐟ 𝔇𝚬𝗟𝗜ℭ𑩑𝗘 . ⋮⋮ │︎𝗟𝗜𝗙𝗘
@DELICElife · 1061 postℱ𝘳𝘢𝘪𝘭 𝘓𝘪𝘨𝘩𝘵ᶦᶰᶠᵒ
@fraillight · 1291 postℱ𝘳𝘢𝘪𝘭 𝘓𝘪𝘨𝘩𝘵ᶫᶦᶠᵉ
@frailllife · 591 post⌕ 𝙃𝙞𝙙𝙙𝙚𝙣 𝙍𝙚𝙫𝙚𝙧𝙞𝙚ᴵⁿᶠᵒ
@HiddenRvr_Inf · 1731 post[ N#w erА ] ⌕ 𝙃𝙞𝙙𝙙𝙚𝙣 𝙍𝙚𝙫𝙚𝙧𝙞𝙚ᴸᶦᶠᵉ
@HiddenRvr_Lf · 1621 post𝗴𝗮𝗹𝗮𝘅𝘆'𝘀 𝗲𝗱𝗴𝗲 › 𝗵𝗼𝘂𝘀𝗲
@houseGalaxysEdge · 341 post: ɪɴᴋɪ ((ɢᴀʏᴏ)) — #ɪɴғᴏ !
@inkigay0info · 2271 post: ɪɴᴋɪ ((ɢᴀʏᴏ)) — #ʟɪғᴇ !
@inkigay0life · 1721 post𒆜 𝓓𝓮𝓽𝓮𝓬𝓽𝓲𝓿𝓮`` #𝙃𝙍𝙑 :: #𝑳𝑴 :: #𝑴𝑾
@IquswiDetective · 141 post𝕭𝔞𝔱 𝖈𝔞𝔳𝔢[life]||15+
@lifebatcaveflood · 1461 post•𝐈𝐍𝐅𝐎• ♯ ݁ 𝐒𝐄𝐊𝐃⊙𝐔𝐌𝐈𝐍 ˖ ౨౿
@SDMNinf · 8311 post•𝐋𝐈𝐅𝐄• ♯ ݁ 𝐒𝐄𝐊𝐃⊙𝐔𝐌𝐈𝐍 ˖ ౨౿
@SDMNlif · 3111 post
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.
Cite this entry
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“𝗳𝗹𝗶𝗻𝘀 › 𝘂𝗻𝗶𝗼𝗻𝘀” (@GaaEdFlins_unions), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/GaaEdFlins_unions.
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.