︎ ︎ ︎︎ ︎︎ _ / ᚚ ઽ᥆. ‘ . 𝕜ᥱᥱƿ ⿻ | ㋍ : ᥴ𝖆ᥣꪑ : ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ꫂ ; ꫝ᥆ᥒ𝔢ɣ \ ♱ , ‹ 𝕀'ო𝖆 ིྀ . 𝕊𝕥ıᥴ𝕜 ( 𑜸 ) 𝒶𝕣ꪮυ𐓣ᦔ :

Channel
ārhiv Нƴυn Wōōƙ
@arhivHyunWook
On this record: Topic · Growth · Engagement · Posts · Cite this entry
9subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003563147103 |
|---|---|
| Type | Channel |
| Username | @arhivHyunWook |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/arhivHyunWook |
Topic
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 2 October 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 19:17 | 9 | -2 |
| 25 Sept 2026, 15:57 | 11 | -1 |
| 14 Sept 2026, 01:37 | 12 | +1 |
| 7 Sept 2026, 03:21 | 11 | +1 |
| 29 Aug 2026, 23:35 | 10 | +1 |
| 22 Aug 2026, 17:18 | 9 | -3 |
| 14 Aug 2026, 17:16 | 12 | -1 |
| 12 Aug 2026, 03:30 | 13 | no change |
| 7 Aug 2026, 19:38 | 13 | first reading |
Engagement
6 posts held, back to 11 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 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 6 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
︎ ︎ ︎︎ ︎︎ _ / ᚚ i'ო. ‘ . ꪗ᥆υ𝕣 𝕷 | ㍱ : 𝔙ıgg𝖊აt : ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ ︎ ︎ ︎︎ ︎︎ㅤㅤㅤㅤㅤㅤㅤ ︎ ︎ ︎︎ ︎︎ ꫂ ; f𝖆n \ ⿻ , ‹ i'lꪶ . ᠻσlᥣ᥆᭙ ( 𑜸 ) ყꪮu :
Sticker, posted without a caption
︎ ︎ ︎︎ ︎ ︎_ 🤩⤸.ೃ࿐ 🤩 𝒞aught ᯓ in🤩 𝒜 ⤸. ` ℬeautiful 🤩!¡ 🤩;; 🤩 𝒟ream 🤩≠ 🤩 ~ ࿓ ࿔ ~ 🤩 ° 23O412 𖦹 𓈒 ❤️❤️ 𝒰pd - 🪦 ; 🤩 𝒰 nder © ;; 🤩% ⊂⊃ ✖️
Sticker, posted without a caption
🤩 .. ౄ ℑᥲκᥱ ' վ च - 🐶 « ࿔ — 🐈 ઽoⲙꫀ ≈ 🌟 ‘ 𝓞f 🌟🌟 — ぉ ^ ✆ ≈ 🌟🌟 ” 𝒯ꫝꪱs 😎 ⋮ - I’ᥣᥣ ७ ‘ 𝒞αᥣm 🤍 **
Showing the 6 most recent of 6 posts we hold for @arhivHyunWook. 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.
Cite this entry
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“ārhiv Нƴυn Wōōƙ” (@arhivHyunWook), 9 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/arhivHyunWook.
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.