MOONLUME GACOR๐ฅ๐ฅ๐ฅ
โค3โคโ๐ฅ1

Channel
@moonlumme
On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Citations ยท Cite this entry
126subscribers
-3 since we began measuring on 11 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1003439572124 |
|---|---|
| Type | Channel |
| Username | @moonlumme |
| Created | Between 1 November 2025 and 24 February 2026 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 26 August 2026 |
| On Telegram | t.me/moonlumme |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Aug 2026, 12:14 | 126 | -3 |
| 11 Aug 2026, 17:12 | 129 | no change |
| 11 Aug 2026, 15:45 | 129 | first reading |
8 posts held, back to 24 February 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 8 posts for this entry, the most recent from 2 April 2026. An engagement rate over an empty window would be a number about nothing.
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.
50 reactions across 8 posts, in 9 distinct kinds. The most used accounts for 36.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 18 | 36.0% | |
| ๐ฅ | 11 | 22.0% | |
| โคโ๐ฅ | 6 | 12.0% | |
| ๐ฅฐ | 4 | 8.00% | |
| ๐ | 3 | 6.00% | |
| ๐ | 3 | 6.00% | |
| ๐ | 2 | 4.00% | |
| ๐พ | 2 | 4.00% | |
| ๐คฉ | 1 | 2.00% |
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 8 of the 8 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 50 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 8 most recent posts we hold, published 24 February 2026 to 2 April 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.
MOONLUME GACOR๐ฅ๐ฅ๐ฅ
โค3โคโ๐ฅ1
๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐๐ฅ๐ฅ๐ฅ
โคโ๐ฅ2๐2๐พ2๐1๐ฅ1
๐๐๐๐๐๐ ๐๐๐๐ ๐ข๐๐๐ ๐๐ ๐๐๐๐๐๐ ๐๐๐ ๐๐ ๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐๐ ๐๐๐๐๐๐๐ ๐ฅkllik disini ๐ฅkllik disini
โคโ๐ฅ3๐2๐ฅ2
IZIN TAMPILL ๐ฅ CLICK HERE ๐ฅ CLICK HERE
โค6๐ฅฐ4๐ฅ2๐คฉ1
๐ฅ ๐ฎ๐จ๐ฉ๐ผ๐ป๐จ๐ต ๐ท๐ฌ๐น๐ซ๐จ๐ต๐จ ๐ด๐ถ๐ถ๐ต๐ณ๐ผ๐ด๐ฌ ๐ฟ ๐ฉ๐ผ ๐ญ๐ถ ๐ฒ๐ฐ๐ป๐จ, ๐บ๐ฐ๐จ๐ท๐จ ๐ณ๐จ๐ฎ๐ฐ ๐ฒ๐จ๐ณ๐ถ ๐ฉ๐ผ๐ฒ๐จ๐ต ๐ช๐ฐ๐ต ๐จ๐ด๐ถ๐น๐ป๐จ ๐ฅ๐
โค7๐3๐ฅ2
File, posted without a caption
๐ฅ2
File, posted without a caption
๐ฅ2
๐ง๐ฒ๐ฟ๐๐ฒ๐ฟ๐ฎ๐ต ๐ถ๐ป๐๐ถ๐ป๐๐ฎ ๐บ๐ผ๐ผ๐ป๐น๐๐บ๐ฒ ๐ด๐๐ฎ ๐ด๐ฎ๐ฐ๐ผ๐ฟ๐ฅ๐ฅ๐ฅ๐ฅ๐ฅ๐ฅ๐ฅ๐ฅ๐ฅ
โค2
Showing the 8 most recent of 8 posts we hold for @moonlumme. 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 โ 859,055 of 1,629,452 entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 18 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐โ (@moonlumme), 126 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/moonlumme.
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.