Telegram RegisterThe public register of Telegram
Telegram profile photo for TEMAN J2MH

Channel

TEMAN J2MH

@temanjjmh

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

1subscribers

+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-1001543580524
TypeChannel
Username@temanjjmh
CreatedBetween 1 August 2021 and 19 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live26 September 2026
Measurements held2
On Telegramt.me/temanjjmh

Growth

17 August 2026 — 1 subscribers14 August 2026 — 1 subscribers7 August 202614 August 2026
2 measurements spanning 7 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:471no change
7 Aug 2026, 07:191first reading

Engagement

20 posts held, back to 19 June 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 page of 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 3 August 2022. 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 14 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

3 Aug 2022, 13:18 UTC50 viewsread 14 August 2026

ㅤㅤㅤ𝐉2𝐌𝐇𝐂 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏ㅤㅤ PAGE 24 ❬ 🩸𝗦𝗘𝗥𝗩𝗜𝗭𝗜𝗢 𝗥𝗢𝗬𝗔𝗟 𝗛𝗘𝗔𝗟𝗧𝗛 ❭ ➜ @CVZHospital ➜ @MPPSSRHBOT ❬ OFC RADAR V ❭ ➜ @PUSATRADARV ➜ @RDVOFFICEBOTㅤㅤ ❬ ❭ ➜ ➜ ❬ ❭ ➜ ➜ ❬ ❭ ➜ ➜ ❬ ❭ ➜ ➜ ❬ ❭ ➜ ➜ ❬ ❭ ➜ ➜ ❬ ❭ ➜ ➜ ❬ ❭ ➜ ➜

14 Jul 2022, 10:33 UTC92 viewsread 14 August 2026

ㅤㅤㅤ𝐉2𝐌𝐇𝐂 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏ㅤㅤ PAGE 23 ❬ 🇻🇮 𝐄𝐕𝕺𝐒 𝐆𝕬𝐍𝐊 ❭ ➜ @ofcevoshome ➜ @psevosgank_bot ❬ 𝐌𝐄𝐍𝐆𝐊𝐄𝐂𝐄 𝐎𝐅𝐂 ❭ ➜ @MENGKECEOFC ➜ @MPMKC_BOT ❬ DREAMWOOD! ❭ ➜ @OFCDRMWOOD ➜ @DRMWPARTNERBOT ❬ OFC BAZENDOS ❭ ➜ @OFCBAZENDOS ➜ @MPBAZENDOSBOT ❬ 𝟮𝟵𝟭𝟬 : 𝐁𝐑𝐀𝐉𝐀𝐏𝐀𝐓𝐈 ❭ ➜ @OFCBRAJAPATI ➜ @MPPSBPBOT ❬ l'OROS Del FAMILIA ❭ ➜ @IOROSDFAMILIA ➜ @DELFAMILIA_BOT ❬ YOUR TRUE LOVE ❭ ➜ @YTLOFC ➜ @FROMPSROBOT ❬ 𝕴eodream 𝕴nt…

10 Jul 2022, 12:57 UTC61 viewsread 14 August 2026

ㅤㅤㅤ𝐉2𝐌𝐇𝐂 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏ㅤㅤ PAGE 22 ❬ The Big Love ❭ ➜ @thebiglove ➜ @PSBIGLOVE_BOT 𝐒𝐔𝐁 𝐔𝐍𝐈𝐓 ❬ 𝗕ig 𝗪orld 𝗣romote ❭ ➜ @bwldpromote ❬ Scornellius Academy ❭ ➜ @scornelliusacademy ➜ @Scn_psbot ❬ REPUBLIK KTH ❭ ➜ @republikkth ➜ @psrpkthbot ❬ 𝐌𝐈*𝐙𝐎𝐍𝐄 ❭ ➜ @izoneofcch ➜ @Mizoneps_Bot ❬ 𝐌𝐎𝐍𝐎𝐅𝐋𝐀𝐌𝐄 𝐒𝐐𝐔𝐀𝐃 ❭ ➜ @OFCMONOFLAME ➜ @Monoflameps_bot 𝐒𝐔𝐁 𝐔𝐍𝐈𝐓 ❬ 𝑩𝑨𝑱𝑨𝑵𝑮 𝟗𝟔𝟖 𝑺𝑸 ❭ ➜ @BAJANGOFC ❬ BASE 00L ❭ ➜ @base00…

6 Jul 2022, 03:07 UTC62 viewsread 14 August 2026

ㅤㅤㅤ𝐉2𝐌𝐇𝐂 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏ㅤㅤ PAGE 21 ❬ 𝐎𝐅𝐂. 𝐁𝐈П₲Ө ❭ ➜ @BINGOOFCSQ ➜ @MPPSBINGOBOT ❬ HELLENIC HOSPITAL ❭ ➜ @HELLENICHOSPITAL ➜ @PSHELLENICBOT ❬ 𝕺𝕱𝕮 𝕯𝐈𝐙𝐀𝐄𝐒𝐓𝐄𝕽 ❭ ➜ @DIZAESTER ➜ @DZSMPPSBOT 𝐒𝐔𝐁 𝐔𝐍𝐈𝐓 ❬ 𝐀𝕮𝕺𝐒𝐒𝐀 𝟓𝟔 ❭ ➜ @ACOSSA56 ❬ BUMI ❭ ➜ @BUMIOFC ➜ @BUMIPARTNERBOT ❬ THVJEN COMPANY ❭ ➜ @THVJENCOMPANY ➜ @kawantjencbot ❬ 𝐕𝐀𝐍 𝐄𝐔𝐓𝐎𝐏𝐈𝐀 ❭ ➜ @EUTOPIASQ ➜ @vaneutpsbot ❬ MIGN♡NNE L♡VE TM♡ ❭ ➜ @Mignolovetmo ➜ …

2 Jul 2022, 16:10 UTC70 viewsread 14 August 2026

ㅤㅤㅤ𝐉2𝐌𝐇𝐂 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏ㅤㅤ PAGE 20 ❬ 𝐎𝐅𝐂 𝐖𝐈𝐋𝐃𝐄𝐑 𝐊𝐓𝐇 ❭ ➜ @ofcwilderkth ➜ @mppswilderbot ❬ OFC YURILOUS ❭ ➜ @OfcYurilous ➜ @YurilouspsBot ❬ 𝐔𝐍𝐋𝐈𝐌𝐈𝐓𝐄𝐃 𝐒𝐐 𝐎𝐅𝐂 ❭ ➜ @UNLIMITEDOFC ➜ @mppsunlimitedbot ❬ ZONA GXG ❭ ➜ @ZONAGXG ➜ @mppszonagxg_bot 𝐒𝐔𝐁 𝐔𝐍𝐈𝐓 ❬ ZONA BUTCHY ❭ ➜ @ZONABUTCHY ❬ ZONA FEMME ❭ ➜ @ZONAFEMME ❬ REPUBLIK DREAM ❭ ➜ @REPUBLIKDREAM ➜ @MPPSREPBDREAM_BOT ❬ 𝐎𝐅𝐂 𝐕𝐄𝐑𝐘𝐋𝐎𝐗 ❭ – L ➜ @ofcverylox…

2 Jul 2022, 05:28 UTC57 viewsread 14 August 2026

ㅤㅤㅤ𝐉2𝐌𝐇𝐂 𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏ㅤㅤ PAGE 19 ❬ 𝐄𝐗𝐈𝐋𝐄 𝐖𝐀𝐑𝐑𝐈𝐎𝐑 ❭ ➜ @OFCEXILEWARRIOR ➜ @EXILEPSBOT ❬ 𝐎𝐅𝐂 𝐇𝐎𝐔𝐒𝐄 𝐎𝐅 𝐂𝐀𝐑𝐃'𝐒 ❭ ➜ @OfcHouseOfCards ➜ @MppsHOCbot 𝐒𝐔𝐁 𝐔𝐍𝐈𝐓 ❬ 𝐎𝐅𝐂 𝐊𝐀𝐊𝐄𝐆𝐔𝐑𝐔𝐈 ❭ ➜ @OfcKakegurui ❬ 𝐌𝐄𝐍𝐅𝐄𝐒𝐒 𝐑𝐎𝐋𝐄𝐏𝐋𝐀𝐘𝐄𝐑⁹³ ❭ ➜ @MenfessRoleplayer93 ❬ 𝗝𝐀𝗦𝐔𝗞𝐄 𝗩I𝗟𝗟A𝗚𝗘 ❭ ➜ @JASUKEVILLAGEOFFICIAL ➜ @JAYABERSAMAJSKENHYBOT 𝐒𝐔𝐁 𝐔𝐍𝐈𝐓 ❬ 𝐸𝐍𝐇𝐘 𝗦𝗤𝗨𝑨𝑫 ❭ ➜ @enhysq ❬ yabai mpps ❭ ➜ @yabaiofc ➜ @yabaimpps_bot ❬ 𝐀𝐅𝐅𝐄𝐂𝐓𝐈𝐎 𝐖𝐄𝐃𝐃…

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

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

“TEMAN J2MH” (@temanjjmh), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/temanjjmh.

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.