Channel
@junhao_m0_0n
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
576subscribers
+8 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003269046812 |
|---|---|
| Type | Channel |
| Username | @junhao_m0_0n |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/junhao_m0_0n |
Music — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 17 Sept 2026, 22:16 | 576 | +15 |
| 8 Sept 2026, 19:57 | 561 | -5 |
| 31 Aug 2026, 00:43 | 566 | -4 |
| 24 Aug 2026, 04:46 | 570 | -6 |
| 16 Aug 2026, 22:04 | 576 | +7 |
| 10 Aug 2026, 15:47 | 569 | +1 |
| 9 Aug 2026, 19:47 | 568 | first reading |
10 posts held, back to 8 August 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 10 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 8 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.
258 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 20.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249153774693400679 | 52 | 20.2% | |
| ❤ | 52 | 20.2% | |
| custom 5208968969750330825 | 40 | 15.5% | |
| 💘 | 33 | 12.8% | |
| 🍓 | 29 | 11.2% | |
| custom 5246909495367445966 | 18 | 6.98% | |
| ❤🔥 | 17 | 6.59% | |
| custom 5242673360533467079 | 15 | 5.81% | |
| 💋 | 2 | 0.775% |
Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 9 of the 10 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 258 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 8 August 2026 to 9 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.
🤩 мальчики tws пришли порадовать вас своим новым летним синглом ! присоединяйтесь к нам и наслаждайтесь им вместе с админкам 🤩 🤩---------------------------------🤩 🤩tws 🍶shinyu 🍶dohoon 🍶youngjae 🍶jihoon 🍶hanjin 🍶kyungmin 🍶jihoon & doohon 🍶shinyu & doohon 🤩seventeen 🍶the8 🍶woozi 🍶seungkwan 🍶jeonghan & joshua 🍶jun & the8 🤩&team 🍶&team ot9 🍶ej 🍶fuma 🍶yudai 🍶nicholas 🍶yuma 🍶harua 🍶t…
каждый день года выкладываю джунхао моменты до тех пор, пока джунхао не дропнут селку 🪄 😍🤩🤩🤩2️⃣2️⃣1️⃣ когда хао о малатанговых ужинах чайна-лайна рассказывал 🤩 мёнсу : среди севентин есть ещё китайские участники? 🐸 : джун мёнсу : вы скорее всего часто полагаетесь на друг друга? 🐸 : когда мы были трейни мы действительно очень много полагались один на другого... мёнсу : вы плакались друг другу и ели малатан? 🐸 : мы е…
custom 52089689697503308257custom 52491537746934006792💋1💘1custom 52426733605334670791
°• - new 🙄 post ! (090826) ☾ - •° 🥳✌🏻 мастер переходов снова в деле 🙏 ✨ #dy ✨ #jun_update ✨
custom 524267336053346707910custom 52089689697503308254🍓1💘1custom 52491537746934006791
°• - new 🙄 post ! (090826) ☾ - •° спасибо кинопремии "Hundred Flowers", спасибо вам всем вам за поддержку! ❤️ я буду продолжать усердно работать! 🤩💪🏻 я очень благодарен всем, кто поддерживал меня на протяжении всего этого времени! ❤️ в будущем я буду и дальше прикладывать все усилия! 😆 (написал на китайском и корейском) ✨ #wb ✨ #jun_update ✨ #inst ✨
❤10custom 52491537746934006796💘1custom 52426733605334670791custom 52469094953674459661
речь джуна на 38th Hundred Flowers Awards номинации «лучший актёр второго плана» за роль ху фэна 🫶 это благодаря вашей поддержке я смог достичь того, что у меня есть сейчас. эта честь принадлежит всем. эта номинация также дала мне поверить ещё больше в то, в что я всегда верил : «нет маленьких ролей, и нет маленьких актёров». каждый шаг важен и я тоже продолжу усердно работать. всем спасибо!
custom 520896896975033082518💘5💋1custom 52469094953674459661custom 52491537746934006791
папа с сыном 🥺
custom 524915377469340067916❤6🍓6💘6custom 52469094953674459662custom 52089689697503308251
джуни сегодня участвовал в объявлении номинантов за звание "лучший актёр второго плана" на премии Hundred Flowers Awards и исполнял песню на её открытии 🫣
❤15❤🔥8custom 52491537746934006794💘3custom 52089689697503308251
вэнь джунхуэй или ху фэн?????
❤20custom 524690949536744596612🍓9❤🔥3💘2custom 52491537746934006791
каждый день года выкладываю джунхао моменты до тех пор, пока джунхао не дропнут селку 🪄 😍🤩🤩🤩2️⃣2️⃣0️⃣ называется угадайте, кто из них старший, а кто самый младший ☺️ > #everydayJ8 (hbd to 🍒)
🍓12custom 52089689697503308257💘3custom 52426733605334670793custom 52491537746934006792❤1custom 52469094953674459661
чоли упомянул джуна во время своего праздничного лайва 🥺 🍒 : джун тоже прислал мне поздравление в какао толк, я ответил ему «оо, файтин~»
custom 524915377469340067919💘11❤🔥6custom 52089689697503308252🍓1custom 52469094953674459661
Showing the 10 most recent of 10 posts we hold for @junhao_m0_0n. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 16 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“𝙩𝙤 𝙢𝙮 𝙢𝙤𝙤𝙣<( ℋ )> 🌙” (@junhao_m0_0n), 576 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/junhao_m0_0n.
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.