Channel
@zhanghaoverse
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
15subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001864249773 |
|---|---|
| Type | Channel |
| Username | @zhanghaoverse |
| Description | all for zhang hao always with zhang hao |
| Created | 6 October 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/zhanghaoverse |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 23:46 | 15 | no change |
| 7 Aug 2026, 20:04 | 15 | first reading |
8 posts held, back to 24 May 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 1 pageof 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 8 posts for this entry, the most recent from 7 September 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
975 reactions across 8 posts, in 13 distinct kinds. The most used accounts for 34.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 333 | 34.2% | |
| custom 5355001130579410019 | 178 | 18.3% | |
| 💘 | 166 | 17.0% | |
| 💔 | 115 | 11.8% | |
| 💋 | 48 | 4.92% | |
| 😭 | 42 | 4.31% | |
| 🍓 | 38 | 3.90% | |
| ❤🔥 | 20 | 2.05% | |
| 🥰 | 14 | 1.44% | |
| 👍 | 10 | 1.03% | |
| custom 5400325735770502231 | 5 | 0.513% | |
| 🔥 | 5 | 0.513% | |
| 💅 | 1 | 0.103% |
Custom emoji. 2 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 areTelegram’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 8 of the 8 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 975reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 24 May 2024 to 7 September 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
story of haoverse has come to an end. 🗝️ если вы зашли сюда снова, я хочу поблагодарить вас за вашу поддержку и привязанность к хаоверс. спустя долгое время я ставлю точку в истории этого канала и делаю его открытым на тот случай, если вы захотите пересмотреть старые посты и треды. оставляю ссылку на сайд , если вы просто хотите поддерживать со мной связь ~
💔12💘10😭8custom 54003257357705022315❤3
ㅤ ㅤ right person wrong place ㅤ
❤97💘39custom 535500113057941001928💔15😭9🍓7💋4🔥3
❗️кроме того, сегодня хао подвергся массовой атаке со стороны антифанатов в социальных сетях, поэтому нам также необходимо очистить поиск и отправить жалобу на них 🩵чистка поисковых запросов! скопируйте слова ниже, а потом ищите каждое слово индивидуально, чтобы эффективно убрать негативные поисковые запросы 🩵장하오 죽간아 🩵장하오 죽간아이돌 🩵장하오 죽간아 직캠 🩵장하오 죽간아 바이올린 примечание: потратьте 1 минуту на изучение запроса/просмотри…
custom 535500113057941001952❤24😭21🍓5💘5💔3❤🔥2👍2
🩷фанбазы решили выводить хэштеги и отправлять письма агентству, чтобы они обратили на это внимание и взялись за дело, поэтому следуйте этой инструкции: 🩷подключайтесь к хэштег трендингу TAKE LEGAL ACTION AGAINST STALKERS WAKEONE DO YOUR JOB PROPERLY #WAKEONETAKEACTION #PROTECTZHANGHAO @wakeone_offcl @ZB1staff 🩷массовая отправка писем электронной почте wakeone ! 🩷английская версия ! 🩷корейская версия ! 🩷обязател…
❤49💘15❤🔥8🍓4💋3💔3custom 53550011305794100192👍1
некомпетентность wakeone привела к тому, что анти почувствовали себя достаточно комфортно, чтобы дойти до преследования и нарушения личных границ чжан хао в отеле, пока он был в бельгии❗️ сасэнка и ее подруга, которые остановились в том же отеле, что и джеби, делали секретные фотографии хао, распространяли его личную информацию, а также кричали на него, когда хао брал еду на вынос, беспокоили его во время завтрака в…
💔82❤24💘15💋9🍓6custom 53550011305794100195👍2❤🔥1
✉️ ( 240524 ) twitter / x update я очень, очень рад стать сегодня спешл мс и занять первое место 🥹 я буду работать еще усерднее чтобы отплатить за любовь, которую я получил, и показать вам еще лучшие выступления и музыку. давайте продолжим писать наше будущее вместе!!!
❤57💘26custom 535500113057941001920💋14🍓7👍3❤🔥2🥰1
my candy, muffin, monblanc, macaroon, dessert, lolly bread, madeleine, cookie, pepsi, shu, custard, oreo, cereal, jelly, apple pie, tart, roll cake, parfait, bread, milk shot, smore cookies, yogurt, waffle, marmalade, jello, baguette, cupcake, marshmallow, dumpling, cheesecake… 😭
❤57💘28custom 535500113057941001921💋10🍓4❤🔥2🥰2
he's so freaking beautiful 😍🥰
custom 535500113057941001950💘28❤22🥰11💋6🍓5❤🔥3😭3
Showing the 8 most recent of 8 posts we hold for @zhanghaoverse. 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“haoverse ౨ৎ” (@zhanghaoverse), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/zhanghaoverse.
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.