Channel
@hanguo
On this record: Growth · Engagement · Posts · Citations · Cite this entry
53subscribers
+1 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002438985883 |
|---|---|
| Type | Channel |
| Usernames | @hanguo @liwupu |
| Created | 29 September 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 3 September 2026 |
| On Telegram | t.me/hanguo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 12:18 | 53 | no change |
| 27 Aug 2026, 02:13 | 53 | +1 |
| 12 Aug 2026, 14:52 | 52 | no change |
| 12 Aug 2026, 14:47 | 52 | first reading |
4 posts held, back to 29 September 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 4 posts for this entry, the most recent from 21 February 2025. An engagement rate over an empty window would be a number about nothing.
🍀高净值用户名商店(Username Store) 💕 @Yibao 便捷按钮Convenient button 🎨租赁用户名 | Rental Username 🎆购买用户名 | Buy Username 中文 ：列表1·列表2·列表3·列表4·列表5·列表6 English ：list1 💕888匿名数字 | Anonymous numbers 888 🆘信息和帮助 | Information and help 1·2·3 电报中文知识分享 @zhishi @xuexi 业主 | Owner ：@Grape 🔤🌹🔤🔤🔤
fragment.com/username/hanguo
用户名出售列表（4）🟥 城市集组合出售⭐️ ▶️@haixi 海西 ▶️@ziyang 资阳 ▶️@shate 沙特 ▶️@hanguo 韩国 ▶️@laisuotuo 莱索托 ▶️@kemoluo 科摩罗 ▶️@jiana 加纳 ▶️@tonga 汤加 ▶️@bageda 巴格达 ▶️@dazhou 达州 ▶️@wulanbatuo 乌兰巴托 ▶️@yisitanbuer 伊斯坦布尔 ▶️@jilongpo 吉隆坡 ▶️@helan 荷兰 ▶️@liwupu 利物浦 ▶@danzhou 儋州
Channel created
Showing the 4 most recent of 4 posts we hold for @hanguo. 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 7 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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“韩国华人🇰🇷@hanguo” (@hanguo), 53 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/hanguo.
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.