Telegram RegisterThe public register of Telegram
Telegram profile photo for 桃子花园

Channel

桃子花园

@taozi923226

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

3,263subscribers

+631 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003746718659
TypeChannel
Username@taozi923226
CreatedBetween 1 February 2026 and 18 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held17
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/taozi923226

Topic

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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.

Growth

2,63212,0617,346.57 August 2026 — 2,632 subscribers7 August 2026 — 2,632 subscribers7 August 2026 — 2,638 subscribers10 August 2026 — 2,671 subscribers13 August 2026 — 2,711 subscribers16 August 2026 — 2,731 subscribers19 August 2026 — 11,001 subscribers20 August 2026 — 12,060 subscribers21 August 2026 — 12,061 subscribers22 August 2026 — 11,341 subscribers24 August 2026 — 5,753 subscribers28 August 2026 — 4,678 subscribers31 August 2026 — 3,691 subscribers3 September 2026 — 3,316 subscribers9 September 2026 — 3,256 subscribers12 September 2026 — 3,266 subscribers17 September 2026 — 3,263 subscribers3,2637 August 202617 September 2026
17 measurements spanning 41 days, net +631. 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 1,218–13,475 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 03:193,263-3
12 Sept 2026, 18:193,266+10
9 Sept 2026, 00:013,256-60
3 Sept 2026, 12:393,316-375
31 Aug 2026, 09:433,691-987
28 Aug 2026, 01:134,678-1,075
24 Aug 2026, 16:275,753-5,588
22 Aug 2026, 21:4411,341-720
21 Aug 2026, 11:1612,061+1
20 Aug 2026, 07:3812,060+1,059
19 Aug 2026, 07:3611,001+8,270
16 Aug 2026, 18:222,731+20
13 Aug 2026, 13:382,711+40
10 Aug 2026, 14:412,671+33
7 Aug 2026, 23:482,638+6
7 Aug 2026, 13:332,632no change
7 Aug 2026, 13:012,632first reading

Engagement

37 posts held, back to 18 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages 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 37 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
17s
Average length
6s

Measured directly from 3 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

56 reactions across 24 posts, in 2 distinct kinds. The most used accounts for 98.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5598.2%
🤬11.79%

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 26 of the 37 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 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 37 most recent posts we hold, published 18 July 2026 to 24 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

23 Aug 2026, 16:00 UTC124 viewsread 23 August 2026

抽奖坂田桃子老师优惠券抽奖(编号L178731714839)已成功开奖: 创建人:诚心[8082834232] 已参与人数:75 中奖名单如下: NPC[6121744597](奖品为16.88口令🧧) 人柱力[6644115706](奖品为100pp优惠券) 國王與騎士[7346384132](奖品为16.88口令🧧) 万物生[7829100411](奖品为100pp优惠券) 無為[7840054696](奖品为100pp优惠券) 勿忘我[8002435391](奖品为16.88口令🧧) 烽火與諸侯[8626173416](奖品为100pp优惠券) 千纸鹤[8795959496](奖品为100pp优惠券)

22 Aug 2026, 08:12 UTC869 views1 reactionsread 23 August 2026
Photo

再次声明一下 第一次过来约课的宝子需要一张定约课,麻烦以后不要问不给定行不行。 谢谢

1

21 Aug 2026, 18:37 UTC≈1,120 viewsread 24 August 2026
Photo

🎉 坂田桃子优惠卷活动 🎁 奖品清单 • pp优惠卷100 × 5 • 口令红包🧧16.8 × 3 🛡️ 参与条件 • 加入 深圳欢乐谷 • 加入 桃子花园 • 加入 欢乐谷活动频道 • 参加抽奖后需在 深圳欢乐谷 内发言9次 └ 群内发送“抽奖进度”查看完成度(每日限5次) • 必须设置用户名 ⌛ 抽选时刻 • 2026-08-25 14:30:00 📜 抽奖说明 中奖24小时内预约,5天内使用 需写报告,过时自动作废 炸号无效作废,放回群内奖池 中奖优惠卷不得转让 活动最终解释权:深圳欢乐谷 兑奖联系:@taozi85201 ✨ 愿命运之剑指引你们前行,直至胜利之光照耀每一个人。

21 Aug 2026, 13:05 UTC891 viewsread 23 August 2026
Photo

🎁更多抽奖 https://t.me/xiu8che 🎟️ 抽奖标题:坂田桃子老师优惠券抽奖 📪抽奖说明:中奖者机器人会发送中奖信息 中奖联系: 🎫 参与条件: 🎫 加入-桃子花园 🎫 加入-深圳汤臣一品-约课认准轮播 🎁 奖品内容: 💰️ 16.88口令🧧 × 3 💰️ 100pp优惠券 × 5 📅 开奖时间:2026-08-24 00:00自动开奖 👉 参与抽奖链接: 深圳汤臣一品-约课认准轮播 🔑抽奖口令: 我爱桃子 (👈点一下可复制)

21 Aug 2026, 12:06 UTC764 viewsread 24 August 2026
Photo

🎰 坂田桃子 @taozi85201 半价优惠券 📮 参与条件: 🌏️ 归属地 广东 🪪 必须设置用户名 🎫 加入-桃子花园 🎫 加入-深圳出击俱乐部认证榜 🎫 加入-深圳出击俱乐部 └ 🎟️ 发言数大于 40 条 🎁 奖品内容: 💰️ 坂田桃子 @taozi85201 半价限P × 1 ⚠️ 抽奖说明: ‼️中奖者私聊老师兑换 ‼️需要24小时内确认中奖 ‼️开奖三天内兑奖 ‼️过期无效 ‼️无效回收积分兑换 ‼️兑奖需要提交报告 ‼️炸号者中奖作废(中奖前后) ‼️转让需要老师同意 ‼️中奖不去私聊 @Fire5inhole 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月24日 14时30分00秒

21 Aug 2026, 11:31 UTC723 viewsread 24 August 2026
Photo

🎰 坂田桃子 @taozi85201 口令红包和优惠券 📮 参与条件: 🌏️ 归属地 广东 🪪 必须设置用户名 🎫 加入-深圳·乱世俏佳人(备用群) 🎫 加入-桃子花园 🎫 加入-深圳·乱世俏佳人 └ 🔑 发送口令﹝我爱桃子﹞ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 坂田桃子 @taozi85201 PP-100优惠券 × 5 💰️ 坂田桃子 @taozi85201 口令红包16.88 × 3 ⚠️ 抽奖说明: 1:中奖者24小时内私聊老师兑奖; 2:开奖3天内没有兑奖的,则过期无效; 3:兑奖需要出击完提交详细报告:@Szqiaojiarenbg_bot 4:不去私聊管理 @bingmeishijiabing 回收 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月24日 15时28分00秒

21 Aug 2026, 11:27 UTC752 views1 reactionsread 24 August 2026
Photo

🎰 深圳坂田桃子福利优惠卷 📮 参与条件: 🎫 加入-桃子花园 🎫 加入-深圳快乐屋(约课认准轮播和榜单) └ 🔑 发送口令﹝我爱桃子﹞ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ pp100优惠卷 × 5 💰️ 红包16.88 × 3 ⚠️ 抽奖说明: 红包24小时内领取、过期不候 使用优惠卷需要提供出击报告 📅 开奖日期:(北京时间) 2026年08月24日 19时21分00秒

1

Showing the 12 most recent of 37 posts we hold for @taozi923226. 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.

Posts edited after publishing

@taozi923226 edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
19 August 2026
Most recent edit
21 August 2026

Mentions

Named by 15 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“桃子花园” (@taozi923226), 3,263 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/taozi923226.

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.