Channel
@kyeomiouq
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
643subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002203459607 |
|---|---|
| Type | Channel |
| Username | @kyeomiouq |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/kyeomiouq |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 44% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 17:40 | 643 | +6 |
| 8 Sept 2026, 18:39 | 637 | -3 |
| 30 Aug 2026, 02:06 | 640 | -3 |
| 23 Aug 2026, 14:26 | 643 | -5 |
| 6 Aug 2026, 20:42 | 648 | no change |
| 6 Aug 2026, 19:51 | 648 | first reading |
14 posts held, back to 3 August 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 page of 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 14 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
373 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 31.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5282872570796861807 | 118 | 31.6% | |
| custom 5258041865915108646 | 82 | 22.0% | |
| custom 5258435989294057886 | 69 | 18.5% | |
| custom 5298562030494586300 | 65 | 17.4% | |
| custom 5235967726878488229 | 39 | 10.5% |
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 are Telegram’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 10 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 373 reactions 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 3 August 2026 to 6 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.
going REDRED like hot cheetos good hit like these channels 🤩 : boys : ✶ cortis : cortis 🤩 james 🤩 martin 🤩 seonghyeon 🤩 juhoon 🤩 keonho 🌟 seonghyeon 🤩 keonho 🤩 seonghyeon 🤩 juhoon 🌟 seonghyeon 🤩 keonho 🤩 ✶ txt : beomgyu & yeonjun 🤩 ✶ enhypen : jake 🤩 jake & sunghoon 🤩 sunoo & ni-ki 🤩 jakewon 🤩 sunoo & jake 🤩 jay & jake & sunghoon 🤩 sunoo & jay 🤩 jungwon & ni-ki 🤩 sunghoon & ni-ki 🤩 ✶ ald1 : sangwon 🤩 geonwoo 🤩 san…
ДОКЕМ С ДИНО 😋
custom 528287257079686180718custom 52985620304945863005custom 52584359892940578864custom 52359677268784882293custom 52580418659151086463
мои самые любимые люди 🫂
custom 525843598929405788622custom 52359677268784882297custom 52828725707968618076custom 52985620304945863005custom 52580418659151086461
▫️ : мы обещали друг другу ( что выберут красный шарик ) сынкван : пока гоинг севентин не закончится, мы будем называть этого человека мусором ( если он нарушит договор ) ▫️ : мусор это слишком.. ▫️ : морской ежик? морской огурец? вернон : пиявка? вернон : надеюсь, твои волосы выпадут? вау, но я правда думаю, что они могут выпасть… ▫️ : *обращается вернону* если ты выберешь синий, твои волосы выпадут
custom 525804186591510864617custom 52828725707968618075custom 52985620304945863005custom 52359677268784882293custom 52584359892940578863
Sticker, posted without a caption
джун : первый участник… это тот, кто вызовет восторг у любого, и это участник, который действительно использует свой мозг ▫️ : это так похоже на меня, неужели это я?? джун : это докем! минхао : ахх..но он не так уж и много использует свой мозг мингю : джун, ты веришь, что докем это тот, кто много использует свой мозг? ▫️ : я действительно много думаю головой *качает головой* 😭😭😭😭😭
custom 529856203049458630014custom 52828725707968618079custom 52584359892940578863custom 52359677268784882292custom 52580418659151086462
эх дурик мой любимый
custom 528287257079686180719custom 52584359892940578867custom 52985620304945863005custom 52359677268784882293custom 52580418659151086461
Sticker, posted without a caption
у бусоков выйдет новая песня под названием «one - spotify singles» дата выхода : 10 августа
custom 525843598929405788618custom 528287257079686180712custom 52580418659151086465custom 52985620304945863005custom 52359677268784882292
dokyeom and seungkwan’s message for T1 !! ▫️ : привет! сынкван : хорошо готовитесь к своему дебюту? ▫️ : но… вы ведь знаете ту дебютную песню, да? в итоге получилось так, что именно мы ее исполнили сынкван : так уж вышло. тогда увидимся на сцене homeground stage! пока!
custom 528287257079686180717custom 52359677268784882296custom 52580418659151086466custom 52985620304945863006custom 52584359892940578861
МОИ ХОРОШИЕ ☹️☹️
custom 525804186591510864621custom 528287257079686180711custom 52359677268784882298custom 52985620304945863006custom 52584359892940578862
🫳🏻🫳🏻🫳🏻
custom 528287257079686180718custom 525804186591510864610custom 52985620304945863009custom 52359677268784882293custom 52584359892940578862
Showing the 12 most recent of 14 posts we hold for @kyeomiouq. 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.
Named by 68 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@kyeomiouq named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“kyeomiou⟢” (@kyeomiouq), 643 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/kyeomiouq.
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.