ㅤㅤㅤㅤㅤㅤㅤㅤㅤ

Channel
𝐋۪𝐀𝕰۫𝐕𝐈𝐌 𝓯𝟕𝟎𝟐 𝅥𝄀 𝐀lliances
@laevimcf
On this record: Growth · Engagement · Posts · Citations · Cite this entry
7subscribers
+1 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 | -1003675205039 |
|---|---|
| Type | Channel |
| Username | @laevimcf |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/laevimcf |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 10:44 | 7 | +1 |
| 16 Aug 2026, 06:48 | 6 | +1 |
| 13 Aug 2026, 03:17 | 5 | no change |
| 9 Aug 2026, 04:11 | 5 | -1 |
| 8 Aug 2026, 09:00 | 6 | first reading |
Engagement
20 posts held, back to 11 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.
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 11 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
ㅤㅤㅤㅤㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤㅤㅤㅤㅤ
Sticker, posted without a caption
ㅤㅤㅤㅤㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤㅤㅤㅤㅤ
Sticker, posted without a caption
ㅤㅤㅤㅤㅤㅤㅤㅤㅤ
— 𝗖𝗢𝗢𝗣𝗘𝗥𝗔𝗧𝗜𝗢𝗡 𝗟𝗘𝗩𝗘𝗟 .::. 𝟭 О1. 𝓡ᴇғʟᴇxɪᴏɴ 𝓓ᴇ 𝓛'ᴀᴍᴇ │ 𝐈nfo : @RdL_1nfo │ 𝐋ife : @RdL_l1fe │ 𝐖atcher : @DISSONANT1A ›‹ Иллуги О2. 𝐹𝐿𝒪𝒪𝒟 𝒪𝒩: 𝒟𝐸𝑀𝒪𝒩-𝒮𝐿𝒜𝒱𝐸𝑅 𝐵𝐿𝒜𝒟𝐸𝒮 │ 𝐈nfo : @TomiokaUta_ShinobuINFO │ 𝐋ife : @TomiokaUta_ShinobuLIFE │ 𝐖atcher : : @adinwix ›‹ Шинобу О3. 𝐒𝐇𝐈𝐑𝐎𝐈 l| 𝐇𝐈𝐍𝐀𝐆𝐈𝐊𝐔 │ 𝐈nfo : @shiroihinagikuinfo │ 𝐋ife : @shiroihinagikulife │ 𝐖atcher : @Sufliatka ›‹ Акиме О4. 🌫°.𝙀lus𝔗ve ¦◖𝘀✗𝔠ret𝓼』 │ 𝐈…
Showing the 12 most recent of 20 posts we hold for @laevimcf. 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 — 712,608 of 1,625,404entries 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 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.
@abetiilife · 541 post𝐀 𝐓 𝐋 𝐀 𝐍 𝐓 𝐈 𝐃 𝐀ᴴᵒᵐᵉ 12+
@Atlantidalife · 951 post𝐀 𝐓 𝐋 𝐀 𝐍 𝐓 𝐈 𝐃 𝐀 12+
@Atlantidaprogekt · 1041 post𝕮𝖔𝖓𝖘𝖙𝖊𝖑𝖑𝖆𝖙𝖎𝖔𝖓 𝕽𝖆𝖞ᴸᶦᶠᵉ
@CARayLife · 1301 post𝗖ؖ𝗵ؒ ؛𝗮ً𝘀𝗲 𝗹𝗶𝗳؈
@chasefloodlife · 791 post𝕴𝒏𝗳𝑜 𔗂꯭ֺ 𝕮𝐡ɑׁׅ𔓕ִꑄ ִ𝆹𝅥 𓈒𝐒𝕔𝖗ꪱׁׁׁׅׅׅᏢɨ ۫𝆬⃝ ִֺ𝅄𝆹ִֺ𝅥ৎ
@CS_inf0 · 2921 post[❄]𝕷𝒊𝗳𝑒 𔗂꯭ֺ 𝕮𝐡ɑׁׅ𔓕ִꑄ ִ𝆹𝅥 𓈒𝐒𝕔𝖗ꪱׁׁׁׅׅׅᏢɨ ۫𝆬⃝ ִֺ𝅄𝆹ִֺ𝅥ৎ
@CS_lif · 2081 post𝑫𝒂𝒓𝒎𝒂𝒏𝒕𝒊𝒏𝒆†
@Darmantine · 231 post𝑫𝒂𝒓𝒎𝒂𝒓𝒏𝒕𝒊𝒏𝒆† - 𝒉𝒐𝒎𝒆
@Darmantine_home · 241 postᰔ.𝙀lu͟͟s͟͟𝔗ve ¦︎◖︎𝘀✗︎𝔠ret𝓼 ʚɞ 𝙃𝟎mℰ
@ELsec_h0m3 · 2681 post𝙃𝙀𝙏𝙐𝙊𝙃 𝘿𝙀𝙍𝙏||𝙄𝙉𝙁𝙊
@HTD_info · 1931 post[ЗАМОРОЖЕН] 𝙃𝙀𝙏𝙐𝙊𝙃 𝘿𝙀𝙍𝙏||𝙇𝙄𝙁𝙀
@HTD_life · 1461 post# 𝓚𝔦𝔰𝑚𝑒𝓉 ⋮ 𝑖𝑛𝑓𝑜 ˊ˗ ¹⁴⁺
@kismetinfo · 1991 post# 𝓚𝔦𝔰𝑚𝑒𝓉 ⋮ 𝑙𝑖𝑓𝑒 ˊ˗ ¹⁴⁺
@kismetlife · 1591 post𝐒𝐧𝐚𝐤𝐞 𝐇𝐨𝐥𝐞 (𝘪𝘯𝘧𝘰)
@krdinfo229 · 2231 post.
@mintydieINFO · 31 post𓈒ִ ꯭ׄ ➤ 𝗅𝗂𝖿𝖾 ⸝⸝ 𝔐‼︎𝗡𝔍𝗬𝔇𝗜𝖤 ִֹ .
@mintydieLIFE · 791 post𝗖𝗵𝗮𝘀𝗲 ؒ ؈𝗶𝗻𝗳ً𝗼
@modestiaxinfo · 2041 postRenasa | 𝐋۪𝐀𝕰۫𝐕𝐈𝐌
@Ranasla · 21 post𝓡ᴇ́ғʟᴇxɪᴏɴ 𝓓ᴇ 𝓛'ᴀ̂ᴍᴇ`𝓘𝓷𝓯𝓸
@RdL_1nfo · 1251 post𝓡ᴇ́ғʟᴇxɪᴏɴ 𝓓ᴇ 𝓛'ᴀ̂ᴍᴇ`𝓛𝓲𝓯𝓮
@RdL_l1fe · 1011 post[ЛАЙФ ЗАКРЫТ]⁺ ׅ ℒ𝘪𝘧𝘦 ℛυb͟͟𝙮 ℱe̺a̶̶s̶̶𝘁..⁺ ׅ
@RubyFeast_Life · 271 postСмена каналов и названия!!!
@TomiokaUta_ShinobuLIFE · 1561 post. channel woi .
@whitekaylso · 11 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐋۪𝐀𝕰۫𝐕𝐈𝐌 𝓯𝟕𝟎𝟐 𝅥𝄀 𝐀lliances” (@laevimcf), 7 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/laevimcf.
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.