Telegram RegisterThe public register of Telegram

Channel

archiewd.com

@archiewdym

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

23subscribers

+0 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002258738130
TypeChannel
Username@archiewdym
Created21 April 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/archiewdym

Growth

239 August 2026 — 23 subscribers11 August 2026 — 23 subscribers9 August 202611 August 2026
2 measurements spanning 2 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 22–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 12:0323no change
9 Aug 2026, 05:4723first reading

Engagement

12 posts held, back to 21 April 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 28 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Videos
3
Links
7

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
4m 54s
Average length
1m 38s

Measured directly from 3 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.

Reaction mix

68 reactions across 11 posts, in 15 distinct kinds. The most used accounts for 29.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘2029.4%
1217.6%
🥰710.3%
💩57.35%
🔥57.35%
🙏34.41%
🤮34.41%
22.94%
❤‍🔥22.94%
🎅22.94%
👍22.94%
🖕22.94%
🌚11.47%
💯11.47%
😁11.47%

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 11 of the 12 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 68reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 21 April 2025 to 28 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Dec 2025, 12:02 UTC138 views2 reactionsread 11 August 2026
Forwarded from @pjkamikoPhoto

• Kiss the Villain - MORE MORE JUMP! | Russian cover by KAMIKO! • ➥ TAP!(⁠。⁠•‌⁠ᴗ⁠-⁠)⁠✧ ★ В ролях: • КАЙТО — taekeo • Ханасато Минори — a1rin • Киритани Харука — Osanemi • Момои Айри — AKU • Хиномори Шизуку — lyuri ♪ Работа над кавером: Обложка - Vakesha Текст - Archie & linnetty Монтаж - Bux-ANKA & a1rin Тюн, Разбор гармоний, Оформление, Сведение - a1rin  |•| Оригинал - Kiss the Villain Приятного просмотра, и на

2

13 Nov 2025, 22:24 UTC207 views5 reactionsread 11 August 2026
Video

🎈Torinoko City - ray of hope #HatsuneMikuColorfulStage VA: linnetty 🔘 Tækeo 🔘 Арчи 🔘 Иорихана (замена) 🔘 Перевод: Арчи Работа со звуком: Najisa & linnetty Работа над видео: Tækeo

3🥰1😁1

18 Sept 2025, 15:00 UTC316 views7 reactionsread 11 August 2026
Forwarded from @pjkamikoPhoto

• 「1」 - Leo/Need | Russian cover by KAMIKO! • ➥ TAP!(⁠。⁠•‌⁠ᴗ⁠-⁠)⁠✧ ★ В ролях: • Мегурине Лука - Шейден • Хошино Ичика - teririn • Тенма Саки - YUI • Мочизуки Хонами - Донна • Хиномори Шихо - FlaiPi ♪ Работа над кавером: Обложка - Vakesha Текст - Archie Монтаж, Оформление - plush hope Тюн, Сведение, Разбор гармоний - a1rin  |•| Оригинал - 「1」 Приятного просмотра, и надеемся на вашу активность!😉 › Буст! #Каве

❤‍🔥2🔥2💘1💩1🥰1

22 Jul 2025, 14:06 UTC457 views4 reactionsread 11 August 2026
Forwarded from @ringoprojectVideo

🍎 Поприветствуем актёра озвучки Аояги Тойя - Арчи! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Обложка: Дохи ✰ Перевод: Рей

💘2💩2

17 Jul 2025, 11:21 UTC370 views4 reactionsread 11 August 2026
Forwarded from @nightvision_prVideo

«Действительно ли это та жизнь, о которой я мечтала?» 🤩 Поприветствуем нашу Хиномори Шизуку! 🤩 (💙) . ⁺ 。💙 @.. . 🦢 Для вас работали: ➿ВА: linnetty 🤍 ➿Монтаж: Rimrin ➿Перевод: Daani ➿Оформление: Мефронк ➿Работа со звуком: linnetty (тюн) ➿ Арчи (сведение) 💙 Уже в нашем TikTok - Хочешь попасть в нашу команду или связаться с нами? Пиши в наш бот! 🤩 #Приветствие #Кавер #MMJ

🌚1🔥1🥰1🙏1

29 Jun 2025, 14:22 UTC410 views9 reactionsread 11 August 2026
Forwarded from @nightvision_prPhoto

С днем рождения, Арчи!💙 (💙) . ⁺ 。💙 @.. . 🦢 Сегодня просим поздравить нашего замечательного тюнера с одним из важных дней в его жизни. Автор баннера: Батон (💙) . ⁺ 。💙 @.. . 🦢 #Стафф #ДеньРождения

4💘2🔥2👍1

27 Apr 2025, 14:02 UTC688 views13 reactionsread 11 August 2026
Forwarded from @pjkamikoPhoto

• ECHO - Vivid BAD SQUAD | Russian cover by KAMIKO! • ➥ TAP!(⁠。⁠•‌⁠ᴗ⁠-⁠)⁠✧ ★ В ролях: • Мегурине Лука - Шейден • Азусава Кохане - doku • Шираиши Ан - Delikora • Шинономе Акито - Juan Pérez • Аояги Тойя - Archie ♪ Работа над кавером: Обложка, Оформление, Разбор гармоний - Archie Текст - Archie & linnetty Монтаж - Kay Kondo Аранжировка - Delikora Тюн - a1rin Сведение - Najisa & a1rin  |•| Оригинал - ECHO Пр

💘72👍1💯1🥰1🙏1

21 Apr 2025, 11:20 UTC729 views13 reactionsread 11 August 2026

Привет👋 Здесь будет репостнуто почти всё что связано со мной

💘7🥰32🙏1

Showing the 12 most recent of 12 posts we hold for @archiewdym. 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

Citation-graph rank — 1,104,175 of 1,189,255entries 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.

Forward network

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.

Mentions

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.

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“archiewd.com” (@archiewdym), 23 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/archiewdym.

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.