Channel
@beibei655
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,976subscribers
+1,958 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003888543085 |
|---|---|
| Type | Channel |
| Username | @beibei655 |
| Created | 6 August 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/beibei655 |
Adult — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 16 Sept 2026, 20:59 | 1,976 | -125 |
| 12 Sept 2026, 15:15 | 2,101 | -57 |
| 8 Sept 2026, 20:01 | 2,158 | -4 |
| 3 Sept 2026, 20:21 | 2,162 | +13 |
| 31 Aug 2026, 01:34 | 2,149 | +14 |
| 28 Aug 2026, 05:05 | 2,135 | +23 |
| 25 Aug 2026, 03:56 | 2,112 | +1 |
| 21 Aug 2026, 13:09 | 2,111 | +1 |
| 18 Aug 2026, 02:02 | 2,110 | +4 |
| 14 Aug 2026, 17:53 | 2,106 | +2,084 |
| 11 Aug 2026, 13:02 | 22 | no change |
| 7 Aug 2026, 14:40 | 22 | +4 |
| 7 Aug 2026, 13:08 | 18 | first reading |
13 posts held, back to 6 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 1 page of 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 13 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 75.0% | |
| 😁 | 1 | 25.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 3 of the 13 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 6 August 2026 to 10 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.
派大星出击报告 验证留名：poou 验证时间：8.9 老师花名：#蓓蓓 城市坐标：#深圳 #南山 上课花费：900p 颜值身材：9 分 服务内容：xcz69舌吻 出击体验：第一次写报告，奉献给老师了，进门第一眼就被吸引住目光，老师穿了件低胸包臀裙，女人味十足，一对大白兔就在眼前晃动，脸又是嫩妹，有反差感。废话不多说交了水费开使流程，老师帮忙洗澡很温柔，轻声细语问水温合适吗，态度很好。主动和老师聊天句句有回应。课表上有的服务都做了，口活超级舒服没有齿感，差点忍不住交枪，赶紧戴上套套老师女上位，坐在上面很会动，一会有点体力不支娇羞地说哥哥来动，换后入大屁股手感很软 蜜桃臀，在小穴里快速抽插，屁股一直顶我，视觉冲击力拉满，在老师的一句句骚话和娇媚叫床声中123下课。值得二刷！ 优点缺点：小嘴很甜，房间还有漱口水 推荐程度：10/满分10.0分；（综合硬件（脸，熊，身材）和软件（服务，态度)等方面打分。自己更看重哪方面，给出打出这个分数…
派大星出击报告 验证留名：koou 验证时间：8.7 老师花名：#蓓蓓 城市坐标：#深圳 #南山 上课花费：900p 颜值身材：9 分 服务内容：xcz69舌吻 出击体验：约好时间到达课室后进门看到妹妹，很满意交了课费，简单帮我擦干很细心，妹妹舌头亲上而耳垂很敏感的地方，妹妹舌头很软糯，一路向亲了一会，之前舌吻一阵，她吃我口水，我吃她口水很爽。开始换我品尝妹妹白嫩充满青春气息的身体，揉捏吸舔妹妹的大咪咪,又轻轻亲小白虎，品尝妹妹的小穴，很粉嫩 ，来感觉了带伞就开始做爱，换了3 个姿势汹涌而出 ，很爽满意👍 优点缺点：小嘴很甜，房间还有漱口水 推荐程度：10/满分10.0分；（综合硬件（脸，熊，身材）和软件（服务，态度)等方面打分。自己更看重哪方面，给出打出这个分数的理由） 联系方式： @beibei534 （提交报告需要提供相关资料，如聊天记录，付款记录等）
❤1
真胸，没科技
穿什么都好看
❤1😁1
开课了，预约中
⚡️地区：南山蓓蓓 ⚡️私聊：@beibei534 ⚡️频道：@beibei655 #嫩妹 #舌吻 #六九 #丝袜 #南山
Video, posted without a caption
Video, posted without a caption
❤1
宝安 蓓蓓（童颜巨乳） pinned a video
私聊 @beibei534
宝安 蓓蓓（童颜巨乳） pinned Deleted message
Photo, posted without a caption
Showing the 12 most recent of 13 posts we hold for @beibei655. 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.
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 1 registered channel — 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“宝安 花花😘雯宝(双飞)” (@beibei655), 1,976 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/beibei655.
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.