Channel
@deymonaarchive
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
12subscribers
+0 since we began measuring on 7 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004408089541 |
|---|---|
| Type | Channel |
| Username | @deymonaarchive |
| First recorded | 7 November 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/deymonaarchive |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 20:22 | 12 | no change |
| 7 Nov 2026, 20:22 | 12 | first reading |
19 posts held, back to 31 October 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 1 November 2026 |
|---|---|
| Posts held | 19 (31 October 2026 – 1 November 2026) |
| Views total | 104 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 20:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 1 video 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.
Telegram’s own ‘edited’ marker: 0 of 19 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🥚🥚🥚 🥚🥚🥚🥚🥚 ➖➖➖➖➖➖➖➖➖ c 01.11.2026 depraved flood и deymona flood заключили дружеский союз. надеемся, что союз продержится очень долго рады союзу!! ➖➖➖➖➖➖➖➖➖ @deparedinfo & @deymonainfo 💖💖💖
🔤🤩✖️𝐍ꫀׁׅw ძrꫀׁׅ𐐼ꪑ 𝐔ꪀ¡𐐫ꪀ⚫️🤩 𝕄ყ ℓ𐐫vꫀׁׅ f𐐫r ყ𐐫υ🔤🔤🔤 💭💭💭 🌟🌟🌟 🔤ɑׁׅℓwɑׁׅყs f𐐫rꫀׁׅvꫀׁׅr 🧁01.11🔤🔤🔤🔤🔤ℓꫀׁׅᧁׁꫀׁׅꪀძ𐐼rყ
На окраинах мёртвого-чёрно-сияющего моря, были замечены люди, которые держались за руки и со слезами на глазах, смотрели на блестящие-нежно-фиолетовые звёзды。 🔮 这... 새로운 조합 ! 💜🩷 私達は協力して嬉しいです。 #SWAG 🔮 @deymonainfo & @GLTRXFL
🤩🔹ew un𝕚𐐫n ! !🤩 T𐐫d𐐼y, y𐐫u 𐐼nd I ƨ𐐼t t𐐫getᲩer 𐐫ver 𐐼 cup 𐐫f c𐐫ffee.
💌ew 💌nion 🐾 ✨➿✨➿✨➿✨➿✨➿✨ 🎀𝗌ɛׅ𝗱 𝘁𐐫 𝗌𝘁𝗶𝗰︩︪𝗸 𝘁𐐫ɡɛׅ𝘁𝗵⃕ɛׅ𝗿 💜 𝘆𐐫𝘂'𝗿ɛׅ ⅿׅ𝘆 𝗯࡙ɛׅ𝗌𝘁 𝗳𝗿𝗶ɛׅ𝗻ׁ𝗱, 𝗜'𝗹𝗹 𝗹𐐫𝘃ɛׅ 𝘆𐐫𝘂 𝗳𐐫𝗿ɛׅ𝘃ɛׅ𝗿 💜 ✨➿✨➿✨➿✨➿✨➿✨ ᴘᴀды союзʏ!
🎬 ꒱ 𐌑ы ɯ᧘ᥙ ᥰ᧐ ᴛёⲙн᧐ᥔ у᧘ᥙцᥱ ᥴᥱу᧘ᥲ,ᥴᴛρᥲɯныᥱ ɯ᧐ρ᧐᥊ д᧐н᧐ᥴᥙᴛᥴя ᥴ᧐ ᥴᥰᥙны,ⲙы ᴛᥙ᥊᧐ ᧐δᥱρну᧘ᥲᥴь ᥙ уʙᥙдᥱ᧘ᥙ ᥙ᥊ 𑀝 ϶ᴛ᧐ᴦ᧐ ᥰρᥱκρᥲᥴн᧐ᴦ᧐ ⲙ᧐ⲙᥱнᴛᥲ @Slash_flood04 ᥙ @deymonainfo нᥲ᥊᧐дяᴛᥴя ʙ дρужᥱᥴκ᧐ᥱ ᥴ᧐юᤋу
На окраинах мёртвого-чёрно-сияющего моря, были замечены люди, которые держались за руки и со слезами на глазах, смотрели на блестящие-нежно-фиолетовые звёзды。 🔮 这... 새로운 조합 ! 💜🩷 私達は協力して嬉しいです。 #SWAG 🔮 @deymonainfo & @bloodd_floodd
На окраинах мёртвого-чёрно-сияющего моря, были замечены люди, которые держались за руки и со слезами на глазах, смотрели на блестящие-нежно-фиолетовые звёзды。 🔮 这... 새로운 조합 ! 💜🩷 私達は協力して嬉しいです。 #SWAG 🔮 @deymonainfo & @ZeinFlood
На окраинах мёртвого-чёрно-сияющего моря, были замечены люди, которые держались за руки и со слезами на глазах, смотрели на блестящие-нежно-фиолетовые звёзды。 🔮 这... 새로운 조합 ! 💜🩷 私達は協力して嬉しいです。 #SWAG 🔮 @deymonainfo & @hGXeyen2eKBczMDQ6
На окраинах мёртвого-чёрно-сияющего моря, были замечены люди, которые держались за руки и со слезами на глазах, смотрели на блестящие-нежно-фиолетовые звёзды。 🔮 这... 새로운 조합 ! 💜🩷 私達は協力して嬉しいです。 #SWAG 🔮 @deymonainfo & @LuminosityFlood
На окраинах мёртвого-чёрно-сияющего моря, были замечены люди, которые держались за руки и со слезами на глазах, смотрели на блестящие-нежно-фиолетовые звёзды。 🔮 这... 새로운 조합 ! 💜🩷 私達は協力して嬉しいです。 #SWAG 🔮 @deymonainfo & @demon1cus
На окраинах мёртвого-чёрно-сияющего моря, были замечены люди, которые держались за руки и со слезами на глазах, смотрели на блестящие-нежно-фиолетовые звёзды。 🔮 这... 새로운 조합 ! 💜🩷 私達は協力して嬉しいです。 #SWAG 🔮 @deymonainfo & @Idol_Flood67
Showing the 12 most recent of 19 posts we hold for @deymonaarchive. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“ժׁׅ݊ꫀׁׅܻ݊ᨮׁׅ֮ꩇׁׅ֪݊ᨵׁׅׅ݊ꪀɑׁׅ ܻ⨍ᥣׁׅ֪ᨵׁׅׅᨵׁׅׅժׁׅ݊ ɑׁׅꭈׁׅᝯׁ֒hׁׅ֮ꪱׁׁׁׁׅׅׅׅ᥎ׁׅꫀׁׅܻ݊ 🔮” (@deymonaarchive), 12 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/deymonaarchive.
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.