Channel
@cdfhvfggvb
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
766subscribers
-315 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004484392147 |
|---|---|
| Type | Channel |
| Username | @cdfhvfggvb |
| Created | 30 August 2026 — measured — dated from the channel’s first post |
| First recorded | 1 September 2026 |
| Last confirmed live | 16 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 16 October 2026 |
| On Telegram | t.me/cdfhvfggvb |
Giveaways & airdrops — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 16 Oct 2026, 22:56 | 766 | -167 |
| 10 Oct 2026, 10:21 | 933 | -177 |
| 4 Oct 2026, 17:41 | 1,110 | -66 |
| 25 Sept 2026, 03:56 | 1,176 | -30 |
| 15 Sept 2026, 07:54 | 1,206 | +1 |
| 12 Sept 2026, 02:15 | 1,205 | -9 |
| 8 Sept 2026, 01:18 | 1,214 | +15 |
| 2 Sept 2026, 18:35 | 1,199 | +118 |
| 1 Sept 2026, 19:45 | 1,081 | first reading |
11 posts held, back to 30 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 1 September 2026. An engagement rate over an empty window would be a number about nothing.
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.
🎉 南山桃子半价优惠券 🎁 奖品清单 • P半价优惠券 × 1 • 刮刮乐10连抽 × 1 🛡️ 参与条件 • 加入 深圳嫩妹协会 • 加入 桃子小🏠 • 加入 嫩妹协会抽奖信息频道 • 加入 TG中文导航搜索 • 需消耗嫩妹币：20 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：66嫩妹币 • 祝福上限：100次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-09-05 18:37:00 📜 抽奖说明 禁止灌水，盖楼水群！！！ 中奖者24小时内联系老师预约时间 七天内出击，出击完成24小时出报告 超时不兑奖自动作废 炸号作废放回奖池重新抽奖 中奖需本人出击不得转让 中奖者必须设置用户名 中奖联系：@Tz060807 最终解释权归“深圳嫩妹协会” ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
🎉 南山桃子五折券抽奖 🎁 奖品清单 • p五折券 https://t.me/Sz2TB/7707 × 1 • 1000淘金币 × 1 🛡️ 参与条件 • 加入 深圳淘宝修车团 • 加入 桃子小🏠 • 加入 深圳淘宝修车团（备用） • 加入 深圳淘宝修车收集录 • 加入 深圳淘宝精选轮播 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10淘金币 • 祝福上限：100次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-09-04 21:30:00 📜 抽奖说明 中奖不可买卖，五折券有效期五天，过期回收群里积分兑换。 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
🎉 桃子老师半价劵福利 🎁 奖品清单 • 单P半价劵 × 1 🛡️ 参与条件 • 加入 深圳赏颜阁 • 加入 深圳赏颜阁（轮播） • 加入 深圳赏颜阁（备用） • 加入 深圳赏颜阁公开榜 • 加入 赏颜阁【甄选榜】 • 加入 桃子小🏠 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：50肾结石 • 祝福上限：100次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 开奖时间 • 2026-09-04 13:00:00 📜 抽奖说明 优惠卷有效期（7天） 半价卷有效期（5天） 白嫖卷有效期（3天） 禁止转让，私下交易买卖 发现永久取消中奖资格 中奖自行联系 @Tz060807 ✨ 愿好运伴随每一位参与者，祝大家好运！
桃子小🏠 pinned a video
Video, posted without a caption
桃子小🏠 pinned a photo
南山桃子165 🉑ks🉑浅蛇 年龄21岁 S型身材166 体重48kg 胸围34D肤白 特色；三点粉嫩 B紧 💦多 本人温柔🉑爱 比照片好看 服务类容：浅🐍k s吻、鸳鸯浴： 猫式吹萧 按摩 深喉口交、 💦中萧 无套口交 情趣制服诱惑、老汉推车、 观音座莲、舔咪咪、舔蛋蛋、 服务好，乖巧、配合 配合各种姿势激情爱爱六六 听从指挥配合度高 主打高情商、体验女友般情绪 巨会聊天不冷场 课费1课1200（45分中） 2课240…
桃子小🏠 pinned Deleted message
桃子小🏠 pinned Deleted message
Channel name was changed to «桃子小🏠»
Channel created
Showing the 11 most recent of 11 posts we hold for @cdfhvfggvb. 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.
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 16 October 2026 — this entry's latest reading, not the date you are reading this.
“桃子小🏠” (@cdfhvfggvb), 766 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/cdfhvfggvb.
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.