Telegram RegisterThe public register of Telegram

Channel

宝安 小泡芙

@xiaopaofu31

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

173subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003776999513
TypeChannel
Username@xiaopaofu31
Description联系方式 @xiaofu36 机器人 @xiaofu339_bot
CreatedBetween 1 February 2026 and 12 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
On Telegramt.me/xiaopaofu31

Growth

173174173.57 Aug 2026, 13:39 — 174 subscribers7 Aug 2026, 14:23 — 173 subscribers8 Aug 2026, 14:31 — 173 subscribers7 Aug 2026, 13:398 Aug 2026, 14:31
3 measurements spanning 1 day, net -1. 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 173–174 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 14:31173no change
7 Aug 2026, 14:23173-1
7 Aug 2026, 13:39174first reading

Engagement

16 posts held, back to 12 June 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
94.3%
avg views ÷ 173 subscribers
Avg views / post
163
7 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
7
of 16 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 7 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 8 August 2026
Posts held16 (12 June 20268 August 2026)
Views total1,142
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 14: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.

What this channel posts

Photos
26
Videos
3
Links
15

Lifetime counters from Telegram’s own channel header, read 8 August 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
6s
Average length
3s

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 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.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 6 of the 16 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 12 June 2026 to 8 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

8 Aug 2026, 06:32 UTC96 viewsread 8 August 2026

派大星出击报告( https://t.me/+2Kbp7dDZd904ZDBk ) 验证留名:嗯哈哈 验证时间:8-7 老师花名:#小泡芙 城市坐标:#深圳 #宝安 上课花费:800p 颜值身材:颜值属耐看型,身材曼妙无比 服务内容:舌吻,69,陪洗 出击体验:首先就是人照一致,小泡芙长得很好看,颜值在线身材没有问题,🐻摸起来也很舒服。从服务上来讲,服务意识很到位,课表该有的全都有,像是69,🐍啥的,老师都能满足,过程反馈也很顶,在进行的过程中老师的表情真的很让人喜欢,老师下面很紧致,整个过程很投入,服务意识真的很好。老师很值得约,颜值耐看,服务意识到位,很听话啊 优点缺点:口活超级好,配合度很高 推荐程度:10/满分10.0分;(综合硬件(脸,熊,身材)和软件(服务,态度)等方面打分。自己更看重哪方面,给出打出这个分数的理由) 联系方式: @xiaofu36 已验证资源频道(备用防失联): 1、https://t.me/+a

8 Aug 2026, 05:24 UTC124 viewsread 8 August 2026

🎟️ 抽奖标题:宝安小泡芙 @xiaofu36 红包加优惠卷抽奖 📪抽奖说明:中奖者机器人会发送中奖信息 联系老师领取 写报告反馈 炸号炸频道抽奖作废 🎫 参与条件: 🎫 加入-宝安 小泡芙 🎫 加入-派大星抽奖优惠活动频道 🎫 加入-派大星备用群3(防失联) 🎁 奖品内容: 💰️ 18.8红包 × 2 💰️ pp200优惠卷 × 3 💰️ p100优惠卷 × 3 📅 开奖时间:2026-08-11 13:00自动开奖 👉 参与抽奖链接: https://t.me/xielaoban1bot?start=join-L178616571733

7 Aug 2026, 06:33 UTC226 viewsread 8 August 2026
Photo

🎰 宝安小泡芙 @xiaofu36 长腿嫩妹 半价 📮 参与条件: 🎫 加入-宝安 小泡芙 🎫 加入-深圳野狼老师轮播 🎫 加入-野狼抽奖活动 🎫 加入-深圳野狼修车公开榜 🎫 加入-深圳野狼修车交流群 └ 🎟️ 发言数大于 30 条 🎁 奖品内容: 💰️ 1P半价 × 1 ⚠️ 抽奖说明: 1、开奖后 3 天内约课使用,老师大姨妈顺延; 2、需要提交报告,优惠券不得私下转让或出售; 3、上课时间需要和老师私聊提前约好; 4、抽奖留给有需要的人,不遵循规则将永久拉黑。 🔋 人品加成:⚡️× 5 规则 📅 开奖日期:(北京时间) 2026年08月10日 12时30分00秒

7 Aug 2026, 06:30 UTC152 views0 reactionsread 8 August 2026
Forwarded from @SZLXFPhoto

长腿嫩妹 花名: #小泡芙 位置: 深圳 #宝安 年龄: 20 胸围: 36B 身高: 170 体重: 50kg 课费: 800P 1500PP #八百 特色: #大长腿 #嫩妹 #女友感 #甜美 #大学生 #肤白 服务: #鸳鸯浴 #无套口 #舌吻 #六九 #丝袜制服 #臀推 私聊: @xiaofu36 双向: @xiaofu339_bot 频道: @xiaopaofu31 📤 提交报告 | 📋 查看报告(0)

6 Aug 2026, 12:22 UTC199 viewsread 8 August 2026

派大星出击报告( https://t.me/+2Kbp7dDZd904ZDBk ) 验证留名:Kan hour 验证时间:8-6 老师花名:#小泡芙 城市坐标:#深圳 #宝安 上课花费:800p-1券 颜值身材:颜值非常高,身材高挑少御风,是我喜欢的类型 服务内容:无套口,🐍,69都有 出击体验:进门是位一米7左右的妹妹,很嫩,很开朗,身材挺好的,瘦瘦的,洗完澡开始服务69和🐍都有,挺舒服的,刚进去妹妹反应就挺好大的,叫声很好听,下面毛少少的也紧紧的很舒服。服务态度很好,要求都也会满足,十分推荐。 优点缺点:细节认真,用心到位 推荐程度:10/满分10.0分;(综合硬件(脸,熊,身材)和软件(服务,态度)等方面打分。自己更看重哪方面,给出打出这个分数的理由) 联系方式: @xiaofu36 已验证资源频道(备用防失联): 1、https://t.me/+aajVEQ4g6yllZmJk 2、https://t.me/+uNpU

20 Jun 2026, 06:29 UTC651 views1 reactionsread 8 August 2026

派大星出击报告( https://t.me/+2Kbp7dDZd904ZDBk ) 验证留名:杜仲 验证时间:2026.6.19 老师花名:#小泡芙 城市坐标:#深圳 #宝安 上课花费:800p 颜值身材:年轻漂亮,身材不错,身材苗条,屁股翘翘 服务内容:xcz🐍69 出击体验:进门迎面而来的一对奶子,顺手捏了一下,手感不错,梦瑶老师样子与照片有9成,果断交了水费,进到浴室,洗弟弟的时候特别温柔,出来擦干之后,抱着老师🐍了一会,开始服务,口活舒服,深喉特别爽,口了一会来感觉了,就让老师戴上,老师说她会女上,我说那你先来,结果刚进去,感觉到紧,小穴真敏感,水越来越多,后面换成传统传教士,握住那一对雪白的奶子,开始冲刺,突然老师双腿一夹,双手用力抓着我,时不时夹我弟弟,真是骚货。最后换后入,疯狂输出,123出货,事后还有回笼萧,这服务真是太棒了。满意而归! 优点缺点:很棒,会配合听话 推荐程度:9.5分 联系方式: @xiaofu

1

19 Jun 2026, 09:25 UTC612 views1 reactionsread 8 August 2026

派大星出击报告( https://t.me/+2Kbp7dDZd904ZDBk ) 验证留名:出击少女协会主任 验证时间:6.19 老师花名:#小泡芙 城市坐标:#深圳 #宝安 上课花费:800p 颜值身材:人照9 分,颜值和身材都很好 服务内容:课表 出击体验:约了妹妹,准时到达位置,到了没罚站,进了门看见妹妹跟照片没什么差别就值得了,交了水费就一起洗澡了,妹妹很热情聊天也很好,很喜欢笑,洗完澡就上床开始口,妹妹刚做,口的还不错,口的时间很久,口完就开干了,女上起手,略有生疏,妹妹下面很紧真的紧,🐍到保,舌头好软,换了几个姿势,夹的我受不了!,一般我都要二十几分钟,十几分钟就缴枪了.太舒服了,完事也没有催,一直聊天,真不错, 优点缺点:懂事,听话,配合度高 推荐程度:9.5分 联系方式: @xiaofu36 已验证资源频道(备用防失联): 1、https://t.me/+aajVEQ4g6yllZmJk 2、https:/

1

Showing the 12 most recent of 16 posts we hold for @xiaopaofu31. 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 — 233,683 of 1,169,250entries 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.

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 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.

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

“宝安 小泡芙” (@xiaopaofu31), 173 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/xiaopaofu31.

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.