Telegram RegisterThe public register of Telegram

Channel

ARSIP DARMAJA

@partnerdarmaja

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

3subscribers

+0 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001583754499
TypeChannel
Username@partnerdarmaja
CreatedBetween 1 August 2021 and 20 December 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/partnerdarmaja

Growth

310 August 2026 — 3 subscribers13 August 2026 — 3 subscribers10 August 202613 August 2026
2 measurements spanning 3 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, 10:193no change
10 Aug 2026, 06:463first reading

Engagement

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

What this channel posts

Links
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 Jan 2022, 08:02 UTC84 viewsread 13 August 2026

⨳ PAGE 25 _ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹

28 Jan 2022, 08:02 UTC45 viewsread 13 August 2026

⨳ PAGE 24 _ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹

28 Jan 2022, 08:02 UTC22 viewsread 13 August 2026

⨳ PAGE 23 _ ★. MIŚFIT EVENT ORGANIZER ▩૰￫ @OFCMISFITGANK ⤹ @TEMANMISFITROBOT 117. RIDERS MAN ▩૰￫ @RIDERSRPW ⤹ @MEDPARTRDM_BOT GOLDEN BAR ▩૰￫ @GOLDENBARCEHA ⤹ @GOLDENMPPS_BOT STRIGIF∅RMΣS ▩૰￫ @STRIGIFORMESOFC ⤹ @mppsstrigiformesbot 𝐃𝐒𝐄𝐂𝐄𝐍 𝐎𝐕𝐈𝐗𝐄𝐍𝐒 ▩૰￫ @OFCDSECENOVIXENS ⤹ @mppsdsecenovixens_bot ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹ ▩૰￫ ⤹

21 Jan 2022, 10:56 UTC39 viewsread 13 August 2026

⨳ PAGE 22 _ 𝐎𝐅𝐂 𝐃𝐑𝐀𝐒𝐈𝐗𝐓𝐀 ▩૰￫ @OFCDRASIXTA ⤹ @DRASIXTAMPPSBOT BUMI ▩૰￫ @BUMIOFC ⤹ @BUMIPARTNERBOT ✰ 𝐁𝐈𝐙𝐎𝐍𝐄𝐂𝐓 ✰ ▩૰￫ @OFCBIZONECT ⤹ @KANTORBIZONECTBOT 𝗢𝗙𝗖 𝗙𝗟𝗨𝗧𝗨𝗥𝗘 🦋 ▩૰￫ @OFCFLUTURE ⤹ @FLUTUREROBOT 975. 𝐒𝐓𝐀𝐆𝐄 𝐉𝐊𝐓𝐇 ▩૰￫ @STAGEJKTH ⤹ @PSSTAGEJKTH_BOT 𝐎𝐅𝐂 𝐕'𝐉𝐄 ▩૰￫ @OFCVJE ⤹ @PSVJEBOT CLASSY HYBE ▩૰￫ @CLASSYHYBE ⤹ @SsiBbipsBot 𝟱𝟴𝟭. 𝗢𝗙𝗖 𝗠★𝗣𝗔𝗡𝗝 ▩૰￫ @OFCMAPANJI ⤹ @MPPSMAPANJIBOT 𝐖Ⱥ𝐑𝐊Ø𝐏 𝟒𝟓 ▩૰￫…

21 Jan 2022, 10:56 UTC27 viewsread 13 August 2026

⨳ PAGE 21 _ 𝐎𝐅𝐂 𝐈𝐍𝐃𝐄𝐒𝐓𝐑𝐔𝐂𝐓𝐈𝐁𝐋𝐄 ▩૰￫ @OFCINDESTRUCTIBLE ⤹ 𝐒 𝐄 𝐂 - 𝐆 𝐄 𝐍 𝐓 [ sub.u ] ⤹ @SECGENT ⤹ 𝐎𝐅𝐂. 𝐁𝐑𝐀𝐕𝐄 𝐖𝐎𝐋𝐅 [ sub.u ] ⤹ @OFCBRVWLF ⤹ 𝐖𝐈𝐍𝐗 𝐏𝐑𝐎𝐌𝐎𝐓𝐄 [ sub.u ] ⤹ @WINXPROMOTE ⤹ @KAWANMBSWBOT ANTARIKSA INTERNATIONAL SCHOOL ▩૰￫ @ANTARIKSASCHOOL ⤹ BATIQUE EVENT ORGANIZER [ sub.u ] ⤹ @BATIQUEORGANIZER ⤹ @ASISSTANANTARIKSA_BOT 𔓕 𝗞𝗔𝗠𝗣𝗨𝗡𝗚 𝗜𝗠𝗣𝗜𝗔𝗡 ▩૰￫ @kampungimpian ⤹ @MPPSKMPGBOT OFC WOLF…

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

.
@AEXTHRONE · 1,8161 post𝐀𝐍𝐓𝐀𝐑𝐈𝐊𝐒𝐀 𝐈𝐍𝐓𝐄𝐑𝐍𝐀𝐓𝐈𝐎𝐍𝐀𝐋 𝐒𝐂𝐇𝐎𝐎𝐋
@ANTARIKSASCHOOL · 3,6131 postOFC . BAJIGUR 🇦🇱
@B4JIGUROFC · 6731 post𖥔 𝗦𝗨𝗥𝗔𝗧 𝗜𝗭𝗜𝗡 𝗕𝗧𝗥𝗩
@bangtanrvsq · 41 post𝐋𝐈𝐒𝐓 𝐌𝐏𝐏𝐒 𝐁𝐁𝐐 [ 𝟐 ]
@bbqmpps2 · 171 postbubar
@bbqofc · 8681 postDESA KATEHA
@dskth · 4501 post[BUBAR] GOLDEN BAR CHANNEL༄
@goldenbarceha · 911 postMarkogank
@Markogank · 61 postSOON
@MASALEMBORPW · 871 postMEMORY MUCIKARI
@mucikariofc · 61 postBUBAR
@OFCAQUZIUZ · 201 postOFC BRAVE WOLF { new era }
@OFCBRVWLF · 2351 post𝗢𝗣𝗠𝗘𝗠𝗕 // 𝐎𝐅𝐂 𝐅𝐋𝐔𝐓𝐔𝐑𝐄 🦋💥
@OFCFLUTURE · 511 postGaruda
@ofcgaruda · 21 post[ROMBAK] 𝗢𝗙𝗖 𝗜𝗧'𝗢𝗡𝗘𝗔𝗦𝗨𝗥𝗘
@OFCITONEASURE · 1261 post𝐌𝐎𝐔𝐍𝐓𝐀𝐈𝐍 𝐓𝐈𝐆𝐄𝐑
@OFCMOUNTAINTIGER · 211 post谷 𝐎𝐅𝐂 𝐑𝐄𝐍𝐂𝐈𝐓𝐘
@ofcrencity · 551 post𝗦𝗨𝗣𝗘𝗥𝗜𝗢𝗥𝗞𝗧𝗛
@OFCSUPERIORKTH · 2571 postvakum, don't unsubs.
@OFCVJE · 901 post𝐎𝐅𝐂 𝐆𝐋𝐀𝐌𝐎𝐑𝐒𝐓𝐀
@officialglamorstagank · 461 postkeep
@officialkosanpakboi · 21 post𝐃𝐄𝐗𝐙𝐀𝐑Ø𝐒 𝐒𝐇¡𝐓𝐏Ø𝐒𝐓
@STAGEJKTH · 2831 postVAKUM || TREAESPA OFC
@Treaespaofc · 1291 post

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.

“ARSIP DARMAJA” (@partnerdarmaja), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/partnerdarmaja.

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.