"BLOOD SAGA" in Busan LD вот такие картули ещё в Пусане🤏🏼
custom 53597790884226935671

Channel
@catwonarch
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
228subscribers
+21 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002220261010 |
|---|---|
| Type | Channel |
| Username | @catwonarch |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/catwonarch |
Memes & entertainment — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 |
|---|---|---|
| 25 Sept 2026, 00:37 | 228 | -1 |
| 12 Sept 2026, 04:21 | 229 | +3 |
| 28 Aug 2026, 10:24 | 226 | +1 |
| 21 Aug 2026, 00:22 | 225 | +13 |
| 14 Aug 2026, 00:46 | 212 | +5 |
| 7 Aug 2026, 03:47 | 207 | no change |
| 6 Aug 2026, 21:32 | 207 | first reading |
10 posts held, back to 6 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 10 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
87 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 46.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5256200536125893628 | 40 | 46.0% | |
| custom 5465339278500320008 | 18 | 20.7% | |
| custom 5390989894208204200 | 15 | 17.2% | |
| custom 5359779088422693567 | 14 | 16.1% |
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 10 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 87 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 6 August 2026 to 7 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.
"BLOOD SAGA" in Busan LD вот такие картули ещё в Пусане🤏🏼
custom 53597790884226935671
возник спор ㅎㅎ дракула и вампир это одно и тоже или разные существа как вы думаете, котики? ㅋㅋㅋ 🦮: Это Дракула. Он другой 🐈⬛: Нет, такой же 🐈: Нет-нет, он другой 🦊: Точно, он другой 🍙: Он... он всё-таки другой 🐈⬛: Словно вампир-аристократ... 🐈: Эй, тут можно поспорить 🐈⬛: О, правда? 👀 🦮: Да, он совсем другой
custom 52562005361258936283custom 53597790884226935671custom 54653392785003200081
ENHYPEN расставляют вампиров по степени стильности — от самых стильных до наименее стильных ребятам нужно было составить рейтинг от самых стильных вампиров до менее стильных. чонвон выбрал эдварда на второе место 🤧 🐈: "Сумерки". Я большой фанат "Сумерек" 👤: Ты за Эдварда или за Джейкоба, Чонвон? 🐈: Э-э... за Эдварда (◝‿◜。) 🦊: И я, и я!! 👤: Тут все — за Эдварда? 🦮: Нет, мнения разделились... но я не хочу об этом гов…
custom 53597790884226935672custom 52562005361258936281custom 54653392785003200081
продолжаем котики❤️🩹🫂
custom 52562005361258936285
давайте поддержим нашего любимого макнэ в этот сложный период 🫂 и чтобы избежать спама, напишите в посте теплые слова любви и поддержки ❤️🩹 как говорится, приятное с полезным 🥲 WITH LOVE TO NI-KI #WithNI_KIForever #NI_KI #니키 @enhypen @ENHYPEN_members
custom 525620053612589362813custom 53909898942082042003custom 54653392785003200083
у ребят даже выходили тик токи вместе 🥺🤏🏼
custom 52562005361258936288custom 53909898942082042006custom 54653392785003200085
Во время недавнего участия в программе IDDP (1theK), Джинхёк из NOWZ рассказал, что они с Чонвоном дружат еще с начальной школы и оба занимались тхэквондо. Он также поделился тем, что его мама показала фотографию Чонвона команде по кастингу агентства BIGHIT, благодаря чему тот и попал в компанию 🥹 (мама Джихёка, спасибо 🙏🏼) 🐈: Мама одного моего друга, который был стажером BIGHIT MUSIC, показала мое фото команде по к…
custom 53597790884226935675custom 52562005361258936282custom 54653392785003200081
⟡ ﹙ weverse dm ﹚ 2020.12.31 Энджин😍 Всем привет~ Вчера и сегодня было очень холодно~!! Не забудьте тепло одеваться!!❣❣ #weverseDM
custom 53597790884226935675custom 53909898942082042003custom 54653392785003200083
⟡ ﹙ weverse dm ﹚ 2020.12.29 Ребята ~ Уже через два дня закончится 2020 год. Есть ли среди вас, энджин😍, те, кто уже придумал планы или цели на Новый год?? + Время Чонвона #weverseDM
custom 52562005361258936284custom 53909898942082042003custom 54653392785003200081
⟡ ﹙ weverse dm ﹚ 2020.12.27 Сегодня я весь белый, прямо как снеговик ㅎㅎ А этого снеговика мы сделали с моей старшей сестрой ещё в детстве. 🤩 (Ммм… Что бы сегодня поесть на ужин?..) #weverseDM
custom 52562005361258936284custom 54653392785003200083
Showing the 10 most recent of 10 posts we hold for @catwonarch. 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.
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.
@catwonarch 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.
References a handle that is not a live channel — we have no record it ever was one.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐝𝐞𝐚𝐫 𝐣𝐮𝐧𝐠𝐰𝐨𝐧” (@catwonarch), 228 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/catwonarch.
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.