Telegram RegisterThe public register of Telegram

Channel

-MT CORP PARTNERSHIP-

@temantmjj

On this record: Growth · Engagement · 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-1001514300856
TypeChannel
Username@temantmjj
First recorded15 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/temantmjj

Growth

17 August 2026 — 1 subscribers15 August 2026 — 1 subscribers7 August 202615 August 2026
2 measurements spanning 8 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
15 Aug 2026, 00:321no change
7 Aug 2026, 01:381first reading

Engagement

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

Recent posts

4 Mar 2022, 00:01 UTC71 viewsread 15 August 2026

ㅤ ㅤ𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐌𝐓 𝐂𝐎𝐑𝐏 ━━━━▣━━◤ 𝐏𝐀𝐆𝐄 3O ◢━━▣━━━━━ 𝐎1. 𝐍𝐀𝐌𝐉𝐀𝐗 𝐎𝐅𝐂 𖠿 ‣ @NAMJAXOFC ‣ @MPPSNJX_BOT 𝐎2. 𓄂𝕺𝐅𝐂. 𝕾𝐈𝐋𝐈𝐖𝐀𝐍𝐆𝐈 𖠿 ‣ @ofc_siliwangi ‣ @siliwangimppsbot 𝐎3. BRIGANZ FLIGHT ACADEMY 𖠿 ‣@BRIGANZFLIGHTACADEMYRP ‣@MPPSBRIGANZCORPBOT [ 𝐒UB 𝐔NIT ] 𖠿 ‣ BRIGANZ CRUISE ORGANIZER 𖠿 ‣ @BRIGANZORGANIZER 𖠿 ‣ @MPPSBRIGANZCORPBOT [ 𝐒UB 𝐔NIT ] 𖠿 ‣ BRIGANZ JOURNAL NE

24 Feb 2022, 02:25 UTC107 viewsread 15 August 2026

ㅤ ㅤ𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐌𝐓 𝐂𝐎𝐑𝐏 ━━━━▣━━◤ 𝐏𝐀𝐆𝐄 29 ◢━━▣━━━━━ 𝐎1. 𝐎𝐅𝐂 𝐑𝐄𝐀𝐋 𝐍𝐂𝐓 𖠿 ‣ @realnctsq ‣ @Mppsrealnct_bot 𝐎2. BORDEAUX 𖠿 ‣ @OFCBORDEAUX ‣ @GR3YROBOT [ 𝐒UB 𝐔NIT ] 𖠿 ‣ @OFCSIGNAL ‣ @THEVISUELLE ‣ @PARANOIDOFC 𝐎3. 𝐎𝐅𝐂 𝐅Ø𝐗 𖠿 ‣ @OFCFOXSQ ‣ @TEMANFOX_BOT 𝐎4. 𝗣𝗔𝗧𝗥𝗜𝗢𝗧 𖠿 ‣ @PATRIOTOFC ‣ @PATRIOTPSBOT 𝐎5. BIKERS AREA 𖠿 ‣ @BIKERSAREA

17 Feb 2022, 04:06 UTC121 viewsread 15 August 2026

ㅤ ㅤ𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐌𝐓 𝐂𝐎𝐑𝐏 ━━━━▣━━◤ 𝐏𝐀𝐆𝐄 28 ◢━━▣━━━━━ 𝐎1. OFC AENZYCT 𖠿 ‣ @AENZYCTOFC ‣ @AENZYCTPS_BOT 𝐎2. 95. J DREAM MANSION 𖠿 ‣ @OFCJDREAM ‣ @PSNCTJBOT 𝐎3. 𝐎𝐅𝐂 𝐖𝐀𝐍𝐓𝐄𝐃 𖠿 ‣ @wantedofc ‣ @mppswanted_bot 𝐎4. 𝗧𝗛𝗘 𝗟𝗨𝗫 𝗕𝗔𝗥 𖠿 ‣ @OFC_TLB ‣ @Theluxmpps_bot 𝐎5. ΘFC ΣPIPHΛNY 𖠿 ‣ @OFCEPIPHANYCITY ‣ @EpiphanyMpps_bot 𝐎6. 𝗟𝗘∆𝗗𝗘𝗡𝗜𝗖 𖠿 ‣ @OFCLEADENIC

12 Feb 2022, 08:01 UTC115 viewsread 15 August 2026

ㅤ ㅤ𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐌𝐓 𝐂𝐎𝐑𝐏 ━━━━▣━━◤ 𝐏𝐀𝐆𝐄 27 ◢━━▣━━━━━ 𝐎1. 𝐎𝐅𝐂 𝐈𝐍𝐃𝐑𝐀𝐏𝐑𝐀𝐒𝐓𝐇𝐀 𖠿 ‣ @OFCINDRAPRASTHA ‣ @idptsmartbot 𝐎2. ASRAMA NAMJA 𖠿 ‣ @ASRAMANAMJAOFC ‣ @ASRAMAMPPSBOT 𝐎3. CARNEVALE EVENT ORGANIZER 𖠿 ‣ @CEOFC ‣ @MPSCARNEVALEBOT 𝐎4. 𝐋𝐀𝐃𝐘 . 𝐑𝐀$𝐂𝐀𝐋𝐒 𖠿 ‣ @OFCLADYRASCALS ‣ @MPPSLADYRASCALS_BOT 𝐎5. OFC NEOITZY 𖠿 ‣ @neoitzysq ‣ @mppsneoitzy_bot 𝐎6. Lotu

10 Feb 2022, 13:33 UTC104 viewsread 15 August 2026

ㅤ ㅤ𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐌𝐓 𝐂𝐎𝐑𝐏 ━━━━▣━━◤ 𝐏𝐀𝐆𝐄 26 ◢━━▣━━━━━ 𝐎1. KAWANAN CHANYEOL 𖠿 ‣ @kawananchanyeol ‣ @kcypsbot 𝐎2. ☾ 𝐎𝐅𝐂 𝐆𝐎𝐋𝐃𝐌𝐎𝐎𝐍 𝐒𝐐 🇹🇰 𖠿 ‣ @ofcgoldmoonsq ‣ @mppsgoldmoon_bot 𝐎3. LOVE INFINITY TMO 𖠿 ‣ @OFCLOVEINFINITY ‣ @LIFYPSBOT 𝐎4. 182.𝐊𝐎𝐍𝐓𝐑𝐀𝐊𝐀𝐍 𝐁𝐔𝐃𝐈𝐒 𖠿 ‣ @KTBGOFC ‣ @CASTLEPSBOT [ 𝐒UB 𝐔NIT ] 𖠿 ‣ @VKOOKSOFC 𝐎5. 𝐎𝐅𝐂 𝐃𝐄𝐕𝐀𝐋𝐎𝐑𝐄 𖠿 ‣ @devaloreofc

8 Feb 2022, 01:15 UTC116 viewsread 15 August 2026

ㅤ ㅤ𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐌𝐓 𝐂𝐎𝐑𝐏 ━━━━▣━━◤ 𝐏𝐀𝐆𝐄 25 ◢━━▣━━━━━ 𝐎1. 𝟮𝟬𝟮 . 𝗕𝗨𝗝𝗔𝗡𝗚 𝗡𝗖𝗧 𖠿 ‣ @DESABUJANGNCT ‣ @PSBUJANGNCTBOT 𝐎2. ZONELINE 𖠿 ‣ @zoneline ‣ @sahabatZLbot 𝐎3. BAEKHYUN’S 𖠿 ‣ @BAEKHYUNAREA ‣ @SECREATBILAGE_BOT [ 𝐒UB 𝐔NIT ] 𖠿 ‣ @CHANBAEKLORD 𝐎4. 𝐆 𝐎 𝐃 𝐒 𖠿 ‣ @OFCGODS ‣ @ofcmpgodsbot 𝐎5. 𝐔𝐍𝐈𝐕𝐄𝐑𝐒𝐄 𝐋𝐀𝐁𝐄𝐋𝐒 𖠿 ‣ @UNIVERSELABELS ‣ @mppsnctubot [ 𝐒UB

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

“-MT CORP PARTNERSHIP-” (@temantmjj), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/temantmjj.

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.