Channel
@for_zhanghao
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
331subscribers
-2 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002492972600 |
|---|---|
| Type | Channel |
| Username | @for_zhanghao |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/for_zhanghao |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:04 | 331 | -2 |
| 12 Aug 2026, 04:45 | 333 | no change |
| 12 Aug 2026, 04:31 | 333 | first reading |
13 posts held, back to 26 May 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 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 13 posts for this entry, the most recent from 28 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 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.
417 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 28.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5406710041447276530 | 119 | 28.5% | |
| custom 5409058525269758004 | 106 | 25.4% | |
| custom 5330077882037339447 | 97 | 23.3% | |
| custom 5330263093912045589 | 95 | 22.8% |
Custom emoji. Every row above is a 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 12 of the 13 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 417reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 26 May 2026 to 28 May 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.
простите, что нет обновлений на канале :[ из-за высокого загруза на работе и ночные смены я толком не успеваю поспать, поэтому начала чувствовать тревожность. вернусь 3-4 июня, мне правда искренне жаль, что не могу быть активной в драгоценную первую неделю дебюта эндабл :(
custom 540671004144727653020custom 540905852526975800413custom 53302630939120455893
Signed ¿
ему пять годиков 🫳
custom 533007788203733944715custom 533026309391204558910custom 54090585252697580047custom 54067100414472765305
Signed ¿
олли ( yuehuaz’s baby ) о «curious» и, возможно, о том, что сможет поехать на фанкон и снять челлендж 💔 🍫 братья слишком красивые! каждый очень выделяется по-своему. эти два главных вокалиста просто невероятны, а потом это движение, где рики тянет за руку перед припевом… а когда я увидел танцевальный брейк хан юджина… о боже мой… и две высокие ноты сынона… это вау! 🍫 я сделаю кавер, точно сделаю. сегодня я посмотрел…
custom 540905852526975800416custom 533007788203733944711custom 53302630939120455898custom 54067100414472765305
Signed ¿
пожалуйста, подключайтесь к стримингу эндабл в spotify или на stationhead и стримингу curious в youtube 🥺 релизы and2ble не добавлены ни в один официальный плейлист spotify, их профиль не виден в поиске, а для клипа нет рекламы и есть подозрения на теневой бан ютуб-аккаунта эндабл. поэтому мы должны приложить МАКСИМУМ усилий. к тому же за первый день продаж альбома мы достигли отметки в 157 тысяч копий ( мне мало ве…
custom 540905852526975800410custom 53300778820373394476custom 53302630939120455896custom 54067100414472765302
Signed ¿
очень важно, нам нужно: 1) стримить эндабл на ютубе и в споти. здесь рассказали про стэйшнхэд и плейлисты для стриминга + правила стриминга (ютуб и споти) 2) снимать тиктоки, хайпить дебютный альбом по максимуму. можете постить мемы и что угодно, чтобы под звуком curious было много видео!! хоть и у эндабл есть фанбаза, все-таки это их новое начало и поддержка нужна в троекратном размере 🙏 3) постепенно готовьтесь …
custom 533026309391204558910custom 54067100414472765304custom 53300778820373394473
Signed ¿
when the quality is 144 but you’re both jjangkyuz enthusiasts #thank_you_kkyu.txt_bro 🫂
custom 533007788203733944713custom 540671004144727653011custom 53302630939120455899custom 54090585252697580046
Signed ¿
Channel photo updated
не забывайте стримить curious на ютуб и стэйшнхиде ! пока на сегодня всё, остальное выложу посреди ночи или утром, я убежала работать 😢
custom 533026309391204558911custom 54067100414472765306custom 54090585252697580046
Signed ¿
you did so well today, our leader hao 🥺🫳🏻
custom 540905852526975800411custom 533007788203733944710custom 53302630939120455897custom 54067100414472765305
Signed ¿
ребята рассказывали о том, как писали лирику к песням, и кюби, конечно же, не мог не похвалить своего хао хена :< ⭐️ мы с кюбином работали над одними и теми же частями [в happy&], когда я писал лирику, то представлял это как создание картины. сначала я формулировал мысли на китайском, а потом писал текст, будто это стихи. я хотел, чтобы люди, переслушивая нашу песню, могли ярче представлять эти сцены, поэтому и писа…
custom 540671004144727653015custom 533026309391204558911custom 53300778820373394478custom 54090585252697580042
Signed ¿
юю должен был выбрать кого-то одного, чтобы обнять сзади и признаться в чувствах, но он выбрал всех хёнов ❤️🥺 🌟🌟 потому что мы семья!!!
custom 540905852526975800416custom 533007788203733944712custom 540671004144727653010custom 53302630939120455896
Signed ¿
awww my precious jjangkyuz ❤️
custom 540671004144727653016custom 540905852526975800410custom 53300778820373394477custom 53302630939120455897
Signed ¿
Showing the 12 most recent of 13 posts we hold for @for_zhanghao. 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.
Citation-graph rank — 862,836 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“짱.zip” (@for_zhanghao), 331 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/for_zhanghao.
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.