Telegram RegisterThe public register of Telegram
Telegram profile photo for Yue.to | 悦通

Channel

Yue.to | 悦通

@yueto_news

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

6,771subscribers

+1,584 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002668606834
TypeChannel
Username@yueto_news
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/yueto_news

Topic

Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 the other topics.

Growth

5,1876,7715,9796 August 2026 — 5,187 subscribers6 August 2026 — 5,205 subscribers9 August 2026 — 5,259 subscribers12 August 2026 — 5,279 subscribers15 August 2026 — 5,397 subscribers18 August 2026 — 5,488 subscribers21 August 2026 — 5,593 subscribers24 August 2026 — 5,726 subscribers28 August 2026 — 5,837 subscribers31 August 2026 — 5,888 subscribers3 September 2026 — 6,122 subscribers8 September 2026 — 6,152 subscribers12 September 2026 — 6,162 subscribers16 September 2026 — 6,181 subscribers1 October 2026 — 6,372 subscribers8 October 2026 — 6,416 subscribers13 October 2026 — 6,471 subscribers16 October 2026 — 6,485 subscribers19 October 2026 — 6,528 subscribers22 October 2026 — 6,572 subscribers24 October 2026 — 6,600 subscribers27 October 2026 — 6,646 subscribers31 October 2026 — 6,684 subscribers2 November 2026 — 6,719 subscribers6 November 2026 — 6,734 subscribers9 November 2026 — 6,744 subscribers13 November 2026 — 6,771 subscribers6 August 202613 November 2026
27 measurements spanning 100 days, net +1,584. 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 4,949–7,009 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
13 Nov 2026, 23:466,771+27
9 Nov 2026, 01:046,744+10
6 Nov 2026, 00:056,734+15
2 Nov 2026, 20:176,719+35
31 Oct 2026, 00:406,684+38
27 Oct 2026, 22:076,646+46
24 Oct 2026, 22:096,600+28
22 Oct 2026, 08:056,572+44
19 Oct 2026, 05:276,528+43
16 Oct 2026, 14:066,485+14
13 Oct 2026, 17:026,471+55
8 Oct 2026, 07:366,416+44
1 Oct 2026, 16:386,372+191
16 Sept 2026, 18:396,181+19
12 Sept 2026, 14:376,162+10
8 Sept 2026, 20:396,152+30
3 Sept 2026, 22:206,122+234
31 Aug 2026, 06:555,888+51
28 Aug 2026, 07:455,837+111
24 Aug 2026, 21:275,726first reading

Engagement

28 posts held, back to 6 February 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 22 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
34.1%
avg views ÷ 6,771 subscribers
Avg views / post
2,310
4 posts measured
Reaction rate
0.227%
reactions ÷ views · ER floor
Posts in window
4
of 28 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held28 (6 February 2026 – 16 November 2026)
Views total9,238
Reactions total21
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 14:44 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

Links
34

Lifetime counters from Telegram’s own channel header, read 16 November 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.

Reaction mix

237 reactions across 28 posts, in 4 distinct kinds. The most used accounts for 68.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤16368.8%
👍3916.5%
🔥218.86%
👏145.91%

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

Measured over the 28 most recent posts we hold, published 6 February 2026 to 16 November 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

Telegram’s own ‘edited’ marker: 0 of 4 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).

16 Nov 2026, 00:25 UTC618 views4 reactionsread 16 November 2026

📢 悦通申诉通道 遇账户、订阅等问题需申诉?📧 请发邮件至 [email protected]。 邮件需包含问题描述、账号信息及截图,以便核实。 感谢支持!🙏

❤4

10 Nov 2026, 08:10 UTC≈2,000 views2 reactionsread 16 November 2026

面板地址更新通知 面板地址已更新为 https://app.yue.to ,原地址 my.yue.to 已停用。收藏夹里的旧链接将无法打开。 订阅地址没有变化,不用更换。 如果登录时提示通行密钥无效,请先用密码登录,再在安全设置里重新添加通行密钥。 若你曾使用个性化邀请短链接(例如 xxx.yue.to),该链接已失效。邀请码仍然有效,请到面板「邀请返佣」或 Telegram 小程序「邀请」里复制新链接。

❤2

9 Nov 2026, 00:38 UTC≈2,100 views2 reactionsread 16 November 2026

🎉 双十一限时礼遇|全场 7 折 一年一度双十一优惠来啦! 📅 活动时间 11 月 9 日 12:00 — 11 月 11 日 23:59:59(北京时间) 🎁 活动福利 全部在售套餐及周期统一 7 折 新购、续费均可享受优惠 VIP 折扣可叠加使用 首单自动优惠与优惠券取更优价格 🏷 专属优惠码 DOUBLE11 ⚡️ 每个账号限使用一次 优惠限时开放,想续费、升级或购买新套餐的朋友,别错过这次机会! 双十一,就趁现在! ❤️

❤2

22 Oct 2026, 06:49 UTC≈4,520 views13 reactionsread 16 November 2026

🎉 程序员节 💻 10 月 24 日 10:00 至 10 月 25 日 24:00。⏰ 购买页输入 YUE1024,全场 85 折,每人一次。🎟 新用户首单如果更低,按更低的价格。💰 已发放的重置卡仍可在礼品卡页兑换,截止 10 月 27 日 17:39。🎁

👍9❤4

10 Oct 2026, 01:03 UTC≈7,450 views2 reactionsread 16 November 2026

📢 Yue.to | 悦通 所有节点升级公告 尊敬的用户: 为提升节点服务质量与连接稳定性, Yue.to 将于 2026 年 10 月 10 日 20:00–24:00(北京时间) 对所有节点进行升级维护。 升级期间,部分节点可能出现连接异常或暂时无法使用的情况,敬请谅解。 ⚠️ 如遇到无法连接或无法使用的情况,请及时更新订阅后重试。 感谢大家的理解与支持! Yue.to | 悦通 让连接更稳定,让体验更流畅。

👍2

21 Sept 2026, 13:43 UTC≈8,590 views14 reactionsread 16 November 2026

🧧 悦享中秋 · 博饼赢红包 全场 7 折,下单博红包,天天免费博! 这个中秋,优惠和好运一起到 🌕 📅 活动时间(北京时间) 2026 年 9 月 25 日 00:00 — 10 月 7 日 23:59 🎟 全场 7 折,一码通用 下单时填写优惠码:悦享中秋 全部套餐、全部周期享 7 折,每人限用 1 次。 🎲 下单就能博红包,人人有奖 活动期间,每一笔实付订单都可博红包 1 次,抽中现金直接进入「现金钱包」! 🏆 一等奖:¥100 现金红包 × 5 名 🥈 二等奖:¥20 现金红包 × 50 名 🥉 三等奖:¥5 现金红包 × 200 名 🎁 四等奖:积分奖励,可兑换流量,不限量 ☑ 季付及以上/大额一次性套餐:本次博红包保底 ¥5 现金! ♾️ Infinity 无限包用户:直接赠送 1 次机会。 🤝 邀请好友下单:再得 1 次机会,邀请奖励每人最多 2 次。 现金红包名额分 13 天按时段放出,每天都…

❤14

16 Sept 2026, 11:29 UTC≈7,430 views5 reactionsread 16 November 2026

📢 Yue.to | 悦通|套餐价格调整通知 亲爱的 Yue.to 用户: 因节点运营、线路及带宽成本持续上涨,为保障服务质量与线路稳定,我们将于: 🕛 2026 年 9 月 19 日 00:00(北京时间) 正式调整部分套餐价格。 💰 新旧价格对照 💡 Mini|迷你年付 59.90 → 69.90 元/年 ☁️ Air|轻量旗舰 月付 14.90 → 16.90 季付 39.90 → 46.90 年付 119.90 → 139.90 🚀 Pro|进阶专业 月付 29.90 → 33.90 季付 79.90 → 89.90 年付 199.90 → 229.90 👑 Max|企业至尊 月付 45.90 → 56.90 季付 125.90 → 156.90 年付 339.90 → 396.90 🧳 Travel|差旅便携包 22.90 → 26.90 🔋 Stack|囤货加油包 89.90 → 106.90 🪐 Giga|巨…

❤5

2 Sept 2026, 05:46 UTC≈6,880 views23 reactionsread 16 November 2026

📢 YueTo 公告|账号清理及近期攻击说明 各位用户: 近期 YueTo 受到严重网络攻击,目前我们正在持续进行安全防护、服务稳定性及节点方面的处理。 为了减轻系统压力,同时清理长期闲置及未完成认证的账号,我们将在 3 天后进行一次账号清理。 ⚠️ 请大家自行检查账号状态 以下两类账号将进行清理: ❌ 没有有效订阅的账号 ❌ 群内未完成认证的用户 请大家自行登录面板确认自己的账号及订阅状态,并检查是否已经完成群内认证。 请务必在 3 天内完成确认,逾期将自动清理。 如果你的账号有正常有效订阅,并且已经完成群内认证,则无需进行任何操作。 另外,近期受到攻击影响,部分节点可能出现连接异常、速度波动或不稳定的情况,我们正在持续处理和优化,请大家耐心等待。 感谢大家的理解与支持。 YueTo 团队

❤17🔥4👏2

30 Jul 2026, 05:11 UTC≈10,600 views24 reactionsread 16 November 2026

🎉 悦通全新自研面板正式上线 经过本周的系统迁移与数据切换,悦通平台现已完成全面升级,全新自研面板正式投入使用! 本次升级对系统架构、运行性能、数据处理能力及整体稳定性进行了全面优化,各项核心服务目前均已恢复正常。 感谢大家在迁移期间的耐心等待与理解。后续我们将继续完善各项功能,为大家提供更加稳定、流畅、安全的使用体验。 🎁 新面板上线福利 活动时间:8月1日—8月7日 🔥 新用户首单立减50% ✅ 系统自动立减 ✅ 无需领取优惠券 ✅ 下单即可享受优惠 请以结算页面实际显示金额为准。 感谢一路陪伴,欢迎体验全新的悦通! YueLink(悦通)运营团队 🤝

❤14👍8🔥2

23 Jul 2026, 01:31 UTC≈10,400 views12 reactionsread 16 November 2026

📢 悦通系统迁移公告 尊敬的各位用户: 为全面提升系统稳定性、运行性能及后续功能扩展能力,悦通平台将于本周执行全面面板迁移工作。 ⚠️ 服务影响说明 迁移期间,提现功能将暂时暂停,待迁移完成后将第一时间恢复服务。在数据同步及系统切换过程中,可能会出现以下情况: - 偶发性卡顿或页面加载缓慢; - 部分页面短暂无法访问; - 个别功能可能出现短时异常。 上述情况均属于正常技术现象,敬请耐心等待,无需担忧。 🔧 客户端升级建议 为确保最佳的兼容性与用户体验,请所有用户升级至最新版本的客户端。 旧版客户端可能存在兼容性问题,导致部分功能无法正常使用。 🙏 衷心感谢各位用户长期以来对悦通的支持与理解。我们将高效完成迁移工作,致力于为您提供更加稳定、流畅、安全的使用体验。 YueLink(悦通)运营团队 🤝

❤10👏1🔥1

30 Jun 2026, 04:42 UTC≈11,600 views15 reactionsread 16 November 2026

🚀 节点升级通知 兄弟们,咱们已经正式上线量子通信线路! ⚛️ 为了获得最佳连接效果,请大家及时更新节点或订阅。 更新方式: 🔄 一键更新订阅 📲 或重新导入最新订阅链接 ✅ 更新完成后选择最新节点即可使用 本次升级将持续优化线路质量,带来更稳定、更快速、更低延迟的连接体验。 如遇到任何问题,请联系客服或在频道内反馈,我们会第一时间协助处理。 悦通机场 感谢大家一直以来的支持!❤️

❤13👍1👏1

15 Jun 2026, 06:56 UTC≈10,900 views17 reactionsread 16 November 2026

🚀 YUE618 限时优惠 优惠码:YUE618 优惠力度:全场立减 30% 06/18 -> 06/22 限时开放,续费、新购均可使用。 感谢大家对悦通的支持,祝各位端午安康!🎉

❤14👏2🔥1

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

Mentions

Named by 2 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.

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

“Yue.to | 悦通” (@yueto_news), 6,771 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/yueto_news.

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.