Telegram RegisterThe public register of Telegram

Channel

𝐋۪𝐀𝕰۫𝐕𝐈𝐌 𝅥𝄀 𝐀lliances

@laevimcf

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

5subscribers

-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
TypeChannel
Username@laevimcf
Descriptionㅤㅤㅤㅤㅤㅤㅤㅤㅤ 𝟕.𝟎𝟒.𝟐𝟎𝟐𝟒 𝐈𝐍𝐅𝐎 : @laevim 𝐋𝐈𝐅𝐄 : @laevimhub
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held3
On Telegramt.me/laevimcf

Growth

565.58 August 2026 — 6 subscribers9 August 2026 — 5 subscribers13 August 2026 — 5 subscribers8 August 202613 August 2026
3 measurements spanning 5 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:175no change
9 Aug 2026, 04:115-1
8 Aug 2026, 09:006first 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.

What this channel posts

Photos
4
Links
4

Lifetime counters from Telegram’s own channel header, read 13 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

11 Jul 2026, 20:13 UTC107 viewsread 13 August 2026

— 𝗖𝗢𝗢𝗣𝗘𝗥𝗔𝗧𝗜𝗢𝗡 𝗟𝗘𝗩𝗘𝗟 .::. 𝟭 О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. 🌫°.𝙀lu‌‌s‌‌𝔗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.

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.

𝒜𝐌𝐎ℛ 𝒍𝑰𝑭𝑬💋💋
@amorfloodlife · 561 post𝐋۪𝐀𝕰۫𝐕𝐈𝐌 𝅥𝄀 𝐈nfo
@laevim · 2711 post

Names

Channels on the register whose handles appear in this channel's posts.

ˡᶦᶠᵉ: 🍂 𝖺 𝖻𝑒𝖺𝗍𝄞𝖿𝗎𝗅 𝖽𝖺𝗒 .. 🥠
@abetiilife · 591 post𝐀 𝐓 𝐋 𝐀 𝐍 𝐓 𝐈 𝐃 𝐀ᴴᵒᵐᵉ 16+
@Atlantidalife · 711 post𝐀 𝐓 𝐋 𝐀 𝐍 𝐓 𝐈 𝐃 𝐀 16 +
@Atlantidaprogekt · 751 post𝕮𝖔𝖓𝖘𝖙𝖊𝖑𝖑𝖆𝖙𝖎𝖔𝖓 𝕽𝖆𝖞ᴸᶦᶠᵉ
@CARayLife · 1181 post𝗖ؖ𝗵ؒ ؛𝗮ً𝘀𝗲 𝗹𝗶𝗳؈
@chasefloodlife · 671 post𝕴𝒏𝗳𝑜 ░⃝𝙲𝕙𝗮✶꯱⊹𝐒𝗖𝐫𝕚ᑭᎿֺ𓈒⁅
@CS_inf0 · 3121 post𝕷𝒊𝗳𝑒 ░⃝ℂ𝚑𝗮✶꯱⊹𝐒𝗖𝐫𝕚ᑭᎿֺ𓈒⁅
@CS_lif · 2231 post[New Era] 𝑫𝒂𝒓𝒎𝒂𝒓𝒏𝒕𝒊𝒏𝒆†
@Darmantine · 261 post[New Era] 𝑫𝒂𝒓𝒎𝒂𝒓𝒏𝒕𝒊𝒏𝒆† - 𝒉𝒐𝒎𝒆
@Darmantine_home · 251 postᰔ.𝙀lu͟͟s͟͟𝔗ve ¦︎◖︎𝘀✗︎𝔠ret𝓼 ʚɞ 𝙃𝟎mℰ
@ELsec_h0m3 · 2431 post𝙃𝙀𝙏𝙐𝙊𝙃 𝘿𝙀𝙍𝙏||𝙄𝙉𝙁𝙊
@HTD_info · 2071 post[РЕСТ] 𝙃𝙀𝙏𝙐𝙊𝙃 𝘿𝙀𝙍𝙏||𝙇𝙄𝙁𝙀
@HTD_life · 1621 post# 𝑲i͟͟s͟͟ɱꫀ𝑡 ⋮ 𝑖𝑛𝑓𝑜 ˊ˗ ¹⁴⁺
@kismetinfo · 1721 post# 𝑲i͟͟s͟͟ɱꫀ𝑡 ⋮ 𝑙𝑖𝑓𝑒 ˊ˗ ¹⁴⁺
@kismetlife · 1261 post𝐒𝐧𝐚𝐤𝐞 𝐇𝐨𝐥𝐞 (𝘪𝘯𝘧𝘰)
@krdinfo229 · 2031 post𓈒ִ ꯭ׄ ➤ 𝗂𝗇𝖿𝗈 ⸝⸝ 𝔐‼︎𝗡𝔍𝗬𝔇𝗜𝖤 ִֹ .
@mintydieINFO · 811 post𓈒ִ ꯭ׄ ➤ 𝗅𝗂𝖿𝖾 ⸝⸝ 𝔐‼︎𝗡𝔍𝗬𝔇𝗜𝖤 ִֹ .
@mintydieLIFE · 751 post𝗖𝗵𝗮𝘀𝗲 ؒ ؈𝗶𝗻𝗳ً𝗼
@modestiaxinfo · 1711 postRenasa | 𝐋۪𝐀𝕰۫𝐕𝐈𝐌
@Ranasla · 21 post𝐑𝐄𝐒𝐓! 𝓡ᴇ́ғʟᴇxɪᴏɴ 𝓓ᴇ 𝓛'ᴀ̂ᴍᴇ`𝓘𝓷𝓯𝓸
@RdL_1nfo · 1351 post𝓡ᴇ́ғʟᴇxɪᴏɴ 𝓓ᴇ 𝓛'ᴀ̂ᴍᴇ`𝓛𝓲𝓯𝓮
@RdL_l1fe · 1111 post[РЕСТ]⁺ ׅ ℒ𝘪𝘧𝘦 ℛυb͟͟𝙮 ℱe̺a̶̶s̶̶𝘁..⁺ ׅ
@RubyFeast_Life · 521 post⌗ ՞ ׅ !ׅׄ! 𝔖𝔠𝔥𝔴𝔞𝔯𝔷𝔢 ℑ𝔯𝔞𝔲𝔯𝔦𝔤𝔨𝔢𝔦𝔱 ַֿׁ 𓈒 𝅄 ‌꒱ ׂ [𝐿𝑖𝑓𝑒]
@Schwarze_Traurigkeit_Life · 1671 post[NEW ERA/РЕСТ]𝓝𝓮𝔀𝓼 𝓯𝓻𝓸𝓶 𝓸𝓾𝓻 𝓯𝓵𝓸𝓸𝓭 #𐌵T𐍃
@TomiokaUta_ShinobuLIFE · 1881 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“𝐋۪𝐀𝕰۫𝐕𝐈𝐌 𝅥𝄀 𝐀lliances” (@laevimcf), 5 subscribers as measured 13 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.