Telegram RegisterThe public register of Telegram
Telegram profile photo for 微斯人,吾谁与归 NOC

Channel

微斯人,吾谁与归 NOC

@Ash_NOC

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

7,143subscribers

+507 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-1002140494078
TypeChannel
Username@Ash_NOC
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/Ash_NOC

Growth

6,6367,1436,889.57 August 2026 — 6,636 subscribers8 August 2026 — 6,646 subscribers11 August 2026 — 6,661 subscribers14 August 2026 — 6,699 subscribers17 August 2026 — 6,734 subscribers20 August 2026 — 6,817 subscribers24 August 2026 — 6,901 subscribers27 August 2026 — 6,965 subscribers30 August 2026 — 7,025 subscribers2 September 2026 — 7,075 subscribers7 September 2026 — 7,143 subscribers7 August 20267 September 2026
11 measurements spanning 31 days, net +507. 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 6,560–7,219 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 16:157,143+68
2 Sept 2026, 08:347,075+50
30 Aug 2026, 15:177,025+60
27 Aug 2026, 07:386,965+64
24 Aug 2026, 17:356,901+84
20 Aug 2026, 16:446,817+83
17 Aug 2026, 13:266,734+35
14 Aug 2026, 08:266,699+38
11 Aug 2026, 02:156,661+15
8 Aug 2026, 09:016,646+10
7 Aug 2026, 14:336,636first reading

Engagement

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

ERR · 30 days
34.2%
avg views ÷ 7,143 subscribers
Avg views / post
2,450
2 posts measured
Reaction rate
0.225%
reactions ÷ views · ER floor
Posts in window
2
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 16 August 2026
Posts held20 (12 February 202616 August 2026)
Views total4,890
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 05:06 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

349 reactions across 15 posts, in 12 distinct kinds. The most used accounts for 29.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡10329.5%
👎7320.9%
5214.9%
💩5014.3%
👍4613.2%
🤮102.87%
😭82.29%
😡20.573%
🤣20.573%
🐳10.287%
👏10.287%
🫡10.287%

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 349 reactions 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 12 February 2026 to 16 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Ash_NOC. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 12 February 2026 to 16 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

16 Aug 2026, 16:27 UTC≈2,520 views9 reactionsread 20 August 2026
Photo

🌙 七夕 · 限定优惠 又是一年七夕 💕 💗 在售套餐 · 85 折 🎟 优惠码:7777 🗓 活动时间 8 月 17 日 00:00 — 8 月 21 日 23:59 ❤️愿这个七夕,有喜欢的人相伴,也有稳定的网络陪伴。

9

12 Aug 2026, 18:15 UTC≈2,370 views2 reactionsread 20 August 2026

📢 线路更新通知 目前线路已完成调整,速度及实际使用表现正常。 部分 CT(电信)方向 Ping 延迟暂时偏高,主要受当前路由影响,延迟数值不代表实际速度,建议以实际使用速度和稳定性为准。 上游预计将在 下个月进行扩容及路由优化,后续我们也会持续跟进调整。 🔄 请大家重新更新一次订阅,获取最新节点配置。 如有需要,也可前往「我的订阅 → 附加入口」自行选择备用入口,支持多选。

👎2

7 Aug 2026, 03:12 UTC≈3,480 views4 reactionsread 20 August 2026
Photo

上线了 AshEmby 求片功能,可前往官网自行求片。

3👍1

5 Aug 2026, 17:14 UTC≈3,460 viewsread 20 August 2026
Photo

目前已经重置所有用户的附加入口选择,默认选择所有入口,如果觉得节点过多,可以去官网->我的订阅取消相应的附加入口。

5 Aug 2026, 02:48 UTC≈3,320 views0 reactionsread 20 August 2026

已经切了,等dns刷新,已经加了一台负载,套餐限速已经暂时解除

5 Aug 2026, 02:26 UTC≈3,140 viewsread 20 August 2026

入口故障,紧急维护中,预计30分钟。先用aws入口和3倍入口

29 Jul 2026, 13:37 UTC≈4,230 viewsread 20 August 2026

维护通知 入口:透传IEPL 影响:约为5分钟,不超过30分钟 日期:2026-07-30 0:00 至 2026-07-30 0:05 GMT+9 原因:更换入口IP

27 Jul 2026, 17:21 UTC≈4,050 views4 reactionsread 20 August 2026

因后端域名被管局暂停解析,导致节点短暂掉线,目前已恢复正常,所有有效用户统一补偿 1 天服务时长,感谢大家的理解与支持!(补偿已经送出)

2🤣2

19 Jul 2026, 14:01 UTC≈8,690 views14 reactionsread 20 August 2026
Photo

📢 附加入口功能上线|加量不加价 为改善不同网络环境下的连接体验,现已为所有有效套餐增加附加入口功能,无需额外付费。 目前提供以下线路: 🔹 透传 IEPL 🔹 AWS 日本 🔹 Gomami 🔹 Sakura 如果默认线路无法正常使用,可进入「我的订阅」→「附加入口」,选择一个或多个可用入口并保存,然后在客户端中重新更新订阅。 附加入口不会替换或删除原有节点,只会额外增加备用节点。默认线路正常的用户无需设置。 ✅ 支持选择多个入口 ✅ 加量不加价

👍122

11 Jul 2026, 14:02 UTC≈5,910 views5 reactionsread 20 August 2026

📢 服务更新公告 江浙沪地区的朋友们请注意安全 🌧 建议尽量减少非必要的外出,确保人身安全。 本次更新对面板及相关页面进行了调整与优化: ✨ 优化了部分页面的 UI 样式与布局显示 🧾 改善了订单、支付及套餐等页面的交互体验 📱 修复了部分移动端显示异常及页面溢出问题 ⚙️ 优化了部分功能逻辑,提升了整体使用流畅度 此外,客户端线路亦有更新: 🚄 Medium 及以上套餐客户已新增深港 IEPL 线路。 📌 该线路为客户端专属。 符合条件的用户在客户端更新订阅后即可查看并使用。感谢大家一直以来的支持 🙏

4👍1

18 Jun 2026, 17:28 UTC≈15,400 views2 reactionsread 20 August 2026

🐉 粽香端午 · 限时特惠 端午佳节将至,为感谢大家一直以来的支持与陪伴,现开启端午限时优惠活动! 🎁 所有在售套餐 85 折 🏷 优惠码:端午安康 📅 活动时间 即日起 - 2026/06/25 23:59 趁活动期间续费或升级,可提前锁定优惠价格。 感谢大家一直以来的支持,祝各位端午安康,万事顺遂! 🐲

2

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

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

“微斯人,吾谁与归 NOC” (@Ash_NOC), 7,143 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/Ash_NOC.

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.