Telegram RegisterThe public register of Telegram
Telegram profile photo for 龙岗坂田19岁贝贝的小窝

Channel

龙岗坂田19岁贝贝的小窝

@baibi66

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,754subscribers

+34 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002814129979
TypeChannel
Username@baibi66
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live18 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/baibi66

Growth

1,7201,7541,73714 August 2026 — 1,720 subscribers14 August 2026 — 1,720 subscribers15 August 2026 — 1,748 subscribers18 August 2026 — 1,754 subscribers14 August 202618 August 2026
4 measurements spanning 4 days, net +34. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,715–1,759 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 01:181,754+6
15 Aug 2026, 00:571,748+28
14 Aug 2026, 07:011,720no change
14 Aug 2026, 06:491,720first reading

Engagement

20 posts held, back to 30 July 2026the 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 · 30 days
44.9%
avg views ÷ 1,754 subscribers
Avg views / post
787
20 posts measured
Reaction rate
0.12%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

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. It is computed over the 6 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held20 (30 July 202614 August 2026)
Views total15,741
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 07:01 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.

What this channel posts

Video runtime
1m 10s
Average length
18s

Measured directly from 4 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.

Reaction mix

8 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
787.5%
🤗112.5%

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 20 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 30 July 2026 to 14 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

14 Aug 2026, 05:32 UTC63 viewsread 14 August 2026
Photo

🎰 龙岗坂田贝贝半价福利 📮 参与条件: 🪪 必须设置用户名 🎫 加入-深圳茶友汇报告榜 🎫 加入-深圳茶友汇🅢 └ 🎟️ 发言数大于 18 条 🎫 加入-龙岗坂田19岁贝贝的小窝 🎫 加入-深圳茶友汇榜 🎁 奖品内容: 💰️ 半价p × 1 ⚠️ 抽奖说明: 1、开奖后5天内完成约课出击,退群、炸号、过期无效; 2、(半价卷)出击完后需要提交出击报告(奖励100积分) 3、优惠券不经同意不得私下转让或出售; 深圳茶友汇:https://t.me/SZXLX 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月17日 14时00分00秒

13 Aug 2026, 06:37 UTC242 viewsread 14 August 2026

#狼友投稿 @beibei687 #坂田 贝贝 闲来无事,看贝贝有空,果断出击 贝贝一如既往的顶级 有弹性的胸,光滑的皮肤,翘臀 口无齿感,水多紧致 然后还能愉快的聊天 By 肉蛋 葱鸡

12 Aug 2026, 08:09 UTC480 viewsread 14 August 2026

#狼友投稿 @beibei687 #坂田 贝贝 妹子年龄:19 人照: 9.5分 环境设备:10分 自由评论: 正在整理收藏夹的时候看到了队长的券,果断出击; 见到本人眼前一亮,果然是青春靓丽的的嫩妹,活力满满,身材高挑匀称,胸提拔又有弹性。 贝贝的身体超敏感,一经挑逗就浑身颤抖,陪洗的过程中就忍不住上下其手,充分感受了一下Q弹的身材。 来到床上,贝贝的口包裹感很强,温柔且细腻,下面也是一样的敏感,品尝了一下鲜嫩的鲍鱼,引的贝贝尖叫连连,可能是快来亲戚了,比平时更敏感了。 传教起手,感受青春肉体的美秒,随着老师逐渐进入状态,情不自禁的吻在了一起,最后在贝贝的高声呼喊中一泄如注。 抱在一起休息聊天的时候,贝贝给我看她的照片,一起点评哪些照片更符合她本人的形象,个人感觉本人更贴近甜妹风。 综合评价: 青春有活力,敏感且娇嫩,大吊们屌下留情。 By Rocky

7 Aug 2026, 03:26 UTC≈1,130 views3 reactionsread 14 August 2026

#狼友投稿 @beibei687 #坂田 贝贝 妹子年龄:19 人照: 9分 环境设备:10分,在云谷,隔层的loft腿酸的时候下楼小心 自由评论: 第一次来云谷,一开始在路边停车,但是离好远,后面就让贝贝等我往停车场那边开,最终在停车场也是绕了很久才找到。十分安全。 进门,身材真ok,高妹笑脸盈盈的,很热情,没有生疏感。 我是i人,聊了一会儿天,一起去洗澡,期间和贝贝聊了一下坂田各位大佬。 有个小插曲,只剩一条漱口水我用了一半,她用了一半,然后就上楼了。 没尝试吻,因为,刚下班过去,没有收拾自己比较邋遢。 贝贝,的口很温柔,没有任何齿感。 重点是一定得试试这个后入看着她的大屁股真的很爽。 过程就不赘述了,就是,嫩妹吧,服务少一点,需要,好好操盘,但是我不会。 综合评价: 老师这身材真的适合后入,随便抓腰抓手抓肩膀。 值得一提的是 临走前还主动给了我一个拥抱,抱着跟我身高一样的高妹,真的是美好的感觉。 希望下一次来这边能

3

Showing the 12 most recent of 20 posts we hold for @baibi66. 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

Citation-graph rank — 954,432 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.

Mentions

Named by 2 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.

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 August 2026 — this entry's latest reading, not the date you are reading this.

“龙岗坂田19岁贝贝的小窝” (@baibi66), 1,754 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/baibi66.

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.