будет съеден через 3....2....
🍓15custom 580306152487650085812custom 58028937033243776448custom 58032732281094867997❤2💘2👻1

Channel
@sunghanbling
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
157subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003858408521 |
|---|---|
| Type | Channel |
| Username | @sunghanbling |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/sunghanbling |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 05:01 | 157 | -1 |
| 8 Aug 2026, 18:02 | 158 | no change |
| 8 Aug 2026, 09:00 | 158 | first reading |
17 posts held, back to 19 July 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 3 August 2026 |
|---|---|
| Posts held | 17 (19 July 2026 – 3 August 2026) |
| Views total | 2,293 |
| Reactions total | 720 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 18:02 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 12 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.
720 reactions across 17 posts, in 11 distinct kinds. The most used accounts for 20.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5800771864926101703 | 150 | 20.8% | |
| ❤ | 147 | 20.4% | |
| custom 5803273228109486799 | 139 | 19.3% | |
| custom 5803061524876500858 | 111 | 15.4% | |
| custom 5802893703324377644 | 62 | 8.61% | |
| 💘 | 45 | 6.25% | |
| 🍓 | 27 | 3.75% | |
| 😭 | 14 | 1.94% | |
| 👻 | 10 | 1.39% | |
| 💋 | 8 | 1.11% | |
| 👀 | 7 | 0.972% |
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 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 17 of the 17 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 720reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 19 July 2026 to 3 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.
будет съеден через 3....2....
🍓15custom 580306152487650085812custom 58028937033243776448custom 58032732281094867997❤2💘2👻1
🌟 : 5 часов записи..ing 🌟 : ㅋㅋㅋㅋㅋ у меня будто зависимость от этого фильтра 🌟 : это обычное лицо сон ханбинаа
custom 580306152487650085816custom 580327322810948679912custom 580289370332437764411❤5💘2👻1
🌟 : кванщим совсем во мне не кванщим* 🌟 : передо мной всегда только бори *собачку ханбина зовут кванщим, что буквально переводится как интерес 😭
custom 580077186492610170319custom 580327322810948679914😭11❤5custom 58030615248765008583💘2👻1
сегодня на фансайне акгэ рики & юджина пропустили сынона, хао и кюбина + кроме того, кто-то слил их номера в отеле, поэтому сейчас фаны эндабл пишут ребятам в баббле, предупреждая о том, что информация об отеле просочилась в интернет, и пытаются достучаться до йехва в твиттере, чтобы тот фанат больше не мог посещать мероприятия даблис! очень надеюсь, что они серьезно отнесутся к безопасности своих артистов :[ текст …
❤4
HE’S SO BAD 🌟
custom 580306152487650085819❤12custom 580077186492610170312custom 58032732281094867995👀1
просто WHATEVER 🌟
custom 580306152487650085816custom 58007718649261017039custom 58032732281094867997❤3🍓2👻1
ханбин рассказал, что потерял свой доступ к сертификату баристы 😭 🌟 : я думал что мне делать, поэтому написал им имейл 🌟 : было сложно получить сертификат, но весело, так что я подумываю о том, чтобы сделать это снова... надо бы заняться этим вопросом 🌟 : я написал им на почту и сказал: "я потерял свой айди и пароль", что я потерял свою лицензию и они мне ответили: "вы не можете потерять вашу лицензию".... я знаю...…
custom 580327322810948679916custom 580077186492610170311❤9🍓4custom 58030615248765008582👻1
ханбина попросили надеть очки наоборот...wth sure 🤩
custom 580327322810948679913❤8💘7custom 58007718649261017034custom 58030615248765008582🍓1👀1
ханбин будет одним из ведущих на AAA 2026 THIS IS NOT A DRILL 🌟🌟
❤17custom 580289370332437764415custom 580077186492610170310💋3💘2👀1😭1custom 58030615248765008581
🌟 : чжан хао, с днем рождения ( на кит. ) 🌟 : спасибо, что являешься таким огромным источником сил для меня. как старший мембер и лидер, тебе скорее всего пришлось пройти через многие сложности, особенно находясь в новых для себя условиях. в то же время, я также уверен, что ты смог отлично повеселиться. я просто надеюсь, что это было время, где твоему сердцу не было больно, и ты смог насладиться собой. я также надеюс…
💘17custom 580327322810948679912❤11💋4😭2custom 58007718649261017031custom 58030615248765008581
happiest birthday to uri jjang hao 🌟 though times might get hard, i believe that with the help by ur side that u already have, everything will seem just like another challenge rather than the end of the world </3 i hope u will continue to thrive in the future too 🌟
❤13💘8custom 58030615248765008587🍓5custom 58032732281094867993custom 58007718649261017032👻1💋1
see u at acon soon uri hamcee 🤍
custom 580077186492610170316custom 58030615248765008588custom 58032732281094867998❤6👻2💘1
Showing the 12 most recent of 17 posts we hold for @sunghanbling. 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 — 439,081 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.
Named by 2 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.
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.
“sunghan._.bling” (@sunghanbling), 157 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/sunghanbling.
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.