上古真神葫芦侠回归 葫芦侠独家功能: 刷流量 刷话费 刷各种平台会员 可刷一切 📱快手区:播放量 点赞 关注 评论 🗑抖音区:播放量 点赞 关注 评论 📖QQ区:名片赞 说说赞 😀游戏区:和平 蛋仔 无畏契约王者 三角洲 火影 均可刷点券 有更多功能自己下载体验 🔥其他黑科技:伪装机型 刷qq会员 跳卡网支付 ai脱衣 刷话费等等🎮 网盘下载链接点击下载 密码8888⚠️关闭VPN下载 葫芦侠网页版点进直接使用 一次性费用购买后真无限使用 软件已对接18000个不同ip账号 欢迎各位老板前来使用 请勿用与非法途径!!! 点击加入官方频道 认准唯一200k频道其他为假冒

Channel
绫波丽直装官方频道
@LBLMOD
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
18,174subscribers
-2,025 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003216724431 |
|---|---|
| Type | Channel |
| Usernames | @LBLMOD @REXNB91 |
| Description | 免责声明 1.本频道所有产品仅供于测试,严禁用于一切非法使用,任何非法造成的后果用户自行承担。 2.本频道不对通过本频道提供的任何外部链接访问的网站网站内容或者安全性承担任何责任。 3.若侵犯了您的合法权益以及出现侵权行为,请及时联系我们沟通 |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/LBLMOD |
Topic
Marketing & affiliate — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 05:48 | 18,174 | +128 |
| 13 Nov 2026, 05:22 | 18,046 | +18,009 |
| 13 Nov 2026, 03:47 | 37 | -19,276 |
| 4 Oct 2026, 15:58 | 19,313 | -111 |
| 26 Sept 2026, 11:41 | 19,424 | -147 |
| 19 Sept 2026, 08:57 | 19,571 | -42 |
| 16 Sept 2026, 23:37 | 19,613 | -32 |
| 15 Sept 2026, 03:15 | 19,645 | -18 |
| 13 Sept 2026, 11:58 | 19,663 | -37 |
| 11 Sept 2026, 14:37 | 19,700 | -80 |
| 8 Sept 2026, 20:37 | 19,780 | -88 |
| 5 Sept 2026, 10:38 | 19,868 | -59 |
| 3 Sept 2026, 15:02 | 19,927 | -16 |
| 2 Sept 2026, 07:58 | 19,943 | -18 |
| 1 Sept 2026, 07:37 | 19,961 | -12 |
| 31 Aug 2026, 04:38 | 19,973 | -11 |
| 30 Aug 2026, 03:44 | 19,984 | -35 |
| 29 Aug 2026, 01:37 | 20,019 | -34 |
| 28 Aug 2026, 02:35 | 20,053 | -18 |
| 27 Aug 2026, 05:24 | 20,071 | first reading |
Engagement
148 posts held, back to 8 August 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 53 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.98%
- avg views ÷ 18,174 subscribers
- Avg views / post
- 361
- 67 posts measured
- Reaction rate
- 0.672%
- reactions ÷ views · ER floor
- Posts in window
- 67
- of 148 held
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. It is computed over the 7 of 67 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 148 (8 August 2026 – 17 November 2026) |
| Views total | 24,155 |
| Reactions total | 15 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 06:42 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.
What this channel posts
- Photos
- 55
- Videos
- 2
- Links
- 5
Lifetime counters from Telegram’s own channel header, read 17 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.
- Video runtime
- 1m 59s
- Average length
- 40s
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.
Reaction mix
130 reactions across 34 posts, in 12 distinct kinds. The most used accounts for 36.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😭 | 48 | 36.9% | |
| 🫡 | 26 | 20.0% | |
| 🥰 | 18 | 13.8% | |
| 😍 | 8 | 6.15% | |
| 🤩 | 8 | 6.15% | |
| 🤪 | 8 | 6.15% | |
| 🏆 | 7 | 5.38% | |
| ❤🔥 | 2 | 1.54% | |
| 🍌 | 2 | 1.54% | |
| 🐳 | 1 | 0.769% | |
| 💯 | 1 | 0.769% | |
| 🤓 | 1 | 0.769% |
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 34 of the 148 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 130 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 148 most recent posts we hold, published 8 August 2026 to 17 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.
Recent posts
Telegram’s own ‘edited’ marker: 3 of 67 posts held from the last 30 days (4.48%) 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).
Photo, posted without a caption
宝贝最强反馈
Photo, posted without a caption
会控分就封不了😘
这个号拿伯乐控分打一辈子
3打上了70分
Photo, posted without a caption
有一个号超1到超3打得有点猛封了一天,现在这个钻石到超凡还没封
上古真神葫芦侠回归 葫芦侠独家功能: 刷流量 刷话费 刷各种平台会员 可刷一切 📱快手区:播放量 点赞 关注 评论 🗑抖音区:播放量 点赞 关注 评论 📖QQ区:名片赞 说说赞 😀游戏区:和平 蛋仔 无畏契约王者 三角洲 火影 均可刷点券 有更多功能自己下载体验 🔥其他黑科技:伪装机型 刷qq会员 跳卡网支付 ai脱衣 刷话费等等🎮 网盘下载链接点击下载 密码8888⚠️关闭VPN下载 一次性费用购买后真无限使用 软件已对接18000个不同ip账号 欢迎各位老板前来使用 请勿用与非法途径!!! 点击加入官方频道 认准唯一200k频道其他为假冒
🤪1
绫波丽瓦手最新公益卡密已经在置顶公告更新了 宣传越多公益时间越长 ‼️不宣传=不公益‼️ 📣和平静等更新...
D0C2A2311B3A898A5C91D2B84D741937
Showing the 12 most recent of 148 posts we hold for @LBLMOD. 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.
Posts recorded as deleted after publishing
We recorded 8 posts on @LBLMOD 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.
- First seen missing
- 15 August 2026
- Most recent seen missing
- 15 November 2026
- Median time before seen missing
- 17 hours
- Seen missing in the last 30 days
- 3
Forward network
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.
Mentions
Named by 3 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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“绫波丽直装官方频道” (@LBLMOD), 18,174 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/LBLMOD.
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.