5 Oct 2026, 11:01 UTC21 viewsread 5 October 2026
#泡芙 已在「老友会」验证上榜 👇👇👇👇👇👇👇👇 查看 距离 营业时间 : t.me/szxglyhOneBot?startapp=td_590796555 👆👆👆👆👆👆👆👆 打造纯净生态，不负信赖与热爱。 加群/频道: t.me/szxglyhOneBot?startapp=glist 加群机器人: @szxglyhglBot
Channel
泡泡芙原来的号上不去啦
@paofu678
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
42subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004415300458 |
|---|---|
| Type | Channel |
| Username | @paofu678 |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 October 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 1 |
| On Telegram | t.me/paofu678 |
Growth
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 14:22 | 42 | first reading |
Engagement
7 posts held, back to 29 September 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.
- ERR · 30 days
- 324.2%
- avg views ÷ 42 subscribers
- Avg views / post
- 136
- 6 posts measured
- Reaction rate
- 1.15%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 7 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 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 October 2026 |
|---|---|
| Posts held | 7 (29 September 2026 – 5 October 2026) |
| Views total | 817 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Oct 2026, 14:22 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
- Photos
- 13
- Videos
- 4
- Links
- 4
Lifetime counters from Telegram’s own channel header, read 5 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 18s
- Average length
- 9s
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.
Reaction mix
3 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 1 of the 7 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 29 September 2026 to 5 October 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
5 Oct 2026, 10:29 UTC34 viewsread 5 October 2026
集团每日五折工兵劵，更多现金大奖期待您的参与 深圳集团狼友交流群组：https://t.me/+T_cG2VyxBB8xYzU1 深圳集团老师公开榜： https://t.me/ShenZhen_68 深圳集团老师广告群： https://t.me/Shenzokba 深圳集团老师报告参考： https://t.me/yeshanghai96 ‼️📢投诉上榜建议： @bbca12
5 Oct 2026, 10:29 UTC34 viewsread 5 October 2026
https://t.me/ShenZhen_68/7131
29 Sept 2026, 09:02 UTC262 views3 reactionsread 5 October 2026
Forwarded from @SceneryOnTheRoad1Photo
泡芙 @paofu55 #T05 颜值S 身材A 态度A+ 整体感受S 是否返食：是，四天内2次PP ——————————————— 极品嫩妹、小只马。163左右，人照9成。5月的视频是最新的。没有蛇，但是口的很认真，会很努力的深。胸B左右，不大但抓上去有肉。很苗条，小屁股，细腰。没有多余的一丝赘肉，78斤。但是不会排骨精那种。身上皮肤无敌好，感觉掐一下出水的那种，亲上去跟亲小孩子皮肤一样。洞很小，很紧。缺点就是没有蛇，大蟒蛇的话，个人可以打到T0。 泡芙比较佛，又比较脆皮。来了深圳10天，除刚来两天接了两单上门外，真正意义上课室开课就一天。小懒猪一只，经常睡到下午，一天接不了几个，又是小脆皮，望大家温柔对待。明天课室开 【关于过程】 碰巧看到泡芙的讯息，发现是去关注但一直没机会去的一个大圈妹子。几经核对基本能确认是本人。相约第二天见面，谁料第二天妹子一觉睡到晚上。由于刚来深圳还没有课室，要上门，五一酒店是真贵。附近好…
❤3
29 Sept 2026, 09:00 UTCviews —
泡泡芙原来的号上不去啦 pinned «泡芙-课表，湖南人 预约私聊我 @paofu86 频道: https://t.me/paofu678 泡芙 06 165cm 胸B 体重42kg （谢绝嘴炮）见面先付课费 不上门不是中介 本人回复 1400p（60分钟） 2800pp(120分钟) 课表:鸳鸯🛀，🐻推，无套吹，调情，爱爱 温馨提示: 素质约课口嗨勿扰，最好现金，感谢理解 没回复就是不在线 上线会回 🈲:大的 WT 不接偷拍 喝酒 🈲:磕药喷雾不接 🈲:桩机 尺大 持久不接 超过15分钟手打出来，大的别找我了，求求了，很脆皮 双向机器人:…»
29 Sept 2026, 09:00 UTC251 viewsread 5 October 2026
泡芙-课表，湖南人 预约私聊我 @paofu86 频道: https://t.me/paofu678 泡芙 06 165cm 胸B 体重42kg （谢绝嘴炮）见面先付课费 不上门不是中介 本人回复 1400p（60分钟） 2800pp(120分钟) 课表:鸳鸯🛀，🐻推，无套吹，调情，爱爱 温馨提示: 素质约课口嗨勿扰，最好现金，感谢理解 没回复就是不在线 上线会回 🈲:大的 WT 不接偷拍 喝酒 🈲:磕药喷雾不接 🈲:桩机 尺大 持久不接 超过15分钟手打出来，大的别找我了，求求了，很脆皮 双向机器人: https://t.me/paofufutbot
29 Sept 2026, 08:59 UTC215 viewsread 5 October 2026
Photo
Photo, posted without a caption
Showing the 7 most recent of 7 posts we hold for @paofu678. 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.
Forward network
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.
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.
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.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“泡泡芙原来的号上不去啦” (@paofu678), 42 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/paofu678.
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.