Telegram RegisterThe public register of Telegram
Telegram profile photo for Partnership Zona Baper

Channel

Partnership Zona Baper

@arsipzonabaper

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

2subscribers

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

Growth

27 August 2026 — 2 subscribers13 August 2026 — 2 subscribers7 August 202613 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”. The vertical axis spans 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 20:502no change
7 Aug 2026, 06:592first reading

Engagement

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

Recent posts

28 Sept 2022, 14:42 UTC50 viewsread 13 August 2026

16 PARTNERSHIP ✎↷: ——————— ঔৣ‌ஓீ‌➣ 𝐎𝐅𝐂 𝐈𝐍𝐅𝐀𝐍𝐓𝐄𝐑𝐈 𝐀𝐄𝐋𝐈𝐔𝐒 𓆩࣪‌🐥𓆪‌ @OFCSQINFANTERIAELIUS ⁖ฺ۟·֗٬‌⃟❄️ @Temaninfaelbot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ THE DEATHSTALKER 𓆩࣪‌🐥𓆪‌ @DEATHSTALKEROFC ⁖ฺ۟·֗٬‌⃟❄️ @dhmpsbot ঔৣ‌ஓீ‌➣ Kindom Hospital 𓆩࣪‌🐥𓆪‌ @kingdomhospitals ⁖ฺ۟·֗٬‌⃟❄️ @Mppskingdomhsptlbot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ GΔŁΔXŦØR GΛNK 𓆩࣪‌🐥𓆪‌ @OFCGALAXTOR ⁖ฺ۟·֗٬‌⃟❄️ @GALAXTORMPPSBOT ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ DEATHWISH…

28 Sept 2022, 14:41 UTC24 viewsread 13 August 2026

16 PARTNERSHIP ✎↷: ——————— ঔৣ‌ஓீ‌➣ 𝐍𝐀𝐌𝐉𝐀 𝐔𝐍𝐈𝐕𝐄𝐑𝐒𝐄 𓆩࣪‌🐥𓆪‌ @OFCNAMJAUNIVERSE ⁖ฺ۟·֗٬‌⃟❄️ @mpsnmjvbot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ 𝐎𝐅𝐂 𝐙𝐄𝐏𝐇𝐖𝐎𝐋𝐅 𓆩࣪‌🐥𓆪‌ @ZEPHWOLFOFC ⁖ฺ۟·֗٬‌⃟❄️ @ZEPHWOLFMPPS_bot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ 𝗠𝗔𝗟𝗩𝗔𝗚𝗜𝗘 '𝟱𝟵 𝗦𝗤 𓆩࣪‌🐥𓆪‌ @OFCMALVAGIESQ ⁖ฺ۟·֗٬‌⃟❄️ @psmalvagie_robot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ ROLEPLAYER ORGANIZER 𓆩࣪‌🐥𓆪‌ @RPORGANIZER ⁖ฺ۟·֗٬‌⃟❄️ @RPOMPPS_BOT ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ REPUBLIK DRE…

28 Sept 2022, 09:27 UTC20 viewsread 13 August 2026

15 PARTNERSHIP ✎↷: ——————— ঔৣ‌ஓீ‌➣ 𝐌Λ𝐑𝐊Ø𝐆𝐀𝐍𝐊 𓆩࣪‌🐥𓆪‌ @MARKOGANK ⁖ฺ۟·֗٬‌⃟❄️ @TEMANMARKO_BOT ꒰ 𝅄 𓆤: AKTIF SUB UNIT ঔৣ‌ஓீ‌➣ MARKOSUICY 𓆩࣪‌🐥𓆪 @MARKOSUICY ঔৣ‌ஓீ‌➣ 𝗠ugen de Cops. 𓆩࣪‌🐥𓆪 @OFCMUGEN ঔৣ‌ஓீ‌➣ 𝐂𝐀𝐒𝐓𝐑𝐔𝐌𝐕𝐊𝐎𝐎𝐊 𓆩࣪‌🐥𓆪‌ @CASTRUMVKOOK ⁖ฺ۟·֗٬‌⃟❄️ @dcvskmppsbot ꒰ 𝅄 𓆤: AKTIF SUB UNIT ঔৣ‌ஓீ‌➣ 𝐃𝐄𝐂𝐑𝐈𝐌𝐒 𝐉𝐄𝐍𝐊𝐎𝐎𝐊𝐕 𓆩࣪‌🐥𓆪 @OFCDECRIMSJENKOOKV ঔৣ‌ஓீ‌➣ BANDARA RP 𓆩࣪‌…

28 Sept 2022, 09:26 UTC16 viewsread 13 August 2026

14 PARTNERSHIP ✎↷: ——————— ঔৣ‌ஓீ‌➣ — ะ 信 𝐁𝐀𝐍𝐆𝐓𝐀𝐍𝐑𝐕 𝐒𝐐 𓆩࣪‌🐥𓆪‌ @bangtanrvsq ⁖ฺ۟·֗٬‌⃟❄️ @btrvmpps_bot ꒰ 𝅄 𓆤: AKTIF SUB UNIT ঔৣ‌ஓீ‌➣ 𝟏𝟕𝟑 – Æ𝐍𝐂𝐓𝐀𝐂𝐊 𝐒𝐐 𓆩࣪‌🐥𓆪 @aenctacksq ঔৣ‌ஓீ‌➣ 𝗢𝗙𝗖 𝗦𝗘𝗖𝗥𝗘𝗧 𝗥𝗔𝗖𝗘𝗥 𓆩࣪‌🐥𓆪‌ @SECRETRACEROFC ⁖ฺ۟·֗٬‌⃟❄️ @pssecretracer_bot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ ⎙ OFC STREET RIDERS 𓆩࣪‌🐥𓆪‌ @OFCSTREETRIDERS ⁖ฺ۟·֗٬‌⃟❄️ @MPPS001BOT ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ ARTEA ORGANIZER 𓆩࣪‌🐥𓆪‌ @AR…

24 Sept 2022, 09:50 UTC20 viewsread 13 August 2026

13 PARTNERSHIP ✎↷: ——————— ঔৣ‌ஓீ‌➣ 𝟳𝟮𝟳. 𝗭𝗔𝗚𝗥𝗘𝗨𝗦 𝗞𝗜𝗡𝗚𝗗𝗢𝗠 𓆩࣪‌🐥𓆪‌ @OFCZAGREUS ⁖ฺ۟·֗٬‌⃟❄️ @MPPSREUZBOT ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ • 𝗡𝗘𝗢𝗖𝗧𝗦𝗣𝗔 II 𓆩࣪‌🐥𓆪‌ @NEOCTSPAOFC ⁖ฺ۟·֗٬‌⃟❄️ @NOECTSPAPSBOT ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ 𝐕𝗲𝗹𝗼𝘁𝗿𝗮𝗻 𝐆𝗮𝗻𝗸 𓆩࣪‌🐥𓆪‌ @OFCVELOTRANGANK ⁖ฺ۟·֗٬‌⃟❄️ @MPPSVLT_BOT ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ 𝗢𝗙𝗖 𝗗𝗥𝗔𝗞𝗢𝗩𝗢𝗭 𓆩࣪‌🐥𓆪‌ @OFCDRAKOVOZ ⁖ฺ۟·֗٬‌⃟❄️ @PSDRAKOVOZBOT ꒰ 𝅄 𓆤: VAKUM ঔৣ‌ஓீ‌➣ 𝐎𝐅𝐂 𝐒𝐄𝐑𝐃𝐀𝐈𝐆𝐋𝐄 𓆩࣪‌🐥𓆪‌ @SER…

22 Sept 2022, 13:24 UTC15 viewsread 13 August 2026

12 PARTNERSHIP ✎↷: ——————— ঔৣ‌ஓீ‌➣ 𝗖Ø𝗥𝗩𝗨𝗦 𓆩࣪‌🐥𓆪‌ @OFCCORVUS ⁖ฺ۟·֗٬‌⃟❄️ @corvusmppsbot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ 𝗩Ⓞ𝗟𝗘𝗨𝗥 𝟖𝟔 𓆩࣪‌🐥𓆪‌ @OFCVOLEUR86 ⁖ฺ۟·֗٬‌⃟❄️ @mppsbegalbot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ B47.𝐎𝐅𝐂. 𝐁𝐈П₲Ө 𓆩࣪‌🐥𓆪‌ @BINGOOFCSQ ⁖ฺ۟·֗٬‌⃟❄️ @MPPSBINGOBOT ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ 車 𝐎𝐅𝐂 𝐙𝐈𝐂𝐀𝐑 𝐒𝐐 🇵🇪 𓆩࣪‌🐥𓆪‌ @zicarsq ⁖ฺ۟·֗٬‌⃟❄️ @mppszicar_bot ꒰ 𝅄 𓆤: AKTIF ঔৣ‌ஓீ‌➣ 𝐎𝐅𝐅𝐈𝐂𝐈𝐀𝐋 𝐒𝐋𝐀𝐘𝐄𝐑𝐒𝐒 𝐒𝐐𝐔𝐀𝐃 𓆩࣪‌🐥𓆪‌ @OFCSLAYERSS…

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

“Partnership Zona Baper” (@arsipzonabaper), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/arsipzonabaper.

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.