Channel
@liangbogege
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
21subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002281784828 |
|---|---|
| Type | Channel |
| Username | @liangbogege |
| Created | 3 April 2025 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/liangbogege |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 14:46 | 21 | no change |
| 7 Aug 2026, 16:29 | 21 | first reading |
12 posts held, back to 3 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 26 September 2025. An engagement rate over an empty window would be a number about nothing.
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 5 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.
19 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 78.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 78.9% | |
| 👍 | 3 | 15.8% | |
| 🔥 | 1 | 5.26% |
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 6 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 19reactions 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 3 April 2025 to 26 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
😘😘😘😘😘😘【欧易担保，守护每一份押金】 尊敬的公群老板及合作伙伴： 近期，我们痛心地关注到担保界内接连发生的担保风波——从YY担保的“钱包被盗”事件，到UU担保再次以“用户名钱包被盗”为由造成各位老板的押金损失，这些异常相似的剧情不仅让众多公群老板蒙受经济损失！ 更让人质疑 “二哥“ 是否将 “担保” 本质异化为资金盘，背离了担保保障交易安全的初心。 欧易担保对此深感愤慨与惋惜。我们坚信，担保服务的核心是责任、透明与守护，而非利用信任机制套取资金。为切实帮助受损公会重建运营信心，欧易担保郑重推出以下扶持计划： 🔹 专项补偿通道：YY/UU受害公群专属权益 1. 公群月租减免政策 · 受影响公群老板入驻欧易担保，押金满2个月申请退押时，仅收取20U手续费（原周期为3个月） 2. 长效运营奖励 · 欧易公群上押满3个月的公群，除全额退还押金外，欧易担保额外奖励66U · （注：公群需在三个月内保持正常运…
❤6
😘欧易能给你的只有财富 USDT😘 😘😘😘😘😘😘😘
梁博 @zulu ：不是你太死板，只因你没开 #揽胜行政加长版
梁博 @zulu：无人懂我来时路 好似孤山起了雾. #路虎揽胜
我梁博 @zulu 立的不是志 是落魄不甘时 偏要争的这一口气
❤4
秦王嬴政比我早生千年 是惧我三分还是王不见王？
❤1🔥1
梁博 @zulu ：我的心不大 只有你和天下
❤1
梁博 @liangboge 这首《出现又离开》，告诉我们这世上，很多人本来都是毫无关联的在这个世界里各自存在，是因为一些偶然或意外，缘分或者命运的安排，一些本来毫无关系的人的命运才开始有了交集。一生很长，要明白总会有人出现或离开，所以至此流年，别在徘徊，过去的没人愿意重来，未来的我们要好好期待
送钱都不要？
✨ 【赌石活动】 🎁 欢迎参加我们的超值活动！邀请朋友一起来赌石，开启惊喜大奖！ 🎉 点击下方按钮开始吧！
😘😘😘😘😘😘😘😘😘 认准欧易官方工作人员： 😘担保负责人：@oyoy +888 0759 6528 😘纠纷客服： @zulu +888 0962 5172 😘宣传客服： @ag99 +888 0625 7091 😘广告客服： @oyook +888 0273 9654 😘推广客服： @oyoom 欧易担保现在 300U 起押，所以很好分辨，（假押整体都是把自己群押金设置很高，整体押金几千上万都是假押） 我们处于网络上，让你转账的都是（骗子、杀鱼）切记千万不要向任何人转账 验真假押群，进入 @oydb_bot 之后，输入公群的编号，发送给机器人，…
❤3👍3
Channel created
Showing the 12 most recent of 12 posts we hold for @liangbogege. 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“梁博朋友圈” (@liangbogege), 21 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/liangbogege.
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.