粉脑浆DesireChurc7 – [自购整合] [588门槛] 含新1.57小时 金主啪啪 顶级白虎萝莉福利订阅 🦇点击此处蓝色字体查看完整版
❤10👍3
Channel
@luolifang
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
32,097subscribers
-55 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001198608941 |
|---|---|
| Type | Channel |
| Username | @luolifang |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/luolifang |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 10 Sept 2026, 13:39 | 32,097 | -65 |
| 7 Sept 2026, 11:41 | 32,162 | -53 |
| 4 Sept 2026, 18:15 | 32,215 | -39 |
| 3 Sept 2026, 05:54 | 32,254 | -25 |
| 2 Sept 2026, 00:29 | 32,279 | -15 |
| 1 Sept 2026, 03:07 | 32,294 | -9 |
| 31 Aug 2026, 04:12 | 32,303 | -10 |
| 30 Aug 2026, 06:24 | 32,313 | -4 |
| 29 Aug 2026, 04:03 | 32,317 | +14 |
| 28 Aug 2026, 03:43 | 32,303 | +1 |
| 27 Aug 2026, 01:43 | 32,302 | +2 |
| 26 Aug 2026, 00:03 | 32,300 | +7 |
| 24 Aug 2026, 23:16 | 32,293 | +14 |
| 23 Aug 2026, 09:42 | 32,279 | +19 |
| 21 Aug 2026, 22:25 | 32,260 | +7 |
| 20 Aug 2026, 17:37 | 32,253 | +12 |
| 19 Aug 2026, 21:02 | 32,241 | +5 |
| 18 Aug 2026, 23:51 | 32,236 | +10 |
| 17 Aug 2026, 23:59 | 32,226 | -8 |
| 16 Aug 2026, 20:55 | 32,234 | first reading |
18 posts held, back to 23 July 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 62 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 27 August 2026 |
|---|---|
| Posts held | 18 (23 July 2026 – 27 August 2026) |
| Views total | 56,590 |
| Reactions total | 46 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Sept 2026, 13:31 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 6 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.
133 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 89.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 119 | 89.5% | |
| 👍 | 10 | 7.52% | |
| 🤔 | 2 | 1.50% | |
| 🔥 | 1 | 0.752% | |
| 😍 | 1 | 0.752% |
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 18 of the 18 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 133 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 23 July 2026 to 27 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.
粉脑浆DesireChurc7 – [自购整合] [588门槛] 含新1.57小时 金主啪啪 顶级白虎萝莉福利订阅 🦇点击此处蓝色字体查看完整版
❤10👍3
乖犬(一枚呆呆)@Daibao1103 – [520门槛] [截至7.10号整合] 2.10小时 Cos白虎萝莉 🦇点击此处蓝色字体查看完整版
❤6👍5
一颗好困芽ykhaokunya – [520门槛] [含新整合] 补增 1.15小时 白虎萝莉合集 [36P6V-4.16G] 🦇点击此处蓝色字体查看完整版
❤7
FFhblue 799门槛[含新2更] 1.15小时 露脸白虎眼睛妹 极品萝莉订阅 [15PnV-4.54G] 🦇点击此处蓝色字体查看完整版
❤3
豆喵doufumiaomiao – 新作 [520门槛] 3套 31分钟 [Cos猫娘黄豆粉+王者大耳狗+西施诗雨] [68P3V-1.98G] 🦇点击此处蓝色字体查看完整版
❤5😍1
咬一口兔娘(咬兔)yaotu77 – 新作 [520门槛] [5套合集] 新增2套 29分钟 双马尾白虎萝莉福利合集 [9V-1.90G] 🦇点击此处蓝色字体查看完整版
❤5🔥1
铃木奈雪(江东萌虎)Alano77lover – 新作 [520门槛] 17分钟 洛丽塔户外车库啪啪 顶级白虎萝莉订阅 [3V-0.99G] 🦇点击此处蓝色字体查看完整版
❤19
小鸢宝宝babyLzyyy – 新作 [520门槛] 13分钟 lo裙白丝自慰 [1V-796MB] 🦇点击此处蓝色字体查看完整版
❤3👍2
推特最新反差萝莉合集,极品反差 coser 下海自慰,粉嫩白虎萝莉小学掰开后狠狠自慰给金主看 🦇点击此处蓝色字体查看完整版
❤6
明の神 – [福利订阅] 22分钟 Cos童颜巨乳裸舞自慰啪啪 🦇点击此处蓝色字体查看完整版
❤7
沅沅@Himikaowo – [520门槛] [含新增] 13分钟 [露酱奶瓶魅魔+猫耳情趣制服] [2P2V-802MB] 🦇点击此处蓝色字体查看完整版
❤5
反差福利姬小苏喵(苏别喵)xiaosumiaomiao – [520门槛] [稀缺] 12分钟Cos顶级白虎萝莉自慰福利订阅[207P2V-742MB] 此处蓝色字体查看完整版
❤4
Showing the 12 most recent of 18 posts we hold for @luolifang. 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.
@luolifang named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“推特反差母狗学生萝莉” (@luolifang), 32,097 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/luolifang.
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.