Channel
@taohuayuang_v2
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,036subscribers
+68 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001524754969 |
|---|---|
| Type | Channel |
| Username | @taohuayuang_v2 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/taohuayuang_v2 |
Ecommerce storefront — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 18 Sept 2026, 11:55 | 1,036 | +4 |
| 14 Sept 2026, 04:57 | 1,032 | +21 |
| 10 Sept 2026, 01:59 | 1,011 | +17 |
| 31 Aug 2026, 20:07 | 994 | +13 |
| 24 Aug 2026, 00:57 | 981 | +8 |
| 15 Aug 2026, 07:36 | 973 | +4 |
| 8 Aug 2026, 13:18 | 969 | +1 |
| 8 Aug 2026, 00:47 | 968 | no change |
| 7 Aug 2026, 17:53 | 968 | first reading |
18 posts held, back to 27 December 2025 — 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 18 posts for this entry, the most recent from 17 June 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.
36 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 63.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 63.9% | |
| 💩 | 7 | 19.4% | |
| 👍 | 4 | 11.1% | |
| 😁 | 1 | 2.78% | |
| 🤡 | 1 | 2.78% |
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 11 of the 18 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 27 December 2025 to 17 June 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.
🌸 桃花源 · 618活动 🌸 🎟 优惠券信息（用完不补） 🔹 七折券：桃花源77777（限20张） 🔸 八折券：桃花源88888（限50张） 📅 活动时间 🕛 2026/06/17 23:59 🕛 2026/06/20 23:59 ⚠️ 重要提醒 套餐不叠加！ 会覆盖原套餐 年付3.5元/300G便宜好用！ 📌 下单输入优惠码自动生效 🌐 官网：https://link.taohuayuan.xyz
❤6
更新hy2 暴力高速 轻点蹬
桃花源&无聊的维护日志 pinned «📢 桃花源免流入口更新公告 大家好，本公告整理了最新的桃花源免流入口信息，便于大家快速访问。 🌐 支持的域名泛解析列表 *.100010.site *.taohua.site *.taohua.eu.cc *.taohua.sbs *.91vip.fun 💡 使用方法 可以通过自定义域名前缀访问，例如：666.91vip.fun 单独入口设计减少被阻断风险 每个自定网站都有单独订阅链接 不再依赖梯子即可更新»
📢 桃花源免流入口更新公告 大家好，本公告整理了最新的桃花源免流入口信息，便于大家快速访问。 🌐 支持的域名泛解析列表 *.100010.site *.taohua.site *.taohua.eu.cc *.taohua.sbs *.91vip.fun 💡 使用方法 可以通过自定义域名前缀访问，例如：666.91vip.fun 单独入口设计减少被阻断风险 每个自定网站都有单独订阅链接 不再依赖梯子即可更新
❤4
六块钱的机场这速度和延时还可以吧🤣不比专线差还稳定 希望大家支持一下别让我倒闭了
桃花源&无聊的维护日志 pinned a photo
专线已经切换阿里云正价G口 倍率改为7，成本150/T 因为售价比较便宜专线为附加不赚钱！请勿刷流量 无视晚高峰三网速度拉满
❤2
🌸 桃花源机场 🌸 💡 6元 / 300G 起 稳定性自己体验，性价比拉满！ 🚀 核心优势 🔹 可长期使用，无需频繁更新订阅 🔹 IPv6 免维护、免墙设计 🔹 在线率高达 99%+（遭遇攻击等不可抗因素除外） 🔹 支持 免流 + 科学上网一体化 🔹 低价 / 高速 / 稳定，备用或主力都非常合适 🔹不虚量！不套路倍率清晰可见 🎁 邀请返利机制 邀请好友下单即可获得 循环返利 10%，长期有效 📢 价格说明 不限时已与市场同步上涨 👉 新用户建议先 月付体验 🌐 节点说明 国际节点均为 IPv6 专线 请自行开启 IPv6 环境后使用（自行搜索教程） ⚠️ 温馨提示 高峰期或遭受攻击可能存在波动 建议搭配备用线路使用，体验更佳 🌐 官网：https://link.taohuayuan.xyz 📊 探针：https://jk.taohuayuan.xyz 👥 群组：https://t.me/v2taohuayuang…
🌸 桃花源 · 新年优惠活动 🌸 🎟 优惠券信息（用完不补） 🔹 七折券：桃花源777（限30张） 🔸 八折券：桃花源888（限100张） 📦 新年福利 🎯taohuayuan 兑换10G流量 📅 活动时间 🕛 2026/02/14 12:00 🕛 2026/02/19 23:59 🚀 三网优化 · 海外优质线路 · 稳定高速 ⚠️ 重要提醒 本次为新年限时活动，结束后恢复原价 年后涨价，继续提高节点质量！ 📌 下单输入优惠码自动生效 🌐 官网：https://link.taohuayuan.xyz 📊 探针：https://jk.taohuayuan.xyz 👥 群组：https://t.me/v2taohuayuang
❤4
深电已更换IP 降低了延时 需要更新订阅获取一下🤪
📢 桃花源线路公告 🌸 桃花源目前已接入 ✅ 海外三网 ✅ 顶级优化线路 💰 仅需 6 元 / 300G 流量 ⚡ 稳定 · 低延迟 · 高性价比 🌐 官网入口： 👉 https://link.taohuayuan.xyz 欢迎体验，如有问题可随时反馈 🙌
深电G口专线已上线 禁止刷流量，联通移动都有顶级优化线路推荐电信使用嗷嗷起飞！刷流量封号
❤1
Showing the 12 most recent of 18 posts we hold for @taohuayuang_v2. 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 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“桃花源&无聊的维护日志” (@taohuayuang_v2), 1,036 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/taohuayuang_v2.
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.