Channel
@mppsMegalos
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
4subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001632194426 |
|---|---|
| Type | Channel |
| Username | @mppsMegalos |
| Created | 7 May 2022 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mppsMegalos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 06:02 | 4 | no change |
| 10 Aug 2026, 22:48 | 4 | first reading |
19 posts held, back to 7 May 2022 — 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 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 19 posts for this entry, the most recent from 11 July 2022. An engagement rate over an empty window would be a number about nothing.
𝐌Σ𝐆𝐀𝐋𝐎𝐒 𝐆𝐀𝐍𝐆 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 ( page 7 ) ════ ⋆★⋆ ════ 01. 𝐒𝐔𝐆𝐀𝐑 𝐃𝐀𝐌𝐘 ➭ @OFCSUGARDAMY ➭ @SUGDAMMPPS_BOT Status : aktif 02. 𝐀𝐍𝐆𝐓𝐀𝐍 𝐒𝐐 ➭ @Abangtansq ➭ @ABSQPartnerbot Status : active 03. 𝗧𝗛𝗘 𝗕𝗘𝗥𝗚𝗜𝗡 ➭ @ofcbergin ➭ @tbgpartnerbot Status : active 04. 𝐎𝐅𝐂 𝐋𝐔𝐂𝐈𝐄𝐍 ➭ @OFCLUCIEN ➭ @MPPSLUCIEN2_BOT Status : active 05. SWIBE SCHOOL ➭ @SWIBEOFFICIAL …
𝐌Σ𝐆𝐀𝐋𝐎𝐒 𝐆𝐀𝐍𝐆 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 ( page 6 ) ════ ⋆★⋆ ════ 01. 𝗢𝗙𝗖 𝗕𝗟𝗔𝗖𝗞 𝗣𝗜𝗦𝗧𝗢𝗡 ➭ @ofcbiston ➭ @bistonmppsbot Status : aktif 02. 𝐄𝐋𝐘𝐗𝐈𝐎𝐍 𝐇𝐎𝐒𝐏𝐈𝐓𝐀𝐋 ➭ @ELYXIONHOSPITAL ➭ @elxpartner_bot Status : libur 03.𝐎𝐅𝐂 𝐁𝐀𝐍𝐃𝐀𝐑𝐋𝐀𝐗 ➭@ofcbandarlax ➭@bandarlaxmpps_bot Status : aktif 04. VARGAS GANK ➭ @vargasgank ➭ @mppsvargasbot Status : aktif 05. #𝗖𝟮𝟳 - 𝐂ETERWAUL…
Sticker, posted without a caption
𝐌Σ𝐆𝐀𝐋𝐎𝐒 𝐆𝐀𝐍𝐆 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 ( page 5 ) ════ ⋆★⋆ ════ 01. ➭ ➭ Status : 02. VIGOROUS SQ ➭ @OFCVIGOROUSS ➭ @mppsvigorousbot Status : ACTIVE 03. 𝐊𝐈𝐍𝐆 𝐗𝐋𝐄𝐕𝐄𝐍𝐎𝐒 ➭ @ofckingxlevenos ➭ @mppsxlevenosbot Status : ACTIVE 04. ⎙ OFC STREET RIDERS ➭@OFCSTREETRIDERS ➭@MPPS001BOT Status : ACTIVE 05. 𝐁𝐀𝐍𝐃𝐈𝐃𝐎𝐒 ➭@officialbandidos ➭@psbandidbot Status …
Sticker, posted without a caption
𝐌Σ𝐆𝐀𝐋𝐎𝐒 𝐆𝐀𝐍𝐆 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 ( page 4 ) ════ ⋆★⋆ ════ 01. ➭ ➭ Status : 02. 𝐗EVANOS 𝐆ANK ➭ @Officialxevanos ➭ @XevanosGankMpps_bot Status : libur 03. 𝗔𝗥𝗘𝗔 𝗝𝗝𝗞𝗪 ➭ @AREAJJKW ➭ @TEMANJEJEKAWEBOT Status : aktif 04. 𝗖𝗔𝗠𝗢𝗥𝗥𝗔 𝗣𝗥𝗢𝗠𝗢𝗧𝗘 ➭ @CamorraPromote ➭ @CamorraMppsBot Status : aktif 05. Æ𝗩𝗘𝗡𝗭𝗬𝗧 ➭ @AEVENZYT ➭ @PSAVT_BOT Status : aktif 06. …
Sticker, posted without a caption
𝐌Σ𝐆𝐀𝐋𝐎𝐒 𝐆𝐀𝐍𝐆 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 ( page 3 ) ════ ⋆★⋆ ════ 01. OFC WÖNKERS ➭ @ofcwonkers ➭ @wonkersmppsbot Status : active 02. 𝗗𝗘𝗔𝗗𝗠ØØ𝗥 𝟲𝟵#𝗢𝗙𝗖 ➭ @OFCDEADMOOR69 ➭ @deadmoormppsbot Status : active 03. 𝟵𝟮𝟯 𝗢𝗙𝗖 𝗖𝗔𝗥𝗕𝗟𝗜𝗦 ➭ @ofcarblis ➭ @carblismppsbot Status : active 04. 𝐙𝐎𝕰𝕶𝐄𝐑 ➭ @Zoekercom ➭ @zoekerami_robot Status : active 05. GOTHEM COMEDY BAR ➭ …
Sticker, posted without a caption
𝐌Σ𝐆𝐀𝐋𝐎𝐒 𝐆𝐀𝐍𝐆 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 ( page 2 ) ════ ⋆★⋆ ════ 01. ➭ ➭ Status : 02. 𝐎𝐅𝐂 𝐓𝐈𝐆𝐑𝐄𝐕𝐈𝐎𝐍𝐒 ➭ @OFCTIGREVIONS ➭ @TRVSPARTNERBOT Status : ACTIVE 03. 𝐃𝐄𝐀𝐓𝐇 𝐒𝐂𝐑𝐄𝐀𝐌 ➭ @OFCDEATHSCREAM ➭ @dscvxnpsbot Status : active sub unit ➭ VLAXION GANK 🏴 ➭ @OFCVLAXION 04. ➭ ➭ Status : sub unit ➭ ➭ 05. ｢𝐍⛦︎︎𝐄𝐒𝐇𝐘𝐕𝐄𝐋𝐓｣ ➭ @NAESHYVELTOFC ➭ @NSVTPSB…
Sticker, posted without a caption
𝐌𝐄𝐆Á𝐋𝐎𝐒 𝐆𝐀𝐍𝐊 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 ( page 1 ) ════ ⋆★⋆ ════ O1. OFC 𝐖AG𝐒EX ➭ @OFCWAGSEX ➭ @mppswgx_bot Status : ACTIVE O2. 𝗖Ø𝗥𝗩𝗨𝗦 ➭ @OFCCORVUS ➭ @corvusmppsbot Status : aktif O3. 275 OFC MATADOR ➭ @OFCMATADOR ➭ @MPPS275_BOT Status : active O4. 957. 𝐎𝐅𝐂 𝐊𝐓𝐀𝐄𝐑𝐎𝐒 𝐂𝐋𝐔𝐁 ➭ @OFCKTAEROSCL ➭ @MPPSHBKTRSBOT Status : active Sub Unit ➭ 495. 𝐇𝐎𝐌𝐄𝐁𝐀𝐒𝐄 𝐊𝐓𝐇 ➭ @O…
Showing the 12 most recent of 19 posts we hold for @mppsMegalos. 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.
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.
@mppsMegalos named 52 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
2 more handles are in this same list but not shown individually here — capped at 50.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“MPPS MÈGALOS.” (@mppsMegalos), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/mppsMegalos.
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.