🚫📱 Telegram 手机端App 访问受限 ⚠️ 当前频道内容无法在 Telegram 手机端App 内查看。 🌐 请使用 Telegram 中文网页版 访问完整内容 🔓 解锁全部频道信息 📢 查看最新频道动态 🚀 获得最佳浏览体验 👇 点击立即查看此信息 https://app.telegram-org.xyz?message=hanguo_sucaiok/1084
❤1

Channel
@hanguo_sucaiok
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
857subscribers
-198 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003807771344 |
|---|---|
| Type | Channel |
| Username | @hanguo_sucaiok |
| Created | Between 1 February 2026 and 10 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/hanguo_sucaiok |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 |
|---|---|---|
| 13 Sept 2026, 11:19 | 857 | -72 |
| 4 Sept 2026, 15:20 | 929 | -69 |
| 27 Aug 2026, 09:36 | 998 | -12 |
| 24 Aug 2026, 14:36 | 1,010 | -15 |
| 21 Aug 2026, 00:52 | 1,025 | -1 |
| 17 Aug 2026, 18:58 | 1,026 | -9 |
| 14 Aug 2026, 16:08 | 1,035 | -8 |
| 11 Aug 2026, 04:38 | 1,043 | -9 |
| 8 Aug 2026, 04:57 | 1,052 | -3 |
| 8 Aug 2026, 00:18 | 1,055 | no change |
| 7 Aug 2026, 14:03 | 1,055 | first reading |
7 posts held, back to 10 April 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 7 posts for this entry, the most recent from 19 July 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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 2 of the 7 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 10 April 2026 to 19 July 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 手机端App 访问受限 ⚠️ 当前频道内容无法在 Telegram 手机端App 内查看。 🌐 请使用 Telegram 中文网页版 访问完整内容 🔓 解锁全部频道信息 📢 查看最新频道动态 🚀 获得最佳浏览体验 👇 点击立即查看此信息 https://app.telegram-org.xyz?message=hanguo_sucaiok/1084
❤1
✨绘图大师·加密货币网银P图【其他均为病毒】 , ✨绘图大师官方频道✨P图软件✨https://t.me/huitudashiSVlP 😲📥以下为素材分类频道📥⚡️⚡️😍😍 😉【海王出海】 😉【网银转账】 😉【人设套图】 😉【聊天翻译】 😉【翻译软件】 😉【三国演义】 😉【中国素材】 😉【007 开户】 请鼠标往上面😊移动,挑选您可以点击蓝色字体
👈🤶人设套图素材业务如下:😉😉😉😄 😖🧐😞 0️⃣海外素材 @suaciroo 1️⃣人设套图 @taotu_sucaiok 2️⃣开客技巧 @renshe_sucaiok 3️⃣狗推宝典 @jingliao_sucaiok 4️⃣素材精聊 @renshe_jingliao 5️⃣精聊话术 @jingliao_huashuh 6️⃣话术素材 @jingliaoo_huashu 7️⃣吃瓜猎奇 @ay2028_cgbg8 8️⃣吃瓜狗推 @MB_149_bp888 9️⃣搞笑视频 @cgbg8_achigua ➕吃瓜群众 @achiguao_achigua ➕吃瓜素材 @chigua186_chiguasucai 🧐😆🙂↕️ 😘@sucai933…
❤1
📱精选人设素材一直在持续更新最新人设素材 💻请大家持续关注👍频道😀以免上架错过更好的人设素材🥰祝您天天开大单,财源广进!分类素材频道如下🦜 😊海外素材 ⏩@suaciroo 😊客服系统⏩ @chats007_H0 😊人设套图 ⏩@taotu_sucaiok 🇮🇳印度素材 ⏩@yindu_sucaiok 🇯🇵日本素材 ⏩@riben_sucaiok 🇹🇼台湾素材 ⏩@taiwan_sucaiok 🇺🇸美国素材 ⏩@meiguo_sucaiok 🇰🇷韩国素材 ⏩@hanguo_sucaiok 🇸🇬新加坡素 ⏩@xinjiapo_sucaiok 🇬🇧英国素材 ⏩@yingguo_sucaiok 🇲🇾马来西亚 ⏩@malaixiya_sucaiok 🇨🇳中国素材 ⏩@zhongguo_sucaiok 🇭🇰香港素材 ⏩@xianggang_sucaiok 😊绘图大师 ⏩@huitudashi_huitu 🔼搜索方法:输入 “#关键词”…
财旺 人设素材 人设套图导航区,挑选好三方发编号或者转发给客服 https://t.me/taotu339 😘❤️😊感谢新老客户的信任 🤤财旺人设套图素材业务如下:😭😜💋😌 生活素材【素材库 】 @suaciroo 人设套图【亚洲女 】 @taotu_sucaiok 人设套图【亚洲男 】 @taotu_sucaiqi 人设套图【欧美女 】 @taotu_sucaiqy 人设套图【欧美男 】 @taotu_sucaitu 人设套图【证件女 】 @taotu_sucaiyo 人设套图【证件男 】 @taotu_sucaiju 人设套图【女私密 】 @taotu_sucaika 人设套图【设计馆 】 @taotu_sucaiye 绘图大师【钻图馆 】 @huitudashi_hui…
📍청담 트웰브(TWELVE) 서울특별시 강남구 도산대로 442 , B1층 #韩国 #首尔 #清潭洞 #lifestylevision #逛超市
cube打卡了,虽然一直在走路但小韩我下次还会来的。 #idle #韩国 #旅行 #cube #首尔
Showing the 7 most recent of 7 posts we hold for @hanguo_sucaiok. 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 54 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@hanguo_sucaiok 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“🇰🇷韩国素材🇰🇷” (@hanguo_sucaiok), 857 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/hanguo_sucaiok.
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.