Telegram RegisterThe public register of Telegram

Channel

DATA MPPS HG VENTURES

@DATAMITRA

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

5subscribers

+0 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-1002577036729
TypeChannel
Username@DATAMITRA
CreatedBetween 1 March 2025 and 31 July 2025— 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/DATAMITRA

Growth

56 August 2026 — 5 subscribers13 August 2026 — 5 subscribers6 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 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:025no change
6 Aug 2026, 22:095first reading

Engagement

20 posts held, back to 28 October 2025the 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 1 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1

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

28 Oct 2025, 13:28 UTC100 viewsread 13 August 2026

𐔌 . ⋮ 𝐃𝐀𝐓𝐀 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 .ᐟ ֹ ₊ ꒱ ━━━━━━━━━━ -‘⛉’- ━━━━━━━━━━ ⠀⠀⠀ ﴾ 𝗣𝗔𝗚𝗘 015 ﴿ 𝐎𝟏. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟐. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟑. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟒. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟓. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟔. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟕. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟖. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟗. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝟏𝐎. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 ﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌ 𖣘 @OFCHGVENTURES 𖣘

28 Oct 2025, 13:28 UTC66 viewsread 13 August 2026

𐔌 . ⋮ 𝐃𝐀𝐓𝐀 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 .ᐟ ֹ ₊ ꒱ ━━━━━━━━━━ -‘⛉’- ━━━━━━━━━━ ⠀⠀⠀ ﴾ 𝗣𝗔𝗚𝗘 014 ﴿ 𝐎𝟏. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟐. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟑. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟒. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟓. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟔. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟕. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟖. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝐎𝟗. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 𝟏𝐎. ◌Ⳋ𝅄 ◌Ⳋ𝅄 ◌Ⳋ𝅄 ﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌ 𖣘 @OFCHGVENTURES 𖣘

28 Oct 2025, 13:28 UTC66 viewsread 13 August 2026

𐔌 . ⋮ 𝐃𝐀𝐓𝐀 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 .ᐟ ֹ ₊ ꒱ ━━━━━━━━━━ -‘⛉’- ━━━━━━━━━━ ⠀⠀⠀ ﴾ 𝗣𝗔𝗚𝗘 013 ﴿ 𝐎𝟏. 𝐏𝐇𝐀𝐍𝐓𝐎𝐌 𝐑𝐄𝐆𝐈𝐌𝐄𝐍𝐓 ◌Ⳋ𝅄 @OFCPHANTOMREGIMENT ◌Ⳋ𝅄 @mppsphntre_bot ◌Ⳋ𝅄 AKTIF 𝐎𝟐. 𝐂𝐀𝐒𝐓𝐋𝐄 𝐎𝐅 𝐇𝐘𝐏𝐄𝐍 ◌Ⳋ𝅄 @CASTLEOFHYPEN ◌Ⳋ𝅄 @MPPSCASTOR_ROBOT ◌Ⳋ𝅄 AKTIF 𝐎𝟑. ‘𝟵𝟭𝟭 : 𝗣𝗢𝗥𝗦𝗬𝗧𝗛𝗘. ◌Ⳋ𝅄 @PORSYTHE ◌Ⳋ𝅄 @MPPSPORSY_BOT ◌Ⳋ𝅄 AKTIF 𝐎𝟒. GØKUHAI ◌Ⳋ𝅄 @GokuhaiDistrict ◌Ⳋ𝅄 @GokuhaiMpps_bot ◌Ⳋ𝅄 AKTIF 𝐎𝟓. Everwild High S

28 Oct 2025, 13:28 UTC61 viewsread 13 August 2026

𐔌 . ⋮ 𝐃𝐀𝐓𝐀 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 .ᐟ ֹ ₊ ꒱ ━━━━━━━━━━ -‘⛉’- ━━━━━━━━━━ ⠀⠀⠀ ﴾ 𝗣𝗔𝗚𝗘 012 ﴿ 𝐎𝟏. RACE ACADEMY ◌Ⳋ𝅄 @OFCRACEACADEMY ◌Ⳋ𝅄 @mppsraceacademybot ◌Ⳋ𝅄 Aktif 𝐎𝟐. 𝐎𝐅𝐂 𝐎𝐑𝐏𝐇𝐄𝐔𝐒 ◌Ⳋ𝅄 @OFCOORPHEUS ◌Ⳋ𝅄 @PODACIPHEUSBOT ◌Ⳋ𝅄 Rombak 𝐎𝟑. 𝗢𝗙𝗖 𝗥𝗨𝗦𝗛𝗢𝗢𝗡 ◌Ⳋ𝅄 @OFCRUSHOON ◌Ⳋ𝅄 @RUSHOONMPPSBOT ◌Ⳋ𝅄 Aktif 𝐎𝟒. 𝐌𝐀𝐍𝐖𝐎𝐌𝐀 𝐀𝐆𝐄𝐍𝐂𝐘 ◌Ⳋ𝅄 @OFCMANWOMA ◌Ⳋ𝅄 @MPPSMANWOMA_bot ◌Ⳋ𝅄 ACTIVE 𝐎𝟓. SKANECA || NOCTURNE ACADE

28 Oct 2025, 13:28 UTC51 viewsread 13 August 2026

𐔌 . ⋮ 𝐃𝐀𝐓𝐀 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 .ᐟ ֹ ₊ ꒱ ━━━━━━━━━━ -‘⛉’- ━━━━━━━━━━ ⠀⠀⠀ ﴾ 𝗣𝗔𝗚𝗘 011 ﴿ 𝐎𝟏. 𝐄𝐒𝐂𝐀𝐏𝐄 𝐎𝐅𝐅𝐈𝐂𝐈𝐀𝐋 ◌Ⳋ𝅄 @OFCESCAPE ◌Ⳋ𝅄 @escapempps_bot ◌Ⳋ𝅄 Aktif 𝐎𝟐. 𝗖𝗟𝗨𝗦𝗧𝗘𝗥 𝗗𝗘𝗢𝗚𝗬𝗨𝗦𝗔𝗡 ◌Ⳋ𝅄 @CLUSTERDEOGYUSAN ◌Ⳋ𝅄 @PARTNERDEOGYUSANBOT ◌Ⳋ𝅄 Aktif 𝐎𝟑. OFC TAURÒ ◌Ⳋ𝅄 @OFCTAURO ◌Ⳋ𝅄 @MPSTROBOT ◌Ⳋ𝅄 Libur ╰─► 𝗦𝗨𝗕 𝗨𝗡𝗜𝗧 ⠀ ⠀ ❝ 𝗢𝗙𝗖 𝗞𝗔𝗨𝗕𝗢𝗜 ◌Ⳋ𝅄 @OFCKAUBOI ◌Ⳋ𝅄 Libur 𝐎𝟒. 𝗢𝗙𝗖 𝗖𝗬𝗧𝗘𝗚𝗡𝗢 ◌Ⳋ𝅄 @C

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

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 HG VENTURES” (@DATAMITRA), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DATAMITRA.

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.