因为前几天生理期 这两天在深圳包天 没有怎么登陆上线哈 好多信息没看见或者漏回的信息GG们多发几遍 看见后我会第一时间回复的↩️ 爱你们❤️❤️❤️@Lulubaby520520
Signed 深圳开.深圳南山🌹白露baby

Channel
@Lulubaby520888
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,936subscribers
-2,125 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002484530741 |
|---|---|
| Type | Channel |
| Username | @Lulubaby520888 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Lulubaby520888 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 17 Sept 2026, 16:59 | 6,936 | -83 |
| 13 Sept 2026, 20:20 | 7,019 | -45 |
| 10 Sept 2026, 08:37 | 7,064 | -220 |
| 4 Sept 2026, 18:02 | 7,284 | -65 |
| 1 Sept 2026, 06:29 | 7,349 | -54 |
| 29 Aug 2026, 04:35 | 7,403 | -77 |
| 26 Aug 2026, 06:54 | 7,480 | -59 |
| 23 Aug 2026, 10:28 | 7,539 | -931 |
| 19 Aug 2026, 12:37 | 8,470 | -103 |
| 16 Aug 2026, 07:59 | 8,573 | -67 |
| 12 Aug 2026, 10:47 | 8,640 | -421 |
| 12 Aug 2026, 00:45 | 9,061 | first reading |
19 posts held, back to 4 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 11 pages of 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 28 August 2026 |
|---|---|
| Posts held | 19 (4 August 2026 – 28 August 2026) |
| Views total | 610 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 22:30 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.
Measured directly from 2 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.
14 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 85.7% | |
| 👍 | 2 | 14.3% |
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 9 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 14 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 4 August 2026 to 28 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.
因为前几天生理期 这两天在深圳包天 没有怎么登陆上线哈 好多信息没看见或者漏回的信息GG们多发几遍 看见后我会第一时间回复的↩️ 爱你们❤️❤️❤️@Lulubaby520520
Signed 深圳开.深圳南山🌹白露baby
生理期提前啦~红休💄过几天见BB们💕💕
Signed 深圳开.深圳南山🌹白露baby
深圳8.27号1W包天已被熟课gg定金预定🌆🌃#汕尾GG和我的第12次约会🎧🎧🐈🤩🌙🌙🤩@Lulubaby520520
❤2
Signed 深圳开.深圳南山🌹白露baby
好久不见 爸爸们💕💕我这周深圳🈶熟课GG要包天 人还在深圳呢 好多上海的爸爸们在问露宝baby好久回上海开课 上次呆的时间太短了 今天终于确定了9.4号晚上到上海🌃 5号上海开课🉑约 上海的爸爸们可私信我提前定金约起来啦~ 定金约课:@Lulubaby520520 双向限制:@Lulubaby520bot
Signed 深圳开.深圳南山🌹白露baby
11枝红玫瑰🌹+深紫色勿忘我的花语💐🎀🎀 我懂😉❤️🤍
Signed 深圳开.深圳南山🌹白露baby
谢谢今天七夕节🤩一大早 就收到不知名BB让外卖员送到我深圳家门口的七夕节鲜花🌹💐🤩love you ♥️💌🤩 如果我没猜错 现在我大概知道是哪位爸爸送我的FaFa啦🎧🎧🎧@Lulubaby520520
❤2
Signed 深圳开.深圳南山🌹白露baby
🥐艺名: 白露 🤗年龄: 23身高 : 167体重 :48 熊:C 📍位置: 浦东 💸价格: 1300p/45min 2200pp/70min 👩🎓标签:舌吻#口#69#深喉#制服丝袜诱惑 🥂联系老师: @Lulubaby520520 💓老师频道: https://t.me/Lulubaby520888 韩信上海备用榜:https://t.me/shhxyxb 韩信上海优选榜:@hxshyx 韩信上海精选榜:@hxshjxb 上海外围大⭕️:@ccxkshww
👍1
Signed 深圳开.深圳南山🌹白露baby
🈵️🈵️🈵️
Signed 深圳开.深圳南山🌹白露baby
感冒休息一天 最早预约周五的课
Signed 深圳开.深圳南山🌹白露baby
群有按地区 按分类搜索 ,每月都有水群榜单内任选抵扣抽奖 进群抽奖 老师榜单 https://t.me/szlistpeach 工兵榜单 https://t.me/szpeachb 桃花坞导航中转 telegram.me/szpeachblossom
👍1
Signed 深圳开.深圳南山🌹白露baby
回深圳第一天上课就是吃喝玩乐🎡🎢🎠 今天早夜课🈵 一会儿和GG去看期待已久的电影🎥🎞【八仙!】暑期档最高分10分🧏♀ 期待 期待ing 吼吼😮💨😮💨😮💨@Lulubaby520520
Signed 深圳开.深圳南山🌹白露baby
生理期休假中ing♨️10号深圳见🎫@Lulubaby520520
Signed 深圳🌹白露baby.红休中
Showing the 12 most recent of 19 posts we hold for @Lulubaby520888. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 3 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“主频道.白露baby🌹反差淫SM剧本🉑69🉑🐍🉑3P” (@Lulubaby520888), 6,936 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Lulubaby520888.
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.