Telegram RegisterThe public register of Telegram
Telegram profile photo for YT.NET | CHANNEL

Channel

YT.NET | CHANNEL

@net2yt

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

1,903subscribers

-149 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003297121979
TypeChannel
Username@net2yt
CreatedBetween 1 October 2025 and 28 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/net2yt

Growth

1,8962,0521,9747 August 2026 — 2,052 subscribers7 August 2026 — 2,052 subscribers8 August 2026 — 2,044 subscribers11 August 2026 — 2,012 subscribers14 August 2026 — 1,970 subscribers17 August 2026 — 1,934 subscribers20 August 2026 — 1,914 subscribers24 August 2026 — 1,896 subscribers27 August 2026 — 1,903 subscribers1,9037 August 202627 August 2026
9 measurements spanning 20 days, net -149. 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,873–2,075 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 18:161,903+7
24 Aug 2026, 17:441,896-18
20 Aug 2026, 18:291,914-20
17 Aug 2026, 20:371,934-36
14 Aug 2026, 19:461,970-42
11 Aug 2026, 15:082,012-32
8 Aug 2026, 12:302,044-8
7 Aug 2026, 20:322,052no change
7 Aug 2026, 18:542,052first reading

Engagement

20 posts held, back to 8 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
30.2%
avg views ÷ 1,903 subscribers
Avg views / post
575
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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 6 August 2026
Posts held20 (8 March 20266 August 2026)
Views total575
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 20:32 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.

Reaction mix

148 reactions across 16 posts, in 12 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3120.9%
3020.3%
💩2416.2%
🤣1610.8%
🤮138.78%
😁128.11%
👏74.73%
🤡64.05%
😭53.38%
🔥21.35%
🖕10.676%
🙈10.676%

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

Measured over the 20 most recent posts we hold, published 8 March 2026 to 6 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

24 Jul 2026, 10:44 UTC≈1,510 views5 reactionsread 7 August 2026

JP.TYO 暑期优惠 1c/1g/1000GB@500Mbps 折后 178.2/年 限量供应 下单地址 https://cloud.yt.net/server/config/106 500M LG: jp-tyo.lg.yt.net

😁5

21 Jul 2026, 12:22 UTC≈1,440 viewsread 7 August 2026

洛杉矶9929+CMIN2节点上线 下单地址 https://cloud.yt.net/deploy/us-lax 200M规格测速地址 https://lax.lg.yt.net/ 八五折循环优惠码 LAX85

20 Jul 2026, 15:21 UTC≈1,420 views0 reactionsread 7 August 2026

香港TKO优化节点上线 下单地址 https://cloud.yt.net/deploy/hk-tko 180M规格测速地址 https://hk-tko.lg.yt.net 九折优惠码 OFF90

25 Jun 2026, 05:27 UTC≈2,330 views5 reactionsread 7 August 2026

日本东京 BGP 节点正式上线通知 下单地址 https://cloud.yt.net/deploy/jp-bgp 限时优惠 循环七五折优惠码:jp75(续费同享,长期有效) 首发福利回馈 为感谢大家的首发支持,我们将于 7 月 1 日统一操作,为 7 月 1 日之前购买且仍在有效期内的服务附赠以下额度: 年付用户: • 12 次免费流量重置额度 • 3 次免费更换 IP 额度 • 1 个免费快照位 月付用户: • 1 次免费流量重置额度 • 1 次免费更换 IP 额度 说明:以上赠送额度不会清零、不会过期,可长期累积使用。执行重置、更换 IP 等操作时将优先抵扣赠送的免费额度,扣完后再按正常规则计费。

3💩2

16 Jun 2026, 16:27 UTC≈2,170 viewsread 7 August 2026

关于网络调整作业通知 尊敬的用户: 我们将于 2026 年 6 月 17 日 02:00—05:00 进行网络传输调整,期间网络将短暂中断,预计 10—30 分钟。 此次维护不影响您的服务器实例运行及数据,无需任何操作。建议您避免在此期间进行重要业务变更或大规模数据传输。 给您带来的不便,敬请谅解。如维护后业务出现异常,请提交工单联系客服。 感谢您的理解与配合。

27 May 2026, 10:37 UTC≈2,980 views2 reactionsread 7 August 2026

关于网络架构优化及割接维护的公告 尊敬的用户: 您好!为持续提升网络稳定性与服务质量,现针对即将进行的网络架构优化及割接操作发布公告,请您留意并提前做好准备: 1. 维护时间与内容 我们计划于 5 月 28 日凌晨 03:00 进行底层网络架构的深度优化及切割(割接)作业。 2. 影响范围 在网络切割操作期间,相关节点的网络可能会出现短暂的中断或路由波动。我们将全力压缩操作时间,尽快完成割接以恢复网络平稳。 3. 注意事项 此次维护仅针对底层网络架构,您的服务器实例运行及底层数据不会受到任何影响,无需进行任何操作。为确保您的业务平稳,建议您尽量避免在上述维护时间段内进行重要业务变更或大规模数据传输。 给您带来的不便,我们深表歉意。如果在维护结束后您的业务出现异常,请随时通过提交工单联系客服处理。 感谢您的理解与配合。

1💩1

12 May 2026, 14:43 UTC≈5,110 views18 reactionsread 7 August 2026

关于 YT IX 互联调整及广州电信系列下架的公告 尊敬的用户: 您好!现针对以下两项业务变动发布公告,请相关用户留意并提前做好准备: 1. YT IX 系列互联调整 YT IX 系列近期接收到阿里云的整改通知。为积极响应并配合整改自查工作,我们已暂时断开与阿里云的 IX 互联。具体恢复时间待定,后续有任何进展我们将另行通知。 2. 广州电信系列下架及善后方案 广州电信系列因收到违法通报,经取证调查后被作拔线处理,将于明天正式执行拔线。 针对受此影响的用户,我们将采取以下善后与补偿方案: 余额退款:所有受影响的机器,将统一按照剩余价值退回至您的平台余额。 数据保留与提取:机器关机后,底层数据将为您至少保留 7 天。如您未能及时完成备份,可通过提交工单联系客服,我们将协助您进行资料提取。 专属补偿:在完成剩余价值退款后,系统将向受影响用户补偿一张 7 折循环优惠券,该优惠券针对所有在售云主机产品均可使用。 请各位

💩105🔥1🖕1🤮1

22 Apr 2026, 03:22 UTC≈3,850 views26 reactionsread 7 August 2026

关于 CNIX NAT 系列开放自愿迁移至 HK-BGP 系列的公告 尊敬的用户: 为提供更优质的网络体验,现正式开放 CNIX NAT 实例自愿迁移至全新的 HK-BGP 系列。HK-BGP 在网络与功能上已完全覆盖 CNIX 的所有使用场景,并彻底解决了原架构共用出口 IP 易受攻击连带断网的痛点。 【自愿原则】 本次迁移纯属自愿。如您无需迁移,现有服务不会受到任何影响,可正常使用。 【迁移与升级说明】 网络升级:出口 IP 升级为独立 IP;IX 端口由 20 个大幅扩容至 50 个。 资费不变:套餐配置、当前资费及续费价格均保持不变,架构升级带来的硬成本由我司全额承担。 数据过渡:客服操作后新实例立即可用,旧实例将保留并调整为三天后到期。请务必在此期间自行完成数据转移。 人工手续费:因跨架构迁移无法自动化,必须由技术客服逐一进行人工开通与调度,因此将象征性扣除 10 元人工操作费。 【申请方式】 如需

8💩8👏7👍1🔥1🤮1

10 Apr 2026, 16:47 UTC≈6,230 views31 reactionsread 7 August 2026

深圳BGP清退 有个叫北京云途的被拔线 躺枪 所有深圳BGP用户 按照剩余价值退款 资料还在(联系客服提) 大家也不要有情绪 特殊时期是这样 回头把公司名字改了(bushi

🤣16🤡6😭51💩1🤮1🙈1

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

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

“YT.NET | CHANNEL” (@net2yt), 1,903 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/net2yt.

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.