🎉 联邦~禅城胡桃💃🏻福利抽奖🎰 🎁 奖品清单 • p半价 × 1 • 100优惠券 × 3 📢 参与条件 • 加入 广州佛山联邦出击群(重生版) • 加入 胡桃桃桃桃 • 加入 广州佛山邦女郎动态榜 • 加入 广州佛山联邦老师榜 • 加入 广州佛山商家榜 • 加入 广州佛山联邦抽奖榜 • 参加抽奖后需在 广州佛山联邦出击群(重生版) 内发言3次 └ 群内发送“抽奖进度”查看完成度(每日限5次) ⌛ 开奖时间 • 2026-11-03 18:30:00 📜 抽奖说明 胡桃: t.me/Gzffol/52066 1.本活动由胡桃赞助,私聊 @hutao2388 兑奖。 2.开奖后请老师七天内兑券,转让需老师同意。 3.中半价券先拉黑抽奖60天,出击交报告即解。 ✨ 愿好运常伴大家,祝大家好运!点击下方按钮参与抽奖。

Channel
胡桃桃桃桃
@hutao128
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
259subscribers
+189 since we began measuring on 1 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004318659798 |
|---|---|
| Type | Channel |
| Username | @hutao128 |
| Created | 21 October 2026 — measured — dated from the channel’s first post |
| First recorded | 1 November 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/hutao128 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 09:05 | 259 | -20 |
| 1 Nov 2026, 21:44 | 279 | +209 |
| 1 Nov 2026, 12:22 | 70 | first reading |
Engagement
17 posts held, back to 21 October 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
- 87.9%
- avg views ÷ 259 subscribers
- Avg views / post
- 228
- 14 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 17
- of 17 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.
| Window | Rolling 30 days · latest post in window 1 November 2026 |
|---|---|
| Posts held | 17 (21 October 2026 – 1 November 2026) |
| Views total | 3,187 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Nov 2026, 12: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
- Video runtime
- 5s
- Average length
- 5s
Measured directly from 1 video 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 17 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
今天还有空
今天下午一点禅城开
https://t.me/Gzffrr/17289 @hutao2388
今天还有🈳
下午一点开头课还在哦
#联邦报告 <https://telegram.me/gzafua> 【出击留名】: 不留名 【出击时间】:2026年10月下旬 【老师艺名】:#胡桃 【联系方式】:@hutao2388 【开课位置】:#禅城 【上课费用】:P 【颜值身材】:颜值如图接近10成,皮肤没有图片白,小麦色有光泽。给我感觉是像“杨超越”,白月光和小红书级别。 【身高体重】:目测164/46kg 【胸杯紧度】: B+ 左右 紧度可以,湿滑通道 【老师类型】:#嫩妹 【服务种类】:自己看课表 【情绪态度】:微笑、礼貌、大方、甜美 【优点缺点】:必填 ①缺点: 有一丢丢纹身。 ②优点:满足你白月光的所有需求,一个主动耐心的白月光。差点沉了。 【自由描述】: 某日下午刷到胡桃复出马上约课,老师很早就上班,劳模。开车来到课室,位置比较方便好停车,留好门进到课室,环境不错(又大格调好,卫生整洁,备品齐全,老师自带漱口水非常注重品质细节)开门胡桃穿个公主小裙子,长相…
今天还有位置
#联邦报告 <https://telegram.me/gzafua> 【出击留名】:匿名 【出击时间】:2026.10.23 【老师艺名】:#胡桃 【联系方式】:@hutao2388 【开课位置】:#禅城 【上课费用】:1400pp+800P 【颜值身材】: 人照10 【身高体重】:165 45kg 【胸杯紧度】:Bcup 【老师类型】:#嫩妹 #小只马 【服务种类】:课表齐全 【情绪态度】:热情 【优点缺点】: ①缺点: 暂时没发现 ②优点:不冷场好聊 嫩妹课表内容齐全 人照一致 【自由描述】: 去年找了胡桃好多次,本以为今年过年回去不来了,想不到她又回归了,看她上线立马联系她pp。胡桃妹妹情绪价值充足口技不错,比例好。 楼下好停车,不用交停车费。遥控上门,胡桃老师先帮忙仔细洗洗身子,她本人还是和频道照片一模一样的模样,比之前短发时候更漂亮了。 浴室位置还是很大的,洗澡也舒服,还有胡桃老师帮忙 前后搓洗。 洗完之后老师也没有…
现在有🈳
今天满啦 明天下午一点禅城开
胡桃桃桃桃 pinned «https://t.me/Gzffol/52066»
Showing the 12 most recent of 17 posts we hold for @hutao128. 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 1 registered channel — 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“胡桃桃桃桃” (@hutao128), 259 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/hutao128.
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.