Telegram RegisterThe public register of Telegram

Channel

DLESQ MPPS

@DLEMPPS

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

6subscribers

+0 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-1001599495224
TypeChannel
Username@DLEMPPS
Descriptionconnect to @dlostempire
CreatedBetween 1 October 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/DLEMPPS

Growth

67 August 2026 — 6 subscribers12 August 2026 — 6 subscribers7 August 202612 August 2026
2 measurements spanning 6 days. 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 19:336no change
7 Aug 2026, 01:356first reading

Engagement

20 posts held, back to 27 May 2023the 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 8 September 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Links
1

Lifetime counters from Telegram’s own channel header, read 12 August 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

8 Sept 2023, 08:37 UTC201 viewsread 12 August 2026

page 12 1. 🐋 • 『 MARKOGANK 』 ‣ @MARKOGANK ‣ @mppsmpridebot ‣ active subunit 🐋 • 『 MARKOSUICY 』 ‣ @MARKOSUICY ‣ active subunit 🐋 • 『 𝗠ugen de Whiz 』 ‣ @MUGENWHIZ ‣ active 2. 🐋 • 『 OFC HASTARAJA』 ‣ @hastarajaofc ‣ @mppshastabot ‣ active 3. 🐋 • 『 𝗕𝗟𝗔𝗖𝗞 𝗥𝗔𝗜𝗗𝗘𝗥𝗦 』 ‣ @OFCLBLACKRAIDERS ‣ @Mppsbrd_bot ‣ active 4. 🐋 • 『 𝐎𝐅𝐂 𝐑𝐄𝐎𝐙𝐄𝐑 』 ‣ @reozerofcc ‣ @reozer

25 Aug 2023, 05:06 UTC162 viewsread 12 August 2026

page 11 1. 🐋 • 『 𝕰𝐗𝐈𝐋𝐄 𝐖𝐀𝐑𝐑𝐈𝐎𝐑 』 ‣ @OFCEXILEWARRIOR ‣ @EXRMPPSBOT ‣ ACTIVE 2. 🐋 • 『 𝖩𝖮𝖬𝖤𝖱𝖫𝖨𝖮𝖲 𝖧𝖨𝖦𝖧 𝖲𝖢𝖧𝖮𝖮𝖫 ⚓️ 』 ‣ @JOMERLIOSHIGHSCHOOL ‣ @mppsjmhsrobot ‣ active subunit 🐋 • 『 SHINKA HOSPITAL 』 ‣ @ShinkaHospitalOfc ‣ active subunit 🐋 • 『 ASTERISMOS SSTORE 』 ‣ @ASTERIMOSTORE ‣ active 3. 🐋 • 『 𝗥𝗔𝗚𝗙𝗢𝗥𝗧 𝗚𝗔𝗡𝗞 』 ‣ @RAGFORTGANK ‣ @MPPSRAGFORTGBOT ‣ active 4. 🐋 • 『

22 Aug 2023, 07:03 UTC121 viewsread 12 August 2026

page 10 1. 🐋 • 『 𝟭𝟯𝟵. 𝗞 - 𝗝𝗡𝗧𝗛𝗩 』 ‣ @KJNTHVOFC ‣ @PSJNTHVBOT ‣ active 2. 🐋 • 『 SEVEN SOUTH DREAM 』 ‣ @OFC7SOUTHDREAM ‣ @PARTNERRSSDBOT ‣ rombak 3. 🐋 • 『 𝐌𝐀𝐉𝐎𝐑𝐈𝐓𝐘 𝐋𝐔𝐗𝐔𝐑𝐘 𝐂𝐀𝐒𝐈𝐍𝐎』 ‣ @OFCMALUCA ‣ @mppsthecas_bot ‣ ACTIVE 4. 🐋 • 『 𝐎𝐅𝐂 𝐆𝐄𝐑𝐕𝐀𝐒𝐎 』 ‣ @ofcgervaso ‣ @mppsgervaso_bot ‣ active 5. 🐋 • 『 𝗥𝗔𝗩𝗜𝗦𝗣𝗔 𝗘𝗦𝗧 '𝟭𝟵 』 ‣ @RAVISPAROLEPLAYER ‣ @MPPSRAVISPA_BOT ‣ vaku

19 Jun 2023, 08:17 UTC208 viewsread 12 August 2026

page 09 1. 🐋 • 『 𝗨𝗡𝗜𝗩𝗘𝗥𝗦𝗘 𝗪𝗔𝗩𝗘 𝗔𝗥𝗨𝗧𝗔𝗟𝗔 』 ‣ @OFFICIALUVT ‣ @MITRAUVTBOT ‣ active 2. 🐋 • 『 𝐒𝐈𝐍𝐍𝐄𝐑 𝐀𝐑𝐄𝐀 』 ‣ @OFCSINNERAREA ‣ @SINNERPS_BOT ‣ active 3. 🐋 • 『 𝟐𝟑𝟏. 𝐉𝐎𝐔𝐑𝐍𝐀𝐋 𝐕𝐌𝐈𝐍𝐊𝐎𝐎𝐊 』 ‣ @OFCVMKRPW ‣ @vmkpartnerbot ‣ aktif 4. 🐋 • 『 𓄂𝕺𝐅𝐂. 𝕾𝐈𝐋𝐈𝐖𝐀𝐍𝐆𝐈 』 ‣ @ofc_siliwangi ‣ @siliwangimpps_bot ‣ aktif 5. 🐋 • 『 502-𝗡𝗘𝗢𝗗𝗥𝗜𝗩𝗘 𝗢𝗙𝗖 』 ‣ @NEODRIVEOFC ‣ @NDVMPPSBOT ‣ active

2 Jun 2023, 13:59 UTC202 viewsread 12 August 2026

page 08 1. 🐋 • 『 OFC RAMONDA 』 ‣ @OFCRAMONDA ‣ @RAMONMPPSBOT ‣ active 2. 🐋 • 『 𝐓𝐄𝐑𝐀𝐒𝐄𝐕𝐎𝐔𝐒 』 ‣ @TERASEVOUS ‣ @MPPSVOUSBOT ‣ active 3. 🐋 • 『NIFTY ORGANIZER』 ‣ @NIFTYORGANIZER ‣ @NIFTYEOPSBOT ‣ active 4. 🐋 • 『 𝕮𝐑𝐑𝐄𝐒𝐎𝐋𝐃 𝐎𝐅𝐂 』 ‣ @OFCRRESOLD ‣ @MPPSCRSBOT ‣ libur 5. 🐋 • 『 AUSARTA HOME 』 ‣ @AUSARTAHOME ‣ @AUSARTAPSBOT ‣ active 6. 🐋 • 『 Ø𝐅𝐂 𝐂𝐑𝐘𝐒𝐓𝐀𝐋 𝐋𝐈𝐎𝐍 』

29 May 2023, 01:57 UTC188 viewsread 12 August 2026

page 07 1. 🐋 • 『 𝗧𝗛𝗘 𝐉𝐎𝐑𝐋𝐄𝐘 』 ‣ @OFFICIALJORLEY ‣ @JORLEYPSROBOT ‣ vakum 2. 🐋 • 『 𝐓𝐇𝐄 𝐌𝐀𝐑𝐂𝐎𝐒 』 ‣ @THEMARCOSOFC ‣ @DMARCOSFRIENDSBOT ‣ aktif 3. 🐋 • 『 JJKW GLITZ 』 ‣ @JJKWGLITZ ‣ @TEMANJEJEKAWEBOT ‣ active 4. 🐋 • 『 𝐏𝐇𝐄𝐑𝐎𝐍𝐀𝐓𝐈𝐂』 ‣ @pheronatic ‣ @mppsphrbot ‣ active 5. 🐋 • 『 875. 𝐏𝐄𝐑𝐅𝐄𝐂𝐂𝐈𝐎𝐍 𝐁𝐀𝐍𝐆𝐓𝐀𝐍 』 ‣ @OFCPERFECCIONBANGTAN ‣ @MEDPARTPERFECCION_BOT ‣ active

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

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

“DLESQ MPPS” (@DLEMPPS), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/DLEMPPS.

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.