Telegram RegisterThe public register of Telegram

Channel

MPPS LEVIEOSTRIX

@mppslvx

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

3subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1001567203743
TypeChannel
Username@mppslvx
CreatedBetween 1 August 2021 and 16 February 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live15 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/mppslvx

Growth

314 Aug 2026, 13:17 — 3 subscribers15 Aug 2026, 01:26 — 3 subscribers14 Aug 2026, 13:1715 Aug 2026, 01:26
2 measurements taken within a single day. 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 01:263no change
14 Aug 2026, 13:173first reading

Engagement

20 posts held, back to 16 February 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 20 posts for this entry, the most recent from 7 March 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

1 Mar 2022, 03:07 UTC121 viewsread 14 August 2026

MPPS LEVIEOSTRIX: Page ∅18 [ Partnership LVX ] 01. user ch : bot yang aktif : status ch : A 02. user ch : bot yang aktif : status ch : A 03. user ch : bot yang aktif : status ch : A 04. user ch : bot yang aktif : status ch : A 05. user ch : bot yang aktif : status ch : A 06. user ch : bot yang aktif : status ch : A 07. user ch : bot yang aktif : status ch : A 08. user ch : bot yang aktif : status ch : A 09.

1 Mar 2022, 03:06 UTC78 viewsread 14 August 2026

Page ∅17 [ Partnership LVX ] 01.𝗢𝗙𝗖 𝗢𝗙𝗖 𝗦𝗨𝗚𝗔𝗥 𝗕𝗢𝗬𝗦 user ch :@ofcsugarboys bot yang aktif : @kantorsboysbot status ch : A SUB UNIT 𝗙𝗘𝗜𝗦𝗧𝗬𝗙𝗘𝗠𝗔𝗟𝗘𝗦 user ch : @feistyfemales 02.PRANVERE ORGANIZER user ch : @PRANVEREEO bot yang aktif : @PRANVEREPSBOT status ch : A 03. COSSANDO user ch : @COSSANDO bot yang aktif : @SOCIETYCOSBOT status ch : A 04. user ch : bot yang aktif : status ch : A 05. user ch : bot yang aktif :

1 Mar 2022, 03:06 UTC55 viewsread 14 August 2026

Page ∅16 [ Partnership LVX ] 01.𝐎𝐅𝐂 𝐃𝐑𝐄𝐗𝐀𝐆𝐎𝐙 𝐊𝐈𝐋𝐋𝐄𝐑 user ch :@ofcdrexagozkiller bot yang aktif : @drexagozmppsbot status ch : A 02.RAPLINE user ch : @OFCRAPLINE bot yang aktif : @RAPHYBEPSBOT status ch : A 03. 𝐂𝐘𝐁𝐄𝐑𝐒𝐏𝐀𝐂𝐄 user ch : @ofcyberspace bot yang aktif : @ofcyberspace status ch : A 04. 𝐓𝐇𝐄 𝐕𝐈𝐍꒞𝐔𝐋𝐀 𝐎𝐅𝐂 user ch : @VINCULAOFC bot yang aktif :@vincula_medpartbot status ch : A 05. 𝐒𝐄𝐑𝐈𝐊𝐀𝐓 𝐊𝐓𝐇 user ch : @sirkt

17 Feb 2022, 08:57 UTC98 viewsread 14 August 2026

MPPS LEVIEOSTRIX: Page ∅15 [ Partnership LVX ] 01. 𝗡𝗘Ⓞ︎𝗭𝗬𝗣𝗔 𝗖𝗔𝗦𝗧𝗟𝗘!? user ch : @NEOZYPACASTLE bot yang aktif : @nzpcmpps_bot status ch : A 02. 𝐃𝐀𝐆𝐑𝐎𝐔𝐙 𝐆𝐀𝐍𝐊 user ch : @ofcdagrouz bot yang aktif : @Mppsdgxbot status ch : A 03. MOLISE DEMIGODS user ch : @molisedemigods bot yang aktif :@psmolisedmgbot status ch : A 04. 𝐅𝐀𝐋𝐃𝐄𝐑𝐒 𝟐𝟐𝟒 user ch : @FALDERS224 bot yang aktif :@FaldersPartner_bot status ch : A 05. BASECAMPK

17 Feb 2022, 08:57 UTC66 viewsread 14 August 2026

MPPS LEVIEOSTRIX: Page ∅14 [ Partnership LVX ] 01. OFFICIAL CALENDARIA user ch :@OFCCALENDARIA bot yang aktif : @mppscalendaria_bot status ch : A SUB UNIT CALENDARIA MENFESS user ch : @calendariamenfess 02. STR∆NGΣRS PROMOTΣ user ch : @OFCSTRANGERSPM bot yang aktif :@strangerspsbot status ch : A 03.𖥔 ִֶָ 🪐 𝗧𝗥𝗘𝗜𝗭𝗢𝗡𝗔𝗧𝗫𝗬 ˖࣪⁩ user ch : @TREIZONATXY bot yang aktif : @treizonatxymppsbot status ch : A 04. 𝐌egáclite use

17 Feb 2022, 08:57 UTC51 viewsread 14 August 2026

MPPS LEVIEOSTRIX: Page ∅13 [ Partnership LVX ] 01. OFC DRAKIOS user ch : @OFCDRAKIOS bot yang aktif : @dksmpps_bot status ch : A 02. NCTEZ user ch : @NCTEZ bot yang aktif :@nctezps_bot status ch : A 03. OFC𝐅𝐑𝐎𝐍𝐓𝐀𝐋𝐈𝐒𝐓𝐄𝐑ftl🇻🇮 user ch : @OFCFTL bot yang aktif :@MppsFrontalstr_bot status ch : A 04. 𝐎𝐅𝐂 𝐖𝐀𝐍𝐓𝐄𝐃 user ch : @wantedofc bot yang aktif :@mppswanted_bot status ch : A 05. 𝐎𝐅𝐂 𝐃𝐑𝐄𝐗𝐀𝐆𝐎𝐙 𝐊𝐈𝐋𝐋𝐄𝐑 user ch : @ofcdr

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

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

“MPPS LEVIEOSTRIX” (@mppslvx), 3 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/mppslvx.

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.