Channel
@LM_XC_ZN
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,694subscribers
+444 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003346673163 |
|---|---|
| Type | Channel |
| Username | @LM_XC_ZN |
| Created | Between 1 November 2025 and 27 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/LM_XC_ZN |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 14:02 | 2,694 | +24 |
| 12 Sept 2026, 05:19 | 2,670 | +45 |
| 7 Sept 2026, 13:00 | 2,625 | +43 |
| 2 Sept 2026, 21:34 | 2,582 | +32 |
| 30 Aug 2026, 15:37 | 2,550 | +34 |
| 28 Aug 2026, 02:06 | 2,516 | +17 |
| 25 Aug 2026, 03:02 | 2,499 | +31 |
| 21 Aug 2026, 08:04 | 2,468 | +39 |
| 18 Aug 2026, 12:54 | 2,429 | +38 |
| 15 Aug 2026, 02:37 | 2,391 | +59 |
| 11 Aug 2026, 09:12 | 2,332 | +64 |
| 8 Aug 2026, 02:00 | 2,268 | +18 |
| 7 Aug 2026, 14:19 | 2,250 | no change |
| 7 Aug 2026, 14:02 | 2,250 | first reading |
15 posts held, back to 27 February 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 15 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
22 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 54.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 12 | 54.5% | |
| ❤ | 9 | 40.9% | |
| 🏆 | 1 | 4.55% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 10 of the 15 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 27 February 2026 to 30 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
新人必读 TG常见骗术介绍： 1、冒充官方账号发送链接 不要随意点击陌生人发送的任何文件和链接，对方发送的很可能是木马文件或者是自动下载脚本的链接，点击后就会危害到你的电脑，有被盗号甚至其他更严重的风险。即便遇到以飞机官方名义发送的任何文件与链接都不要点击，点进去号就会被盗。 2、冒充好友让协助解封 有时会遇到一些人假冒好友以帮助解封为由让帮忙收验证码，实则是在登录你的账号，对方会骗取你的验证码或聊天界面的截图，从而盗取你的账号。切记！登录验证码不要外泄！！ 3、冒充飞机官方的诈骗信息 诈骗短信冒充Telegram 官方账号，声称该用户的TG 账号违反了账号使用规则将被限制使用，需要登陆网站解除受限。如果用户不慎点击链接，账户就会被盗。 4、声称无法私聊让你去解除 诈骗分子会发一张他制作的假图，声称有他所谓的小号或者其他人无法私聊你，让你去私聊他发给你的假冒官方解除私聊机器人，诱导你发送自己的号码和验证码，从而完成盗号 …
👍1
⚠️ 防盗号提醒！ 凡是收到此类消息千万别信，不管是谁发给你的，只要声称你的账户有问题都是盗号的！ 电报官方不会主动给你发送中文消息，更不会私聊向你索要手机号、验证码等信息。
夜游快乐指南 pinned «中山,珠海的上榜权限,这个周末,我会全部回收 自此,中山,珠海的上榜,全面会由我来亲自接手 上榜的,不要给我扯皮,我不会跟你们说那么东西,让你们改,就按提示改 别跟我扯皮,我不会搭理你! 之后,老师活动,会专门安排人进行对接 所有的活动,都必须通过机器人进行添加,推送.»
中山,珠海的上榜权限,这个周末,我会全部回收 自此,中山,珠海的上榜,全面会由我来亲自接手 上榜的,不要给我扯皮,我不会跟你们说那么东西,让你们改,就按提示改 别跟我扯皮,我不会搭理你! 之后,老师活动,会专门安排人进行对接 所有的活动,都必须通过机器人进行添加,推送.
👍4
https://t.me/qwert63512
夜游快乐指南 pinned «中山群,我会重开一个新的班底 重开一个新的中山群 我会让2个中山群互相竞争 最后,那个做的更好,就留下 最近我会留意,群里活跃度用户 我至少需要1个话事人,1个主要管理,2-3个辅助的管理»
中山群,我会重开一个新的班底 重开一个新的中山群 我会让2个中山群互相竞争 最后,那个做的更好,就留下 最近我会留意,群里活跃度用户 我至少需要1个话事人,1个主要管理,2-3个辅助的管理
👍2
#广东联盟论坛TG账号绑定教程
❤1
#广东联盟论坛注册教程(基于TG的安卓篇)
❤2
论坛是我们长期运营下去的 但是,论坛的局限性,它是无法,也不可能取代主流的聊天软件 更别说像TG这种全球知名的聊天软件 但是我希望论坛可以作为一个根据地 你可以不用! 但是你得有! 必要时,你能够在上面找到你想要的东西! 可能是一个色色的小说,漫画 甚至是一个机场 又或者是一个会所,老师的出击体验! 除了一开始这种完整的注册视频 一些能增加论坛使用体验的设置教程 都会得到奖励 这个教程,算是IOS比较完整的教程了 这种完整的教程,奖励会比较丰富 你们也可以做一些小的补充,并不一定是视频 不会做视频,直接发教程帖子也是一样,同样也会获得奖励 ———————- 事实上,现在邀请人的长期任务是1个人2块钱 但是,这要求是活人 所以,我设置要求,注册后需要到TL1才算 问题是,这样你们的体验就会很差 如果拉一个就涨一个,你们会有动力很多 但是这样的垃圾账号,我们都不太喜欢,之后还需要站长花时间去删除这种长期不登录的账号 有时候,很…
❤2
#广东联盟论坛注册教程(ios)
❤1
我的机器人 @gjhgkjhslikjdlkas_bot 已经更换了新的版本 所有需要联系的人,都需要重新启动我的机器人 否则我无法主动联系你们
Showing the 12 most recent of 15 posts we hold for @LM_XC_ZN. 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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“夜游快乐指南” (@LM_XC_ZN), 2,694 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/LM_XC_ZN.
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.