Channel
@LUM3Nll
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
53subscribers
-13 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003890692788 |
|---|---|
| Type | Channel |
| Username | @LUM3Nll |
| Created | Between 1 February 2026 and 23 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/LUM3Nll |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 08:58 | 53 | -4 |
| 8 Sept 2026, 11:20 | 57 | -2 |
| 30 Aug 2026, 16:58 | 59 | -4 |
| 16 Aug 2026, 19:44 | 63 | -2 |
| 10 Aug 2026, 02:46 | 65 | no change |
| 9 Aug 2026, 02:01 | 65 | -1 |
| 8 Aug 2026, 08:33 | 66 | first reading |
16 posts held, back to 23 July 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 16 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
8 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5242371145159705712 | 4 | 50.0% | |
| 👻 | 4 | 50.0% |
Custom emoji. One row above is a 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 count beside it is Telegram’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 3 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 8 reactions 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 23 July 2026 to 28 July 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.
Дорогие союзники,увы,но со всеми разрыв из-за закрытия флуда.этот флуд был дорогим для участников и администрации,но все когда нибудь заканчивается.всем хорошего дня. #lumenRP
👻4
Signed ~ 𝐖𝐢𝐧𝐝𝐲! | #bestwindy31
Поздравляю вас!❤️
Signed ~ 𝐖𝐢𝐧𝐝𝐲! | #bestwindy31 #𝑰𝑵𝑭𝑷 #𝐘𝐌
🔤nfected нуждᴀᴇᴛᴄя ʙ дᴩужᴇᴄᴋих ᴄᴏюɜᴀх !! макс пдп 8:8 / мин 2:2 папки рп / вз писать @kkkkkkejdueoqlam ; @tellazx #RPinfectedׄ ᅠ𓈒 ׁ ︶︶ִ︶︶︶ ୨ 🌸 ୧ ︶ׄ︶ִ︶︶︶. 𝅄
Signed 𝙉𝙞𝙠𝙨~
Нас 150! #д᧘яᥴ᧐юɜ᧐ʙ
Signed 𝙉𝙞𝙠𝙨~
Союзники и не только наши союзники, прошу вас дайте союзов этому инфо: Your.Start.flood буду очень благодарна вам за это, владелец тоже будет рад. #д᧘яᥴ᧐юɜ᧐ʙ
Signed 𝙉𝙞𝙠𝙨~
Нам нужны такие роли как: фрея майкалсон камилла джози зальцман лиззи зальцман джексон кеннер тристан марсель жерар Также мы ищем союзы. По поводу вступления и союзов писать: @Xdxinf #для_союзов
Signed ~ 𝐖𝐢𝐧𝐝𝐲! | #bestwindy31 #𝑰𝑵𝑭𝑷 #𝐘𝐌
🕯️ɱы ɞ ησυсκϱ τακσύ α∂ɱυʜυсτραʯυυ κακ.. ➿➿➿➿➿🧥ɱσʜταжёρ 🧛α∂ɱυʜ ησ ɥατƴ➿➿➿➿ 🤩 ησ ησɞσ∂ƴ ∂σⲗжʜσсτυ ηυсατь::@cainatrix / @PA3L0JEH1E_HA_AT0Mbl
Signed ~ 𝐖𝐢𝐧𝐝𝐲! | #bestwindy31 #𝑰𝑵𝑭𝑷 #𝐘𝐌
🌟ɱы ɞ ησυсκϱ ƴɥαсτʜυκσɞ ➿➿ρσⲗυ κρ🌍ρσⲗυ сχс➿➿ 🍷ɞсτƴηυτь:: @Siideria_bot
Signed ~ 𝐖𝐢𝐧𝐝𝐲! | #bestwindy31 #𝑰𝑵𝑭𝑷 #𝐘𝐌
➿➿ⲙы ɞ η૦υςκ૯ ς૦юਡ૦ɞ➿➿ 🌹🌹🌹🌹 (ηραɞυⲗα сσюʒσɞ) ➿➿➿🌍мαкѕ. 6:6➿➿➿ 🖤ηυсατь: @PA3L0JEH1E_HA_AT0Mbl / @cainatrix
Signed ~ 𝐖𝐢𝐧𝐝𝐲! | #bestwindy31 #𝑰𝑵𝑭𝑷 #𝐘𝐌
🌟🌟🌟 #𝑵𝒆𝒘𝑽𝒊𝒅𝒆𝒐 🌟🌟🌟 🤩 🔹𝐫𝐞𝐚𝐭𝐞𝐝 𝐛𝐲 🤩 𝐋𝐀𝐍𝐄 🥹🥹 🥹🥹 | 𝐢𝐝 : 𝐧𝐨𝐭 𝐨𝐮𝐫𝐬 🎁 🥹 ཿ 𝅄 ۫ ᰈ 𝒕𝒊𝒌𝒕𝒐𝒌 𝒍𝒊𝒏𝒌 🥹🌟🥹 🌟 ୭ৎ Будем рады если 🪽 поставите реакции! ୭ৎ 🌟
Signed 𝙉𝙞𝙠𝙨~
Это уже как рптайм какой то,ну да ладно😁
Signed ~ 𝐖𝐢𝐧𝐝𝐲! | #bestwindy31 #𝑰𝑵𝑭𝑷 #𝐘𝐌
❤︎ СОЮЗОВ МНЕЕЕ ❤︎ •Папки: вз/рп •Максимальная подписка: 3х3 •Название: 𝑷𝒐𝒊𝒔𝒐𝒏 (P.s: в лс сразу,помимо вашего инфо,напишите с кого пост о заключении союза,выберите папку и подписку) Писать: @ylpiik #сзрп
Signed 𝙉𝙞𝙠𝙨~
Showing the 12 most recent of 16 posts we hold for @LUM3Nll. 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.
Named by 3 registered channels — 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“𓊆ྀི🤍𓊇ྀི⟡. 𝑳𝑼𝑴ꈼ𝑵 ♯𝑰𝓃𝒻𝑜 ༒︎” (@LUM3Nll), 53 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/LUM3Nll.
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.