Telegram RegisterThe public register of Telegram

Channel

DATA MPPS DELTAFORCE

@deltaforcempps

On this record: Growth · Engagement · Posts · Citations · Cite this entry

3subscribers

+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-1001466178498
TypeChannel
Username@deltaforcempps
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/deltaforcempps

Growth

37 August 2026 — 3 subscribers13 August 2026 — 3 subscribers7 August 202613 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:173no change
7 Aug 2026, 06:433first reading

Engagement

20 posts held, back to 9 June 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 15 June 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

15 Jun 2022, 01:35 UTC131 viewsread 13 August 2026

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ 𝗣𝗔𝗥𝗡𝗘𝗥𝗦𝗛𝗜𝗣 𝗣𝗔𝗚𝗘 𝟏𝟓 ◈ ━━━━━━ ⸙ ━━━━━━ ◈ ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ◈ ━━━━━━ ⸙ ━━━━━━ ◈

15 Jun 2022, 01:35 UTC85 viewsread 13 August 2026

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ 𝗣𝗔𝗥𝗡𝗘𝗥𝗦𝗛𝗜𝗣 𝗣𝗔𝗚𝗘 𝟏𝟒 ◈ ━━━━━━ ⸙ ━━━━━━ ◈ ➤ 𝗭𝗢𝗫𝗥𝗜𝗗𝗘𝗥𝗦 (active) ╰► @ofczoxriders ╰► @mppszoxridersbot ➤ 𝗝𝗔𝗘𝗥𝗢𝗦𝗘 𝐂𝗘𝗡₮𝗨𝗥𝗬 (active) ╰► @JAEROSECENTURY ╰► @CENTURYPSBOT ➤ 𖥸 𝕭𝐋𝐎𝐎𝐃𝐒 𝐍 𝕮𝐑𝐈𝐏𝐒 (active) ╰► @OFCBLOODSANDCRIPS ╰► @BLOODSANDCRIPSMPPSBOT ➤ 𝗚𝗘𝗔𝗥𝗭𝗘𝗫 (active) ╰► @OFCGEARZEX ╰► @PSGEARZEXBOT ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ➤ ╰► ╰► ◈ ━━━━━━ ⸙ ━━━━━━ ◈

15 Jun 2022, 01:34 UTC70 viewsread 13 August 2026

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ 𝗣𝗔𝗥𝗡𝗘𝗥𝗦𝗛𝗜𝗣 𝗣𝗔𝗚𝗘 𝟏𝟑 ◈ ━━━━━━ ⸙ ━━━━━━ ◈ ➤ 𝐂𝐀𝐒𝐓𝐑𝐔𝐌𝐕𝐊𝐎𝐎𝐊 (active) ╰► @CASTRUMVKOOK ╰► @dcvskmppsbot SU ❱ ✧𝐃𝐄𝐂𝐑𝐈𝐌𝐒 𝐉𝐄𝐍𝐊𝐎𝐎𝐊𝐕✦ ╰► @OFCDECRIMSJENKOOKV ➤ SERENDIPITY EVENT ORGANIZER (active) ╰► @SERENDIPITYEO ╰► @PSMPSERENDIPITYBOT SU ❱✧SERENDIPITY HOSPITAL✦ ╰►@SERENDIPITYHOSPITAL ❱✧SERENDIPITY NATIONAL UNIVERSITY✦ ╰► @SERENDIPITYUNIVERSITY ❱ ✧SERENDIPITY SALON✦

15 Jun 2022, 01:34 UTC58 viewsread 13 August 2026

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ 𝗣𝗔𝗥𝗡𝗘𝗥𝗦𝗛𝗜𝗣 𝗣𝗔𝗚𝗘 𝟏𝟐 ◈ ━━━━━━ ⸙ ━━━━━━ ◈ ➤ 𝐎𝐅𝐂 Désmond (active) ╰► @OFCDESMOND ╰► @MppsDesmond_bot ➤ 𝗩𝗘𝗥𝗟𝗔𝗚𝗢𝗦 𝗨𝗡𝗜𝗧𝗘𝗗 (active) ╰► @verlagosunitedsq ╰► @mppsvgu_bot ➤ ✶. 𝐎FFICIAL 𝐉ENVKOOK (active) ╰► @OFCJENVKOOK ╰► @RELASIJVKBOT ➤ 𝐑𝐄𝐕𝐎𝐋𝐈𝐂 (active) ╰► @REVOLICSQ ╰► @MPPSREVOLICBOT ➤ ÉBLOUIR CASTLE (active) ╰► @EBLOUIRCASTLE ╰► @EBLOUIRPARTNERBOT ➤ 𝗢𝗙𝗖 𝗫𝗧𝗥𝗔𝗬𝗭𝗘𝗥 (active) ╰► @XTRAYZEROFC ╰► @XTRAYZ

15 Jun 2022, 01:33 UTC54 viewsread 13 August 2026

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ 𝗣𝗔𝗥𝗡𝗘𝗥𝗦𝗛𝗜𝗣 𝗣𝗔𝗚𝗘 𝟏𝟏 ◈ ━━━━━━ ⸙ ━━━━━━ ◈ ➤ 𝗢𝗙𝗖 𝗘𝗔𝗚𝗟𝗘 𝗨𝗡𝗜𝗧𝗘𝗗 (active) ╰► @OFCEAGLEUNITED ╰► @mppseglbot ➤ #𝗖𝟮𝟳 - 𝐂ETERWAULING (active) ╰► @OFCCETERWAULING ╰► @mpctwbot ➤ LEGEND CASINO (active) ╰► @LCST300 ╰► @BARTANDERLC_BOT ➤ RADEXAS OFFICIAL (rombak) ╰► @OFCRADEXAS ╰► @mppsradexas_bot ➤ 𝐎𝐅𝐂 𝐉𝐀𝐍𝐆𝐆𝐀𝐋𝐀 (active) ╰► @OFCJANGGALA ╰► @PSJANGGALABOT ➤ 174. D'LOST EMPIRE (active) ╰► @DLOSTEMPIRE ╰► @M

13 Jun 2022, 01:26 UTC61 viewsread 13 August 2026

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ 𝗣𝗔𝗥𝗡𝗘𝗥𝗦𝗛𝗜𝗣 𝗣𝗔𝗚𝗘 𝟏𝟎 ◈ ━━━━━━ ⸙ ━━━━━━ ◈ ➤ 𝗠𝗔𝗘𝗦𝗧𝗥𝗢 𝗝𝗘𝗞★𝗧𝗘𝗛𝗔 (active) ╰► @MAESTROJEKATEHA ╰► @MPPSMJKBOT ➤ VZENZAERO (active) ╰► @ofcvzenzaero ╰► @psvzzrrobot ➤ 𝕭ELAMOUR, 𝗧𝗛𝗘 𝗛𝗢𝗧𝗘𝗟. (active) ╰► @BELAMOURHOTEL ╰► @PARTNERBLMRBOT SU ❱ ✧𝗧𝗛𝗘 𝗖𝗢𝗡𝗧𝗜𝗡𝗘𝗡𝗧𝗔𝗟 𝗕𝗔𝗥✦ ╰► @thecontinentalbar ➤ TREAESPA OFC (active) ╰► @TREAESPAOFC ╰► @TREAEMPSBOT ➤ 𝐒𝐀𝐈𝐍𝐒𝐁𝐔𝐑𝐘'𝐒 𝐀𝐂𝐀𝐃𝐄𝐌𝐘 (active) ╰► @SBAOFC ╰► @Sainsburysmp

Showing the 12 most recent of 20 posts we hold for @deltaforcempps. 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 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“DATA MPPS DELTAFORCE” (@deltaforcempps), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/deltaforcempps.

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.