Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐿𝑈𝑀𝐼𝑁𝑂𝑈𝑆

Channel

𝐿𝑈𝑀𝐼𝑁𝑂𝑈𝑆

@luminous_vir

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

44subscribers

-26 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003966958463
TypeChannel
Username@luminous_vir
Created14 July 2026 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live3 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/luminous_vir

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 29 September 2026 and assigned it the closest of 31 fixed categories, at 91% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

4470577 August 2026 — 70 subscribers10 August 2026 — 70 subscribers16 August 2026 — 61 subscribers24 August 2026 — 57 subscribers31 August 2026 — 55 subscribers10 September 2026 — 52 subscribers19 September 2026 — 47 subscribers3 October 2026 — 44 subscribers7 August 20263 October 2026
8 measurements spanning 57 days, net -26. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 40–74 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 08:1644-3
19 Sept 2026, 07:1747-5
10 Sept 2026, 12:1852-3
31 Aug 2026, 13:3355-2
24 Aug 2026, 03:2857-4
16 Aug 2026, 04:5461-9
10 Aug 2026, 00:0170no change
7 Aug 2026, 19:4070first reading

Engagement

15 posts held, back to 14 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 15 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

79 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 21.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53416996254536442621721.5%
custom 54566117331561578251721.5%
custom 53391103743544840171316.5%
custom 517036034908540250878.86%
custom 534159358271110768656.33%
custom 534858411872671804056.33%
🌚56.33%
👾45.06%
😈33.80%
🦄33.80%

Custom emoji. 6 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 are 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 7 of the 15 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 79 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 14 July 2026 to 5 August 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.

Recent posts

15 Jul 2026, 19:06 UTC277 views12 reactionsread 10 August 2026

Байден на троне.

custom 51703603490854025083custom 53391103743544840172custom 53416996254536442622custom 53485841187267180402custom 54566117331561578252custom 53415935827111076861

15 Jul 2026, 19:05 UTC277 views15 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 51703603490854025084custom 54566117331561578254custom 53415935827111076862custom 53416996254536442622custom 53485841187267180402custom 53391103743544840171

15 Jul 2026, 17:21 UTC265 views9 reactionsread 10 August 2026
Photo

ADMINISTRATION. Владелец — @grrrrr104 Владелец —@SW33TT1 Совладелец —@str4xx41m старший админ: ✅@aivalorens админы по чату: ❤️1. ❤️2. ❤️3. админы по активу: 🤩1. @mrrrrr_w 🤩2. 🤩3. админы по видео: 💕1. 💕2. админы по нью: 💜1. 💜2.

custom 53391103743544840173custom 54566117331561578253custom 53416996254536442622custom 53485841187267180401

15 Jul 2026, 16:59 UTCviews —

Channel name was changed to «Твоя Сука Меня Любит, Будто Клипы На ПорнХаб, Ну Конечно Же Ты Знаешь Каждый Трек, Но Не Фанат.»

15 Jul 2026, 16:56 UTC232 views8 reactionsread 10 August 2026

🤩🤩🤩🤩🤩🤩🤩🤩 NAVIGATION 🎀rules. 🎀administration. 🎀patent. 🎀chat.

custom 53416996254536442623custom 53415935827111076862custom 54566117331561578252custom 53391103743544840171

15 Jul 2026, 16:50 UTC229 views11 reactionsread 10 August 2026
Photo

👋для того, чтобы вступить в чат вам нужно: 📌прочитать правила. 📌подписаться на инфо. 📌подать заявку в чат.

custom 53416996254536442624custom 53391103743544840172custom 54566117331561578252🌚1🦄1😈1

15 Jul 2026, 16:44 UTC206 views12 reactionsread 10 August 2026
Photo

🧘прошу внимательно прочитать правила, чтобы в дальнейшем не влипать в неприятные ситуации.😋 👼1. контент 18+ (порно, расчлененка и т.п) — разрешен, но в меру. 👼2. реклама собственного блога или канала — только с разрешением главной администрации. 👼3. калл вызывать калл имеет право только администрация. участники обязаны будут спрашивать разрешения у главной администрации, иначе — пред. 👼4. политика обсуждение полит…

🌚3custom 53391103743544840172custom 53416996254536442622custom 54566117331561578252👾1🦄1😈1

Showing the 12 most recent of 15 posts we hold for @luminous_vir. 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.

Cite this entry

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 3 October 2026 — this entry's latest reading, not the date you are reading this.

“𝐿𝑈𝑀𝐼𝑁𝑂𝑈𝑆” (@luminous_vir), 44 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/luminous_vir.

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.