快饿死了 大家买个号支持下吧 http://aoa.aacu.cn/shop/mxkj 出问题补号售后客服 @mxsjh66
👍7❤1
Signed 频道主全网收管理@WGSJH520

Channel
@lianbingnb
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
12,402subscribers
+700 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003431972867 |
|---|---|
| Type | Channel |
| Username | @lianbingnb |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/lianbingnb |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 |
|---|---|---|
| 18 Sept 2026, 19:37 | 12,402 | +54 |
| 16 Sept 2026, 12:37 | 12,348 | +39 |
| 14 Sept 2026, 19:38 | 12,309 | +5 |
| 13 Sept 2026, 07:41 | 12,304 | +22 |
| 11 Sept 2026, 07:55 | 12,282 | +44 |
| 8 Sept 2026, 13:20 | 12,238 | +37 |
| 5 Sept 2026, 09:00 | 12,201 | +18 |
| 3 Sept 2026, 13:57 | 12,183 | +21 |
| 2 Sept 2026, 10:33 | 12,162 | +7 |
| 1 Sept 2026, 11:57 | 12,155 | +1 |
| 31 Aug 2026, 11:27 | 12,154 | +8 |
| 29 Aug 2026, 09:26 | 12,146 | +9 |
| 28 Aug 2026, 07:12 | 12,137 | -7 |
| 27 Aug 2026, 08:46 | 12,144 | +18 |
| 26 Aug 2026, 11:44 | 12,126 | +22 |
| 25 Aug 2026, 12:06 | 12,104 | +31 |
| 24 Aug 2026, 11:38 | 12,073 | +10 |
| 22 Aug 2026, 19:26 | 12,063 | +45 |
| 21 Aug 2026, 06:27 | 12,018 | +26 |
| 20 Aug 2026, 08:52 | 11,992 | first reading |
463 posts held, back to 30 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 49 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 2 September 2026 |
|---|---|
| Posts held | 463 (30 July 2026 – 2 September 2026) |
| Views total | 47,405 |
| Reactions total | 1,131 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 22:53 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.
Measured directly from 35 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.
2,778 reactions across 450 posts, in 13 distinct kinds. The most used accounts for 93.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,588 | 93.2% | |
| ❤ | 141 | 5.08% | |
| 👎 | 11 | 0.396% | |
| 🤡 | 11 | 0.396% | |
| 😱 | 10 | 0.36% | |
| 🖕 | 7 | 0.252% | |
| 😁 | 2 | 0.072% | |
| 😡 | 2 | 0.072% | |
| 🤔 | 2 | 0.072% | |
| 👏 | 1 | 0.036% | |
| 💩 | 1 | 0.036% | |
| 🔥 | 1 | 0.036% | |
| 😎 | 1 | 0.036% |
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 451 of the 463 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 2,778 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 463 most recent posts we hold, published 30 July 2026 to 2 September 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.
快饿死了 大家买个号支持下吧 http://aoa.aacu.cn/shop/mxkj 出问题补号售后客服 @mxsjh66
👍7❤1
Signed 频道主全网收管理@WGSJH520
小黄鸭补帧工具 steam原价二十多 看片看动漫都可以补帧 让你有不一样的感受你懂的🥰 #电脑工具
👍6❤1
Signed K Y
快饿死了 大家买个号支持下吧 http://aoa.aacu.cn/shop/mxkj 出问题补号售后客服 @mxsjh66
👍8
Signed 频道主全网收管理@WGSJH520
在家没有去打工的,在家闲着也是闲着 不如在线上赚点生活费,没有门槛欢迎来赚钱联系 @mili13148
👍12
14岁女初中生 被3人轮奸👀👀 处女膜被破 ‼️‼️ 「点我进机器人看视频回放」 「点我进机器人看视频回放」 「点我进机器人看视频回放」
👍12
znl团队成功正式上市 启动器下载安装即可 内置独家驱动适配全机型解密以及全机型自描 三角洲王者内部依旧稳定 解密依旧稳定客户从未拉闸过 无视所有下发加密🔐无视闪框 赞助网址↓ https://shop.bromk.cn/shop/lnzZ [全网最低价内部价格亲民] znl团队打造三角洲 + 王者荣耀持续更新中… znI团队出品必是精选频道加入↓ https://t.me/CountNb https://t.me/CountNb https://t.me/CountNb https://t.me/CountNb
👍3❤2
快饿死了 大家买个号支持下吧 http://aoa.aacu.cn/shop/mxkj 出问题补号售后客服 @mxsjh66
👍4
Signed 频道主全网收管理@WGSJH520
在家没有去打工的,在家闲着也是闲着 不如在线上赚点生活费,没有门槛欢迎来赚钱联系 @mili13148
👍4
14岁女初中生 被3人轮奸👀👀 处女膜被破 ‼️‼️ 「点我进机器人看视频回放」 「点我进机器人看视频回放」 「点我进机器人看视频回放」
👍5
洛月体验服 直装 更新 修复兵线美化 修复按键美化 UC网盘 https://drive.uc.cn/s/7ddd305e70684?public=1 电报群 https://t.me/lianbingnb
👍14
dogzbq ue4dump工具 支持 腾讯所有吃鸡吃鸡游戏 如和平暖暖与PUBG #dogzbq
👍9
Signed K Y
启动器更新2.0.2 ◾️修复一些bug,修复一些逻辑问题 ◾️优化部分动画效果 ◾️修复随机包名无效果问题 ◾️修复无法自动删除下载文件问题 支持巴巴托斯三个辅助的启动[巴巴托斯,衍生和腹黑后妈],支持云端拉取下载,内置驱动刷取,辅助配置更改,以及包名随机和路径加密等功能,衍生支持和平,巴巴托斯支持pubg,腹黑后妈支持第五人格,我是巴巴托斯新人,我会认真听取你们有关启动器优化的意见,有问题反馈! https://drive.uc.cn/s/5f19aa98f1e04?public=1 公益频道 https://t.me/BBTSNHNB1 #第五人格 #公益 #内核 #巴巴托斯 #和平精英 #pubg
👍8❤1
Showing the 12 most recent of 463 posts we hold for @lianbingnb. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
cfm有人玩吗
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 463 most recent posts we hold, published 30 July 2026 to 2 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 5 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.
@lianbingnb named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“洛月【公益】” (@lianbingnb), 12,402 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/lianbingnb.
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.