Telegram RegisterThe public register of Telegram
Telegram profile photo for Lumosel Remastred

Channel

Lumosel Remastred

@Lumosel

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Cite this entry

6,457subscribers

+1,364 since we began measuring on 6 September 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1004290300011
TypeChannel
Username@Lumosel
Description@Lumoselsupp_bot
CreatedBetween 1 May 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 September 2026
Last confirmed live16 November 2026
Measurements held19
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/Lumosel

Topic

Ecommerce storefront — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 28% 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 the other topics.

Growth

5,0936,7215,9076 September 2026 — 5,093 subscribers6 September 2026 — 5,093 subscribers9 September 2026 — 5,758 subscribers13 September 2026 — 6,650 subscribers17 September 2026 — 6,721 subscribers25 September 2026 — 6,674 subscribers4 October 2026 — 6,631 subscribers11 October 2026 — 6,587 subscribers15 October 2026 — 6,552 subscribers18 October 2026 — 6,519 subscribers21 October 2026 — 6,522 subscribers24 October 2026 — 6,543 subscribers27 October 2026 — 6,549 subscribers29 October 2026 — 6,511 subscribers1 November 2026 — 6,497 subscribers4 November 2026 — 6,482 subscribers7 November 2026 — 6,494 subscribers10 November 2026 — 6,485 subscribers16 November 2026 — 6,457 subscribers6,4576 September 202616 November 2026
19 measurements spanning 71 days, net +1,364. 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 4,849–6,965 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 06:346,457-28
10 Nov 2026, 16:216,485-9
7 Nov 2026, 13:516,494+12
4 Nov 2026, 07:386,482-15
1 Nov 2026, 08:266,497-14
29 Oct 2026, 18:386,511-38
27 Oct 2026, 02:206,549+6
24 Oct 2026, 01:376,543+21
21 Oct 2026, 09:386,522+3
18 Oct 2026, 11:376,519-33
15 Oct 2026, 08:086,552-35
11 Oct 2026, 20:426,587-44
4 Oct 2026, 21:586,631-43
25 Sept 2026, 09:376,674-47
17 Sept 2026, 01:196,721+71
13 Sept 2026, 02:396,650+892
9 Sept 2026, 13:185,758+665
6 Sept 2026, 18:225,093no change
6 Sept 2026, 17:475,093first reading

Engagement

43 posts held, back to 6 August 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 13 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.7%
avg views ÷ 6,457 subscribers
Avg views / post
1,210
10 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
10
of 43 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 November 2026
Posts held43 (6 August 2026 – 18 November 2026)
Views total12,090
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 21:24 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.

What this channel posts

Photos
51
Links
26

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 10 posts held from the last 30 days (20.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).

18 Nov 2026, 13:28 UTC164 viewsread 18 November 2026
Photo

Lumosel Exclusive Offer A new 35% discount is now available across Lumosel! Use promo code WELCOME35 at checkout to claim your discount. Take advantage of this limited promotional offer and enjoy premium AI API access at an even better price. Start saving today: https://lumosel.vip/dashboard/payments

15 Nov 2026, 17:49 UTC474 viewsread 18 November 2026

A limited number of Unlimited API slots are now available. Interested? Contact us directly: @lumoselsupport

15 Nov 2026, 13:17 UTC591 viewsread 18 November 2026
Photo

Uncensored AI models are now available! Contact @adbknife to purchase access.

14 Nov 2026, 18:45 UTC701 viewsread 18 November 2026
Photo

Paid API Is online! https://lumosel.vip/dashboard/payments

31 Oct 2026, 23:15 UTC≈1,730 viewsread 18 November 2026

Maintenance is expected to be completed by tomorrow. We're currently experiencing an issue with our hosting datacenter, and our team is working to resolve it as soon as possible. We apologize for the inconvenience and appreciate your patience and understanding.

29 Oct 2026, 22:21 UTC≈1,710 viewsread 18 November 2026

We are currently looking for promoters and VT/YouTube creators to collaborate with Lumosel. We offer attractive plans and benefits in exchange for promotion and content creation. @lumoselsupport

28 Oct 2026, 14:21 UTC≈1,700 viewsread 18 November 2026

A 30% discount is now available on Lumosel — use code REMASTRE30 at checkout: https://lumosel.vip/dashboard/payments

26 Oct 2026, 23:23 UTC≈1,480 viewsread 18 November 2026
Photo

Card payments are now live on Lumosel, with support for multiple new payment methods for a smoother and more convenient checkout experience! https://lumosel.vip/dashboard/payments

16 Oct 2026, 20:07 UTC≈2,310 viewsread 18 November 2026
Photo

All 502 errors have been eliminated, and the gateway is running smoothly since yesterday update.

15 Oct 2026, 22:28 UTC≈2,120 viewsread 18 November 2026

Card payments are temporarily unavailable due to an issue with our payment gateway. We’re working on integrating Stripe within the next 3 days, alongside UPI payments to provide more convenient payment options.

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

Posts recorded as deleted after publishing

We recorded 1 post on @Lumosel as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
16 November 2026
Most recent seen missing
16 November 2026
Median time before seen missing
8 days
Seen missing in the last 30 days
1

Mentions

Named by 1 registered channel — 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.

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.

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

“Lumosel Remastred” (@Lumosel), 6,457 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/Lumosel.

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.