Channel
@lianlianbs
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
19subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002456015754 |
|---|---|
| Type | Channel |
| Username | @lianlianbs |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lianlianbs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 16:31 | 19 | no change |
| 6 Aug 2026, 20:04 | 19 | first reading |
12 posts held, back to 8 April 2025 — 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 pageof 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 11 August 2026 |
|---|---|
| Posts held | 12 (8 April 2025 – 11 August 2026) |
| Views total | 2 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 16:31 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.
Lifetime counters from Telegram’s own channel header, read 11 August 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.
Measured directly from 1 video 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 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 1 of the 12 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 8 April 2025 to 11 August 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.
来自速搜推荐 @SSOU 📢缅甸赌场-华纳赌场-万宝... 📢欧博官网|亚星官网|欧博... 📢侏罗纪世界|史前巨兽|恐... 📢A股市-A股，股票，博彩... 📢海外精聊盘-外汇-币盘合... 📢福布斯平台 福布斯真人 ... 📢影视剪辑|无缝衔接|治愈... 📢游戏乐人间 📢屁眼,爆菊,肛交 📢环球360网址 环球36... 📢东南亚新闻 @U9U77 📢AG代理 AG官网 AG... 📢环球360代理 环球36... 📢華人今日網 📢欧博百家乐 亚星百家乐 ... 👉流量互推规则介绍💥 以下是广告推荐 📢 X-panel 一站式拉人增粉平台 📢🔰开元官方🔥代理70%|电子棋牌|AG百家乐 📢⚽️爱博体育-佣金55%-玩家首存即升VIP7等级⚽️ 🚀蓝图数据🚀SDK+DPI｜106通道技术分析全行业💰技术实力诚邀合作🔥 📢 Ton 中文索引 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpB…
来自速搜推荐 @SSOU 📢AG亚游-体育-电竞彩票 📢安娜 📢百家乐-龙虎-德州-赌博... 📢妮妮💞🌍爱中国 📢动漫频道 📢菲菲裸聊馆👅超多大胸妹... 📢宜昌MMC 📢未来电影 独一无二 深耕... 📢AG官网-新博88-万博... 📢奇葩挑战|欢乐😄狂飙 📢皇冠代理 皇冠体育 皇冠... 📢腾龙赌场|西班牙赌场 📢黑料曝光/黑台曝光/东南... 📢Telegram知识库 📢德国巴登巴登赌场--金... 👉流量互推规则介绍💥 以下是广告推荐 📢 X Panel 商店 [主营：苹果ID] 📢东南亚今日头条|新闻|爆料|悬赏|通缉|吃瓜缅甸妙瓦底大揭 📢✅金边娱乐城✅全网上押800万u盘总聚集地 📢 全网最全面、最便宜的自助引流服务 📢联盟数据Data 全行业数据，sdk dpi源头直出欢迎合作 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员，即可在2000+频道
来自Ton流量小助手推荐 📢小Lin说 📢国际先生韩国美男 Mis... 📢珂珂Coco🥰 📢telsa 塔尔萨 📢CCTV电视剧 📢奇妙动画馆 📢憨人疼天宫 📢周杰伦 Jay Chou 📢热点恋综|奇葩情侣|变态... 📢北方姑娘 📢浙江修车 浙江外围 浙江... 📢冷知识|神秘恐怖灵异|脑... 📢Bubble Chann... 📢撩妹|啪啪|兩性密碼🫦... 📢10元一件 女大学生 原... 👉流量互推规则介绍💥 以下是广告推荐 📢 X-panel 一站式拉人增粉平台 📢蕾丝舞社官方频道 📢 TeleTop 中文索引 📢 X Panel 商店 [主营：苹果ID] 📢摩根体育官方招商 55%佣金分红 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员，即可在2000+频道进行互推曝光，实现订阅快速增长。
午休午休。
放下个人素质，享受缺德人生。
高铁上！
有人说我脸大，笑死，没文化真可怕，这叫宽容。
叫阿姨。
周末结束，明天上班。
告诉你们一个变开心的小妙招：遇事先肯定自己，然后再啃点东西…
❤2
几年没见，甚是想念。
西北风，那个吹！
Showing the 12 most recent of 12 posts we hold for @lianlianbs. 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.
Citation-graph rank — 550,714 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 37 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@lianlianbs 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“依依不舍” (@lianlianbs), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/lianlianbs.
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.