File, posted without a caption
Channel
业务频道
@Yuanhen01
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry
32subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003697723126 |
|---|---|
| Type | Channel |
| Username | @Yuanhen01 |
| Created | Between 1 December 2025 and 16 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/Yuanhen01 |
Topic
Hacking & security — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 00:58 | 32 | -1 |
| 30 Sept 2026, 18:18 | 33 | -2 |
| 30 Aug 2026, 11:37 | 35 | -1 |
| 22 Aug 2026, 14:02 | 36 | +1 |
| 10 Aug 2026, 23:31 | 35 | no change |
| 7 Aug 2026, 18:52 | 35 | first reading |
Engagement
20 posts held, back to 16 March 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 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 20 posts for this entry, the most recent from 6 April 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 20s
- Average length
- 20s
Measured directly from 1 video 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
9 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 44.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 44.4% | |
| 👍 | 2 | 22.2% | |
| 🤣 | 2 | 22.2% | |
| 👎 | 1 | 11.1% |
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 4 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 9 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 16 March 2026 to 6 April 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
担保由买家定
出一份无限制p三很快 几万条照样跑 所有运营商都能跑 私信报价 支持任何担保 支持测试 购买联系 @Yuanhen0
莫欺少年穷
❤1
吃饱喝足拜拜啦 跑你们就只能受着了谢谢!!!
❤1👍1👎1🤣1
这几天有点累 所有业务暂停几天 不好意思
单头全户压压价怎么样
这几天搞到一个单头全户的路子 可惜了 不带板子 有人能做独家板子的可以来私信我
❤1
真文全9️⃣🔤保真不保漏 现在来一直在排队秒 此文全为真文全 吊打市面任何一家低价文全 支持埋雷测试 支持双押复查 随便埋雷 不是真的头砍下来送给你 报单联系 @Yuanhen0
文字全户9️⃣🔤保真不保漏❗️❗️❗️排队秒 文字全户9️⃣🔤保真不保漏❗️❗️❗️排队秒 文字全户9️⃣🔤保真不保漏❗️❗️❗️排队秒 量大可以拿屠龙刀来砍 支持测单 支持双押 联系客服 @Yuanhen0
😀😀😀😀🇺🇿 营业执照😀😀秒 客服联系 @Yuanhen0
😀😀😀😀🇺🇿 公网单头3️⃣🔤8️⃣🔤公网单头3️⃣🔤8️⃣🔤 有量来谈 联系客服 @Yuanhen0
Showing the 12 most recent of 20 posts we hold for @Yuanhen01. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@Yuanhen01 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 10 posts, 11 August 2026 – 11 August 2026
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“业务频道” (@Yuanhen01), 32 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/Yuanhen01.
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.