Channel
@zzundoxxy
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
76subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002360882493 |
|---|---|
| Type | Channel |
| Username | @zzundoxxy |
| Description | all about lee junhyuk from polarix ( ex mirae ) фьючер : @intoourfuture_mirae анон : @zzundoxxy_bot вп : @sangphire |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/zzundoxxy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 21:02 | 76 | no change |
| 8 Aug 2026, 17:15 | 76 | first reading |
16 posts held, back to 2 December 2025 — 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 16 posts for this entry, the most recent from 12 February 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 5 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.
207 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 27.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5233593516201884119 | 57 | 27.5% | |
| custom 5434003321662747899 | 56 | 27.1% | |
| custom 5434101457370493543 | 52 | 25.1% | |
| custom 5228820291412583149 | 42 | 20.3% |
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 14 of the 16 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 207reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 2 December 2025 to 12 February 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.
джун станцевал под новый релиз ateez — adrenaline, и уже успел заслужить лайк от уёна ❤️ #junstagram
custom 54341014573704935437custom 52288202914125831494custom 52335935162018841194custom 54340033216627478994
▫️джун и донхва только что всего пару минут были на совместном эфире в инсте 😭
custom 543400332166274789910custom 54341014573704935435custom 52288202914125831493custom 52335935162018841191
🤩 : « здравствуйте, ребята. вот и еще один год подошел к концу. каким был для вас 2025 ? думаю, в нем было и много хороших, и много трудных моментов. но хотя бы сейчас я хочу, чтобы вы отпустили все плохие воспоминания и надолго сохранили в сердце только счастливые моменты. спасибо вам огромное за то, что дошли до этого момента и были со мной до самого конца. я не знаю, какие события ждут нас в следующем году, но мы …
custom 52335935162018841196custom 54341014573704935434custom 52288202914125831493custom 54340033216627478991
Sticker, posted without a caption
звездочки ⭐️ с новым годом ! спасибо каждому из вас за то, что остаетесь с нами и продолжаете интересоваться жизнью мирэшек, даже спустя больше года после распада.. для нас это невероятно ценно и тепло — видеть, что фьючер все еще живет благодаря всем нам, нау, которые так любят ребят 💙 пусть в новом году будет больше радостных новостей, вдохновения, тепла и поводов улыбаться ! надеемся, вы и дальше будете с нами —…
custom 54340033216627478996custom 52335935162018841192custom 54341014573704935432custom 52288202914125831491
🤩 : « счастливого рождества » #junstagram
custom 54341014573704935437custom 52288202914125831494custom 52335935162018841193custom 54340033216627478992
▫️ 🤩 : « чем занимаетесь ~ ? раз уж зима, надо сменить тему на эту 💙 во сколько обычно ложитесь спать ?? у меня каждый день по-разному TMI : если засыпать под bgm майнкрафт, спится хорошо чтобы посмотреть ответы на это, нужно закрыть инст и заново открыть, только тогда видно – неудобно доброй ночи, я еще загляну ~ спокойной ночи 🫶🫶 не обращай внимания на людей вокруг, которые несут всякую ерунду !!!!! я всегда буду т…
custom 52335935162018841196custom 54341014573704935435custom 52288202914125831494custom 54340033216627478991
и кто такой прелестный у нас ? #tiktok
custom 52288202914125831496custom 54340033216627478994custom 52335935162018841193custom 54341014573704935433
БЫСТРО ловите поцелуйчик от джунека ! 🥰 #junstagram
custom 52335935162018841199custom 54340033216627478994custom 54341014573704935433custom 52288202914125831492
🤩 : « впервые за долгое время обесцветил волосы » #junstagram
custom 52335935162018841196custom 54340033216627478993custom 54341014573704935433custom 52288202914125831491
джунджун вернул блонд, и в корее выпал снег 🍑 #tiktok
custom 54340033216627478999custom 52288202914125831494custom 54341014573704935434custom 52335935162018841192
@zzundoxxy
custom 52335935162018841194custom 52288202914125831492custom 54341014573704935432custom 54340033216627478991
Showing the 12 most recent of 16 posts we hold for @zzundoxxy. 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 — 335,907 of 1,480,688entries 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.
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 1 registered channel — 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“⋆ ˚｡ zzundoxy 𖦹 ⋆｡°” (@zzundoxxy), 76 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/zzundoxxy.
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.