Property of @OFFICIALEUXOR
Channel
Keep Leuxor
@LXRSQ_OFC
On this record: Growth · Engagement · Posts · Citations · Cite this entry
6subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001966050513 |
|---|---|
| Type | Channel |
| Username | @LXRSQ_OFC |
| Created | 12 April 2023 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 12 September 2026 |
| On Telegram | t.me/LXRSQ_OFC |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 00:06 | 6 | +1 |
| 13 Aug 2026, 02:03 | 5 | no change |
| 6 Aug 2026, 22:16 | 5 | first reading |
Engagement
2 posts held, back to 12 April 2023 — 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 2 posts for this entry, the most recent from 12 April 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel created
Showing the 2 most recent of 2 posts we hold for @LXRSQ_OFC. 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.
Mentions
Named by 122 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@ghostelpatner · 33 postsRAINLINA EVENT ORGANIZER
@RAINLINAOFC · 443 postssᨣ̸ft 𝛎ɩ︩︪llꬰցꫀ
@angkringansoftvilagge · 152 posts𝐏𝐋𝐀𝐓𝐎𝐎𝐍 𝐎𝐅𝐂 | ROMBAK
@areaabn · 152 posts𝗠𝗔𝗥𝗞𝗬𝗘𝗡𝗜𝗩 𝗔𝗥𝗘𝗔 MEDPART
@MARKYENIVMP · 242 posts𝐒𝐐𝐔𝐀𝐃 𝕯𝐄𝐈𝐍𝐎𝐒🦖
@OfficialDeinos · 202 postsMPPS / PFP KOMPLEK GADIS
@patihrpw · 242 postsJKR
@pengirimanpakettRP · 3412 postsOPMEM - OFC RAVENOUS
@ravenousofc · 152 postsREXVENDER MPPS
@rexvendermpps · 652 postsBUBAR
@seindahsenyumanmu · 2292 posts𝐒𝐓𝐀𝐑𝐇𝐈𝐓𝐄𝐑
@STARHITEROFC · 292 postsStylooenxt.🧚🏻♀️
@stylooenxt · 622 posts𝐏𝐀𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐘𝐄𝐑𝐉𝐄𝐍𝐌𝐀𝐑𝐊
@yerjenmarkps · 22 postsbubar, unsubs aja
@KKJMCASTLE · 121 postmpps
@mppsarsipsltd · 11 postPS DRAVASTAR
@mppsdsr · 11 postVAKUM
@ofcyemarksung · 91 postKAWAN DESANAMJA
@OPICIKAWANDNJ · 51 postPARTNERSHIP LK
@partnershipLk · 31 postSKY PHOENIX [ HIATUS ]
@skyphoenixofc · 491 post$POOKHUIS MPPS
@spookyst · 61 post𝐓𝐀𝐄𝐍𝐍𝐈𝐄 𝐊𝐈𝐍𝐆𝐃𝐎𝐌
@TNNIKNGDM · 791 postWattana Partnership
@wattanapartner · 71 post
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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Keep Leuxor” (@LXRSQ_OFC), 6 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/LXRSQ_OFC.
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.