на самом деле, мне многого не надо: только переплести наши пальцы и видеть твою улыбку.
custom 5240295554969271053113custom 531026021144385362063custom 542289284256342895855custom 596988130164841415241

Channel
@hyunhoonly
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,941subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002189324576 |
|---|---|
| Type | Channel |
| Username | @hyunhoonly |
| Created | 10 June 2024 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/hyunhoonly |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 03:04 | 3,941 | +11 |
| 9 Aug 2026, 18:41 | 3,930 | -13 |
| 6 Aug 2026, 10:47 | 3,943 | no change |
| 6 Aug 2026, 10:03 | 3,943 | first reading |
14 posts held, back to 1 June 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 4 pagesof 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 4 August 2026 |
|---|---|
| Posts held | 14 (1 June 2026 – 4 August 2026) |
| Views total | 14,870 |
| Reactions total | 1,148 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 05:47 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 6 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.
3,430 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 32.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5969881301648414152 | 1,122 | 32.7% | |
| custom 5422892842563428958 | 742 | 21.6% | |
| custom 5310260211443853620 | 706 | 20.6% | |
| custom 5240295554969271053 | 592 | 17.3% | |
| custom 5422737107049277544 | 268 | 7.81% |
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 14 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 3,430reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 1 June 2026 to 4 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.
на самом деле, мне многого не надо: только переплести наши пальцы и видеть твою улыбку.
custom 5240295554969271053113custom 531026021144385362063custom 542289284256342895855custom 596988130164841415241
ㅤㅤㅤ ㅤ๑︎ㅤР О З Ы Г Р Ы Шㅤ๑︎ чтобы принять участие, необходимо выполнить ряд условий: 1. оформить подписку на указанные каналы: 1 2 3 4 2. сделать репост этой публикации в свой личный канал (если нет канала, то в любой чат/другу) 3. нажать на кнопку 'Участвую' призы: тг-премиум на 3 месяца, 3 кольца, 3 букета. ⏳ Подведение итогов: 20:00 22-08-2026 (Московское время) 🏆 Призовых мест: 7 👤
custom 531026021144385362017custom 52402955549692710536custom 54228928425634289585custom 59698813016484141523
отдай мне свою любовь, пока она не наполнит мои легкие. умоляю, я стою на коленях, я в твоей власти.
custom 531026021144385362080custom 596988130164841415264custom 524029555496927105351custom 542289284256342895831custom 542273710704927754413
Posted without readable text
custom 596988130164841415234custom 52402955549692710538
наша любовь намного интереснее, чем во всяких книгах и фильмах. она настоящая, живая.
custom 5969881301648414152110custom 542289284256342895862custom 531026021144385362052custom 542273710704927754423custom 524029555496927105316
я хочу быть твоим грехом, который ты будешь повторять снова и снова. я могу быть твоим проклятием или твоим спасением.
custom 5969881301648414152129custom 531026021144385362062custom 542273710704927754459custom 542289284256342895827custom 524029555496927105324
☺️астоящая 🥬🥬🥬🥬🥬🥬будет жить 🥬🥬🥬🥬🥬, даже если человек🥬🥬🥬🥬🥬. ☺️ этом и есть🥬🥬🥬🥬🥬 настоящих 🥬🥬🥬🥬🥬🥬.
custom 5969881301648414152102custom 524029555496927105358custom 542289284256342895854custom 531026021144385362032custom 542273710704927754418
это всегда будешь ты. ведь я встречал много людей, но никто не похож на тебя.
custom 5422737107049277544118custom 542289284256342895860custom 531026021144385362057custom 596988130164841415226custom 524029555496927105319
я отдал частичку своей души тебе, я был создан для тебя.
custom 5969881301648414152152custom 542289284256342895877custom 524029555496927105369custom 531026021144385362026custom 542273710704927754419
я — единственный, кто целует твои шрамы, тот ветер, что касается самых скрытых ран. стоит тебе закрыть глаза — я уже жду тебя внутри твоего сна. и каждую ночь ты возвращаешься, чтобы искать мой голос среди тишины, — ведь без него твои сны пусты, а я — единственный, кто их наполняет.
custom 5969881301648414152114custom 524029555496927105376custom 542289284256342895866custom 53102602114438536208custom 54227371070492775444
take it slow, put it down on me.
custom 5422892842563428958175custom 531026021144385362088custom 596988130164841415287custom 524029555496927105348custom 54227371070492775446
понимаешь, нам достаточно лишь надежды и любви. все остальное мы построим вместе.
custom 5310260211443853620105custom 542289284256342895863custom 596988130164841415248custom 524029555496927105335custom 54227371070492775443
Showing the 12 most recent of 14 posts we hold for @hyunhoonly. 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 — 249,958 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 4 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“влюбленные хенхо” (@hyunhoonly), 3,941 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/hyunhoonly.
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.