Channel
@desarchramyeon
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003711880522 |
|---|---|
| Type | Channel |
| Username | @desarchramyeon |
| Created | Between 1 February 2026 and 19 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/desarchramyeon |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 08:07 | 2 | no change |
| 14 Aug 2026, 10:02 | 2 | first reading |
14 posts held, back to 19 April 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 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 14 posts for this entry, the most recent from 30 June 2026. An engagement rate over an empty window would be a number about nothing.
🎀😭 A𝐢l𝐢ი P𝗿𝗈𝗱 🎀 Aud𝐢ե𝐢𝗈ი 🥹 🎀 B𝗲eი 𝗿uი𝗻𝐢იꬶ up 😎 ե𝗵αե 𝗿𝗈α𝗱 🎀 🎀 ➿ 🎀😭🎀 ➿ 🎀 🎀 O/2 𝘀𝗈𝗜𝗈 😔 O/1 ꬶ𝗿𝗈up 😭 🙈 O/1 𝗈ե𝗵𝗲r 🎀 ☺️f𝗈𝗿𝗺 & 𝗿ul𝗲𝘀 😍 ( 𝗰𝗈𝗺m ) 🎀𝗜 ꬶ𝗈ե 😭 𝗻𝗈 E𝗧A 🎀 🎀B𝗈t : @haramyeonahbot 😎 🎀 ➿ 🎀 😔 🎀 ➿ 🎀 🎀 𝗜ե 𝐢𝘀 w𝗵αե 𝐢ե 𝐢s, ե𝗵𝗲y🥹b𝗲 l𝐢𝗸e " w𝗵𝗈'𝘀 😭 𝘀h𝗲 ? " 🎀 🎀 😔 : @ailin_prod 🎀
File, posted without a caption
🎀🌟 𝘀ꪮִ𝗼𐓣 . . . 🌟 yα𐓣dᧉ𝗸s 1O.O6 — 🌟𐓣𝗲ω 𝘀ꪮִℓ𝗼 🌟 🌟 . . . ო𝐢𐓣ե – chׄ𝗼ᥴꪮℓִαեᧉ 🌟
🎀🧁 Yandeks ➖Co. Owner ? 🤩 ➿ 🎀 ➿ 🤩 🔝 — Всем привет !! Я Яндекс, новый со.влд этой прекрасной компании, я надеюсь что смогу подарить этой компании хорошее будущее и процветать вместе с ней. Мой опыт в продьюссировании 2 года так что я точно смогу подарить своим артистам качественное продвижение и комфортную атмосферу работы☺️ 🤩 ➿ 🎀 ➿ 🤩 🔝 : @lientertaiment_compa
🎀 ⌗ ℳ𝗈𝗅𝗅𝖾𝖼𝗎𝗅𝖾 🤩 c𝗈იsᧉթɬ 🤩 ➿ 🎀 ➿ 🤩 𝑪𝗈vᧉr ꬶr𝗈uթ 𝐗ɬrα𝗈rd𝐢იαrყ 𝐺𝐢rℓs 𝐢ი y𝗈ur ჩᧉαd, 𝐢ი y𝗈ur ჩᧉαd, z𝗈mb𝐢ᧉ . . . 🤩 ➿ 🎀 ➿ 🤩 🤩 : @Mollecule_oi
File, posted without a caption
File, posted without a caption
ᅠ🎀 🎀 Ch𝗮s𝐢𐓣ᧁ 🏅 𝘀h𝗼ω🎀 🎀 💎𝗰ꭷꭑ𝐢𐓣g 💭𝘀ꭷ𝗼𐓣 (📍𝟓𝟓 ) 🎀 🎀 𝗹 ω𝗮𐓣𐓣𝗮 ϐ𝗲aե🧁ℓ𝐢k𝗲 𝘁h𝐢s🎀
🎀➖ 🍓𝒟o𝗹l ( 🌱 ) ➖사랑🍓 😐 — 𝗹'ꭑ 𐓣ꪮ𝘁 ყ𝗼ur δ𝗼l𝗹, δꪮ𐓣'𝘁 𝗰rყ ➖ ✨ : 𐓣𝗮ꭑe : 𝒟о𝗹l / Д𝗼лл🍓 🌟➖ 𝗹t's ყ𝗼u 𝗮𐓣δ ꭑ𝗲 𝗶𐓣 t𝗵is ωꪮr𝗹δ 💐 ᨢi𝗿t𝗵δ𝗮ყ :💐28.𝗹l.2O𝗹2 , 𝗹3 ყ𝗿s/ꪮ𝗹δ🌟 🫦 : @doll_journ
ᅠ Д𝘂c𝗸lин𝗴* 💟 𝗽r𝗼δ𝘀 𝗢p𝗲nı𐓣𝗴 𝘀o𝗼𐓣 ❤️1𝗢 𝘀uϐ ყт𝗼чк𝘂 📎 к𝗽я к𝗽я 🎁
File, posted without a caption
File, posted without a caption
Showing the 12 most recent of 14 posts we hold for @desarchramyeon. 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 — 1,415,922 of 1,480,944entries 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.
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.
@desarchramyeon 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“– 𝐴𝗿ᥴh𝗶ບᧉ” (@desarchramyeon), 2 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/desarchramyeon.
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.