💋➖ольшое спасибо за добавление в краш лист!! 😍
custom 52426799790780860723

Channel
@Moonlux_0
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
89subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002767754092 |
|---|---|
| Type | Channel |
| Username | @Moonlux_0 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/Moonlux_0 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 00:37 | 89 | -2 |
| 9 Aug 2026, 14:02 | 91 | no change |
| 7 Aug 2026, 18:54 | 91 | first reading |
16 posts held, back to 26 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 16 posts for this entry, the most recent from 3 May 2026. An engagement rate over an empty window would be a number about nothing.
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.
95 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 31.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5239941842937608222 | 30 | 31.6% | |
| ❤ | 25 | 26.3% | |
| 💯 | 14 | 14.7% | |
| custom 5242679979078086072 | 12 | 12.6% | |
| 🍓 | 11 | 11.6% | |
| 🤡 | 2 | 2.11% | |
| 💔 | 1 | 1.05% |
Custom emoji. 2 of the rows above are 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 areTelegram’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 11 of the 16 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 95reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 26 April 2026 to 3 May 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.
💋➖ольшое спасибо за добавление в краш лист!! 😍
custom 52426799790780860723
😁😆😁 🅱️ы᥈𐐫ⲿυⲧь ⲕ𝕒ⲃᥱρ 𐔤ɥ𝕒ᥴⲧⲏυц 😍
custom 52399418429376082222❤1
«🐉»🅰️ел𝕦 ⲏⲁ к𝕒мбэк 💎 15 комм* 30 рк* 500 пм* 🤩🎀🎀🎀🎀🎀🎀🎀🤩 🍭#𝕄σ𐐫ηℓ𝕦𝐱 🔠#𝗢𝗠𝗚 ⭐
custom 52399418429376082223🍓1
..«💋». - 🩸𐐫ⲙⲉ𝔟a𝕔𝕜 🍭 ყ𝐨u ᥴᥲ𝗻 ᥉ᥙbⲙιt ᥲᥒ 💎ᥲρρᥣ𝐢ᥴᥲ𝐭ι𝗻 " 𝗗𝗨𝗢 𝗖𝗢𝗩𝗘𝗥" 𝐢ᥒ th𝐞 tⳋᥴ'᥉ r𝐞ⳋι᥉𝐭r𐔤 🤚 🎀¡ 𝗣𝗜𝗡𝗞 𝗩𝗘𝗡𝗢𝗠 ¡🎀 🫀 «🤩────୨ৎ────🤩» 🔝Mꫀɱ𝗯ꫀɾ𝕤:: ☆ 🅱️𝗶𝗹𝗹𝗶𝗲&🩸𝗶𝗮 🧸 #𝕄σ𐐫ηℓ𝕦𝐱 ᶜᵒᵐᵉᵇᵃᶜᵏ #𝗗𝗨𝗢 ⭐
❤5custom 52399418429376082225custom 52426799790780860722
File, posted without a caption
Sticker, posted without a caption
➖➖➖➖➖
Sticker, posted without a caption
..«💎»🅱️ᥴ𝕖𝗺 ⲇ𝕠ⳝ𝕡𐔖𝗲 𐔤ⲧ𝕡𝗲ɥⲕ𝕠 ⭐
💯2custom 52399418429376082222
Sticker, posted without a caption
Video message, posted without a caption
❤5custom 52426799790780860723custom 52399418429376082222🤡1
Sticker, posted without a caption
🍓4❤3💯3custom 52399418429376082222
Showing the 12 most recent of 16 posts we hold for @Moonlux_0. 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.
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.
“❤️- 𝕄σ𐐫ηℓ𝕦𝐱 ᵒⁱ 🖤” (@Moonlux_0), 89 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Moonlux_0.
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.