扎啤
👍23🙏4
Signed 小宇
![Telegram profile photo for KK数据号[全游戏]](https://cdn.tgregister.com/av/ce/ce9f8fcee53ce9fdb3e31f40a746edf3d73f2d0a9a6cdc1070c6599c24edbd6d.jpg)
Channel
@LANM8
On this record: Topic · Previous handles · Growth · Engagement · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
1,037subscribers
-8,182 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002343653093 |
|---|---|
| Type | Channel |
| Usernames | @DNFMY9 @LANM8 @ZoloCheatGFP |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/LANM8 |
Hacking & security — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 42% 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.
@LANM8 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 14:58 | 1,037 | -8,728 |
| 13 Nov 2026, 11:00 | 9,765 | +8,747 |
| 9 Nov 2026, 10:56 | 1,018 | -8,784 |
| 8 Nov 2026, 17:50 | 9,802 | -19 |
| 5 Nov 2026, 11:47 | 9,821 | -4 |
| 4 Nov 2026, 17:22 | 9,825 | +8,901 |
| 2 Nov 2026, 08:16 | 924 | +166 |
| 25 Oct 2026, 16:30 | 758 | -9,074 |
| 25 Oct 2026, 07:00 | 9,832 | -2 |
| 22 Oct 2026, 04:21 | 9,834 | +6 |
| 18 Oct 2026, 21:09 | 9,828 | +9,185 |
| 18 Oct 2026, 15:28 | 643 | -9,086 |
| 15 Oct 2026, 18:39 | 9,729 | +9,728 |
| 13 Oct 2026, 14:48 | 1 | -9,698 |
| 12 Oct 2026, 18:18 | 9,699 | +9,064 |
| 10 Oct 2026, 21:00 | 635 | -8,941 |
| 8 Oct 2026, 18:48 | 9,576 | +96 |
| 4 Oct 2026, 14:20 | 9,480 | +203 |
| 26 Sept 2026, 22:22 | 9,277 | no change |
| 26 Sept 2026, 21:47 | 9,277 | first reading |
61 posts held, back to 26 September 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 15 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 61 (26 September 2026 – 14 November 2026) |
| Views total | 9,077 |
| Reactions total | 669 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 13:18 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
727 reactions across 60 posts, in 11 distinct kinds. The most used accounts for 94.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 687 | 94.5% | |
| ❤ | 14 | 1.93% | |
| 🤣 | 9 | 1.24% | |
| 🖕 | 4 | 0.55% | |
| 🙏 | 4 | 0.55% | |
| 🔥 | 3 | 0.413% | |
| 👏 | 2 | 0.275% | |
| 🍌 | 1 | 0.138% | |
| 😱 | 1 | 0.138% | |
| 🤔 | 1 | 0.138% | |
| 🥰 | 1 | 0.138% |
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 60 of the 61 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 727 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 61 most recent posts we hold, published 26 September 2026 to 14 November 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.
Telegram’s own ‘edited’ marker: 1 of 48 posts held from the last 30 days (2.08%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
扎啤
👍23🙏4
Signed 小宇
🔠🔡🔡🔡🔡🔡🔡三角粥公益直装 本项目由俄罗斯顶级作者开发 并研究出来了全网独家稳定不遁地的完全稳定性! 🎮当前适配三角洲国服 (后续即将适配台服/国际服) 👍详细功能介绍🔸 😄独家过检测思路为你保驾护航 😃独家陀螺仪自瞄 安全稳定枪枪到肉 😄全面优化深层CPU占比 绘制稳定流畅 😃还有全物资价值绘制 跑刀的专属选择 😄可选择开启防录屏 可供直播接单等使用 #⃣船长V3版本下载链接: https://wwwa.qyshare.com:2083/s/ijmwha 😇🙃😉:@CZNB616 😇🙃😉:@CZNB616 😇🙃😉:@CZNB616 🤣公益卡密: GYKMFD8A7B5E372EC3BD5D896E3C646E 🥰全网收频道广告位!无要求和限制! 联系 @Nian1960
👍19❤4
Signed 引路人
Photo, posted without a caption
👍13
📱短视频平台发布白玉京瓦手活动 发布任意关于白玉京瓦手直装视频 😙标题 #白玉京直装 #无畏契约 #手瓦 ☺️然后置顶上方图片注意切号看一下有没有置顶 😄3000播放量加20点赞 奖励白玉京天卡加8.88 😄5000播放量加30点赞 奖励白玉京三天卡加18.88 😄10000播放量加50点赞 奖励白玉京周卡加38.88 👑领活动在线客服 @xy15932
👍11❤1
Signed 小宇
Photo, posted without a caption
👍8
Signed 小宇
🎮白玉京无畏契约3.0(容器)版本 装载机1.0版本 这次打造全网最稳的直装 不吹任何牛逼 亲身体验才知道 😙功能介绍:人物自瞄/人物绘制/人物方框/人物血量/名称绘制/ ⏩目前全网7天/十年/三方问题一直困扰兄弟们 白玉京携手顶尖团队 诚意打造全网功能最全 稳定性拉满的直装 ✅️下载地址 https://drive.uc.cn/s/30ab4d985e7a4?public=1 🥚赞助地址 https://911.x9ynb.cn/shop/THL02SE8 查卡地址 http://llua.cn/?mod=cardcheck&id=47258 问题咨询/反馈合作 @xy15932
👍10❤1🔥1🤔1
再他妈不反馈,那我就删卡了
👍8🖕4🤣1
Photo, posted without a caption
👍8
Photo, posted without a caption
👍8
Photo, posted without a caption
👍8
3.0有问题
👍17
所有人去玩2.0
👍17
Showing the 12 most recent of 61 posts we hold for @LANM8. 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.
We recorded 1 post on @LANM8 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“KK数据号[全游戏]” (@LANM8), 1,037 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/LANM8.
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.