Channel
@Levilde_Luminia
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
6,770subscribers
+1,092 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002194635034 |
|---|---|
| Type | Channel |
| Username | @Levilde_Luminia |
| Created | 23 October 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/Levilde_Luminia |
Giveaways & airdrops — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 23:57 | 6,770 | +1 |
| 9 Nov 2026, 03:09 | 6,769 | +36 |
| 5 Nov 2026, 13:11 | 6,733 | +18 |
| 2 Nov 2026, 13:54 | 6,715 | +12 |
| 30 Oct 2026, 16:57 | 6,703 | +18 |
| 27 Oct 2026, 15:50 | 6,685 | +28 |
| 24 Oct 2026, 06:38 | 6,657 | +26 |
| 21 Oct 2026, 16:31 | 6,631 | +27 |
| 18 Oct 2026, 18:28 | 6,604 | +37 |
| 15 Oct 2026, 09:56 | 6,567 | +95 |
| 12 Oct 2026, 09:17 | 6,472 | +656 |
| 5 Oct 2026, 09:17 | 5,816 | +184 |
| 27 Sept 2026, 01:21 | 5,632 | -23 |
| 17 Sept 2026, 16:01 | 5,655 | -2 |
| 13 Sept 2026, 20:36 | 5,657 | -5 |
| 10 Sept 2026, 03:15 | 5,662 | -9 |
| 4 Sept 2026, 15:42 | 5,671 | +6 |
| 1 Sept 2026, 07:37 | 5,665 | -8 |
| 29 Aug 2026, 17:44 | 5,673 | +9 |
| 26 Aug 2026, 14:04 | 5,664 | first reading |
9 posts held, back to 23 October 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 20 pages 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 9 posts for this entry, the most recent from 24 September 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 November 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.
🎉临境享境中秋国庆双节特惠来啦 🎉 双节期间，全场享 88 折优惠 充值按照 1.13 倍倍率到账（实际折算约为 88 折） 本次优惠活动截止至 10 月 7 日，有需要的朋友可以按需充值 另外，截至今晚，现有用户的公费时长统一顺延 10 天，感谢大家一直以来的支持😝 假期难得，希望大家少看片，多陪陪家人😄 祝大家双节快乐，假期愉快！🎉(＾▽＾)🎉 ———————————— ⭐️ 临境 Liminal EA 「10CNY/月起」 ✅ 60W+ 高码资源 ✅ 全新 EA 架构加持 ✅ 混合架构硬盘缓存新增至100T ⭐️ 享境 Luxrealm EA 硬盘服 「5CNY/月起」 ✅ 30W+ 精品中低资源 ✅ 全新 EA 架构加持 ✅ 全新硬盘架构秒拖秒拉无压力 ⚡购买入口点这里⚡ 临境 频道： @LiminalChannel 临境 群组： @Liminal_E…
更新完毕，更新内容 1. 更换 EA 架构，起播更快更稳定 请自行去 bot 重置密码使用，有问题随时反馈
🎉 临境周年庆 & 星星频道万人订阅抽奖 六一儿童节快乐♪٩(´ω`)و♪ 🎁 抽奖活动已开始！ ━━━━━━━━━━━━━━ ⏰ 截止时间：2026年6月3日 18:00:00 🎁 奖品： ▸ 临境公益服 注册码 x61 ▸ 临境公益服 白名单 x1 ▸ Vidhub 永久 x1 📣 发布群组： ▸ 临境 Liminal 2.0 ▸ 星星的集邮地 ▸ 星星的 Emby & 机场指南 📋 参与要求： ▸ 订阅 星星的 Emby & 机场指南 ▸ 订阅 临境 Liminal 2.0 ▸ 订阅 星星的集邮地 🔑 口令：临境生日快乐～ 👥 好友裂变奖励 每邀请 5 位好友参与，提高中奖机率！ ━━━━━━━━━━━━━━ 🍀 祝所有参与者好运！
换库完毕 🎬 电影数量：23201 📽️ 剧集数量：13286 🎵 音乐数量：0 🎞️ 总集数：479067
Levilde · Luminia 2.0 正式回归 💝 全新版本上线，系统与体验全面升级。🥳 🥰本周日晚上 9 点 将开放 100 个注册名额。 同时，在未来一周内， 我们会在群里不定时随机发放共 50 个注册码。 谢谢大家这段时间的等待 💝 如有问题随时联系客服 @LiminalSupport_bot 发电可点击 https://levilde.shop
Channel name was changed to «Levilde Luminia 通知频道»
简单省流一下，就是 1. 即日起本服的维护交予临境团队维护，服务依旧维持独立运营 2. 保号方式转为签到保号 3.旧有白名单用户凭收据发给如此，重新开白
Levilde Luminia 祝全球华人农历新年快乐 农历新年是拜年的重要时间，因此走亲访友、互致吉祥、拜年是家常便饭。 中国礼品，包括曾经风靡一时的幸运红包，里面装满了 中国货币。 虔诚的佛教徒和道教徒也经常到当地寺庙迎接新年。
Channel created
Showing the 9 most recent of 9 posts we hold for @Levilde_Luminia. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“Levilde Luminia 通知频道” (@Levilde_Luminia), 6,770 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/Levilde_Luminia.
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.