浅浅的私密分享空间 pinned a photo

Channel
浅浅的私密分享空间
@meixiBB
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,202subscribers
+513 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002736000730 |
|---|---|
| Type | Channel |
| Username | @meixiBB |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/meixiBB |
Topic
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 21:20 | 1,202 | +25 |
| 14 Sept 2026, 07:19 | 1,177 | +7 |
| 10 Sept 2026, 06:37 | 1,170 | -6 |
| 5 Sept 2026, 05:36 | 1,176 | -32 |
| 1 Sept 2026, 11:17 | 1,208 | -20 |
| 29 Aug 2026, 11:47 | 1,228 | -19 |
| 26 Aug 2026, 15:48 | 1,247 | +512 |
| 19 Aug 2026, 14:24 | 735 | +46 |
| 19 Aug 2026, 00:15 | 689 | first reading |
Engagement
19 posts held, back to 11 April 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 19 posts for this entry, the most recent from 17 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 7s
- Average length
- 7s
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.
Reaction mix
7 reactions across 7 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 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 7 of the 19 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 11 April 2026 to 17 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.
Recent posts
Photo, posted without a caption
🎉💐🎉Winner Winner🎉💐🎉 荔湾/南海可上门大胸御姐浅浅老师半价抽奖福利 @GFtongcheng 1:兑奖请联系 @GFtongcheng 2:优惠券自开奖时间起7天内有效 3:炸号者中奖作废 4:发奖人在发奖前请仔细发奖指引,以防奖品被冒领造成不必要的损失👉 https://t.me/yonglezhidao/22 5:半价券必须写报告,不写报告永久拉黑 🎫参与人数: 126|号码总数: 951 🔖中奖名单如下: 1- 塔基把喇桑[+75] 🉐: 2P优惠200 2- (v8加持) 禤[+75] 🉐: 1P优惠100 3- Mr Bette[+15] 🉐: 1P半价 4- kk v[+15] 🉐: 2P优惠200 5- 小丑鲸(噼里啪啦[+75] 🉐: 1P优惠100 6- 杰 陈[+15] 🉐: 1P优惠100 7- 史太浓 (蓝波版[+75] 🉐: 1P优惠100 8- 洛嘉[+75] 🉐: 1P优惠1…
❤1
Channel photo updated
浅浅的私密分享空间 pinned a photo
🎰荔湾/南海可上门大胸御姐浅浅老师半价抽奖福利 @GFtongcheng 🎁奖品如下: 1P半价 x 1 1P优惠100 x 5 2P优惠200 x 3 🎟参加条件: 加入-广州佛山永乐红人馆 加入-广州佛山永乐公开榜 加入-广州佛山永乐严选 加入-广佛永乐抽奖公告 加入-广州佛山永乐出击报告 加入-广州佛山黑车防爆 加入-永乐优惠券免转大厅 加入-浅浅的私密分享空间 🌕参加消耗:1永乐通宝 ➕加权消耗:10永乐通宝/次 上限5次|每次加15 此活动可消耗永乐通宝增加中奖率,点击参加按钮操作! 📝抽奖说明: 1:兑奖请联系 @GFtongcheng 2:优惠券自开奖时间起7天内有效 3:炸号者中奖作废 4:发奖人在发奖前请仔细发奖指引,以防奖品被冒领造成不必要的损失👉 https://t.me/yonglezhidao/22 5:半价券必须写报告,不写报告永久拉黑 ⏰开奖时间: 2026-05-13 18:00:00
❤1
今天在桂城呢.附近的小伙快约我吧😊😊
开课咯.怎么没有陪我玩👠💃
https://t.me/Gzffol/29621
❤1
https://t.me/GZHL01/2620613
https://t.me/guangfoyongle2020 群链接发你频道里
❤1
浅浅的私密分享空间 pinned «开课时间:中午1点到晚上12点 (本人比较懒所以课时比较短,有需要的哥哥请提前预约时间)人照合一 谢谢哥哥的理解 私聊 @GFtongcheng 双向 @GFtongchengbot»
Showing the 12 most recent of 19 posts we hold for @meixiBB. 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.
Mentions
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.
@guangfoyongle2020 · 62,1542 posts永乐TG防骗指导中心
@yonglezhidao · 7282 posts广州佛山永乐出击报告
@baogaowenxue · 21,2671 post佛山嫩妹甄选榜
@FSNMB2 · 51,3901 post佛山嫩妹甄选府
@FSNMFU · 38,8721 post嫩妹名探府【备用】
@GFMRT1 · 22,1091 post广州佛山永乐公开榜
@guangfoyongle · 47,9121 post广州佛山联邦老师榜
@Gzffol · 76,0621 post广州佛山红楼探花坊⛩
@GZHL01 · 36,3051 post广州佛山黑车防爆
@heichefangbao · 12,3621 post永乐优惠券免转大厅
@mianzhuandating · 9,4951 post佛山嫩妹【备用榜】
@NNnmbang · 15,8511 post佛山嫩妹备用榜单
@NNnmmtb · 9,7241 post佛山嫩妹甄选轮播群
@NNnmzxq · 22,0231 post广佛永乐抽奖公告
@yonglechoujiang · 13,1501 post广州佛山永乐严选
@yonglelunbo · 19,1271 post
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“浅浅的私密分享空间” (@meixiBB), 1,202 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/meixiBB.
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.