FAMILY UNIONS LIST 1 ꞋꞌꞋ ִ ࣪ ⋆𝐼𝑛𝑠𝑒𝑐𝑡 𝐹𝑙𝑜𝑜𝑑 ִ ࣪ ⊹ Life — @IFilife Info — @IFiinfo Watcher — @Meoki1 2. Life Info Watcher — 3. Life Info Watcher 4. Life Info Watcher 5. Life Info Watcher 6. Life Info Watcher 7. Life Info Watcher 8. Life Info Watcher 9. Life Info Watcher 10. Life Info Watcher Следяший – @Kanae_lo 1/10

Channel
.
@unionskanae
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
3subscribers
-1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003907823272 |
|---|---|
| Type | Channel |
| Username | @unionskanae |
| Created | Between 1 April 2026 and 1 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/unionskanae |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 84% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 12:51 | 3 | -1 |
| 29 Oct 2026, 16:01 | 4 | -1 |
| 23 Oct 2026, 01:20 | 5 | -1 |
| 16 Oct 2026, 13:09 | 6 | -1 |
| 29 Sept 2026, 03:38 | 7 | +4 |
| 11 Sept 2026, 11:59 | 3 | +1 |
| 25 Aug 2026, 04:05 | 2 | -2 |
| 13 Aug 2026, 09:47 | 4 | no change |
| 10 Aug 2026, 06:48 | 4 | first reading |
Engagement
2 posts held, back to 1 August 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 2 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
UNIONS LIST 1. °• ~𝐹𝐿𝒪𝒪𝒟 𝒪𝐹 𝒲𝐼𝒩𝒢𝐸𝒟 𝒟𝑅𝐸𝒜𝑀𝒮 ~ •° Lifᴇ —@lifeFOWD Infᴏ —@infoFOWD Wᴀᴛᴄhᴇr —@green1_teacup 2. ₊⸊゙@..𝑮𝒂𝓎𝙋𝖊𝖆Ꮥ૯ .︵ׁ₊ #𝓛𝓖_𝓐 Lifᴇ —@GayPease_Life1 Infᴏ —@GayPease_info1 Wᴀᴛᴄhᴇr —@ShidoKR 3. 𝗪𝗛𝗜𝗧𝗘 𝗟𝗢𝗧𝗨𝗦 Lifᴇ —@wh1te_l0tus_life Infᴏ —@wh1te_l0tus Wᴀᴛᴄhᴇr —@Im_Atasya 4. Ⲋⲟυⲃʀⲉⲧⲧⲉⲋ_Ⲋⲟⲛⳋ Lifᴇ — @life_channelSS Infᴏ — @soubrettesong Wᴀᴛᴄhᴇr — @kkklum 5 𓆗ꪀ᥆ꪑꫀ૮ꫂꪶꫀ ᥆ꪉꪋꪦꪋꪯ𓆗 Lifᴇ — @ObanaiEstateLife Infᴏ — @ObanaiE…
Showing the 2 most recent of 2 posts we hold for @unionskanae. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
@Bat_cave_flood · 861 postПереходник еме
@EME_LIFES · 71 post07.11.26
@inf_np · 1141 post^^инфо^^ °• ~ 𝐹𝐿𝒪𝒪𝒟 𝒪𝐹 𝒲𝐼𝒩𝒢𝐸𝒟 𝒟𝑅𝐸𝒜𝑀𝒮 ~ •°
@infoFOWD · 1151 post୨ᰰ᳟ㅤ꒰ᩧ৯ 𝐊𝗮𝗻𝗮𝗲 𝐚𝗻ԁ 𝐊𝗼𝘆𝘂𝗸𝗶 𓈒 ░⃪⃨◟ױ │𝖨𝖭𝖥𝖮
@kanaefull67 · 121 postᯏ 𐔌 𝗞𝗡𝗞│ЗАКРЫТ!
@Knk_lifeee · 71 post˚₊‧꒰ა 🫧 ʜᴇʀᴍɪᴛ ᴘᴜʀᴘʟᴇ¦Life ໒
@lif_np · 841 post~My Life 🌿🌹
@life_channelSS · 201 postЗАМОРОЖЕН 𝕭𝔞𝔱 𝖈𝔞𝔳𝔢[life]||15+
@lifebatcaveflood · 591 post𝑳𝑰𝑭𝑬 • °• ~ 𝐹𝐿𝒪𝒪𝒟 𝒪𝐹 𝒲𝐼𝒩𝒢𝐸𝒟 𝒟𝑅𝐸𝒜𝑀𝒮 ~ •°
@lifeFOWD · 191 post꒰ ✁ ꒱ 𝓚𝙤𝙣𝙤𝙝𝙖 𝓜𝙚𝙢𝙤𝙧𝙞𝙚𝙨 °𝆹𝅥 ⛓ 𓂃 ₊ |Life|
@lifeKonohaMemories · 201 post#WSF || Life
@LifeWSF · 1761 post/𝑰𝑵𝑭𝑶/ ꪀ᥆ꪑꫀ૮ꫂꪶꫀ ᥆ꪉꪋꪦꪋꪯ
@ObanaiEstateInfo · 1621 post/𝑳𝑰𝑭𝑬/ ꪀ᥆ꪑꫀ૮ꫂꪶꫀ ᥆ꪉꪋꪦꪋꪯ
@ObanaiEstateLife · 911 postRP Jujutsu
@RpJujutsuinfo · 1361 postЗАКРЫТО 𝅄☾ ˗ˏ𝑊ℎ𝑖𝑡𝑒 𝐿𝑜𝑡𝑢𝑠ˊ˗ 𑁍𝅄 | 𝑰𝑵𝑭𝑶
@wh1te_l0tus · 531 postЗАКРЫТО 𝅄☾ ˗ˏ𝑊ℎ𝑖𝑡𝑒 𝐿𝑜𝑡𝑢𝑠ˊ˗ 𑁍𝅄 | 𝑳𝑰𝑭𝑬
@wh1te_l0tus_life · 371 post#WSF || Info
@WSF_info · 1731 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.
Handles this channel named that no longer answer
- Dead references
- 12
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 12
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@unionskanae named 12 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 18 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 16 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 16 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 30 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 2 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 15 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 2 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 25 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 14 August 2026 – 14 August 2026 · confirmed gone 27 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“.” (@unionskanae), 3 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/unionskanae.
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.