Telegram RegisterThe public register of Telegram
Telegram profile photo for ARSIP BSC

Channel

ARSIP BSC

@arsipbsc

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

4subscribers

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

Growth

47 August 2026 — 4 subscribers13 August 2026 — 4 subscribers7 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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:464no change
7 Aug 2026, 09:504first reading

Engagement

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

Recent posts

12 Jul 2022, 11:31 UTC148 viewsread 13 August 2026

ㅤ ㅤ✧ BLOOD SACRIFICE'S PARTNER ⌗⋆ PAGE O45 ㅤ➪★ @Xalverosofc ㅤㅤ☆ @Xelmpps_bot ╰┈➤ ACTIVE ㅤ➪★ @OFCWEIBERDRACHE ㅤㅤ☆ @Weiberdrachempps_bot ╰┈➤ ACTIVE ㅤ➪★ @SLUSTER_OFC ㅤㅤ☆ @MPPSOFFICE_BOT ╰┈➤ ACTIVE ㅤ➪★ @ANGVOLOOFFICIAL ㅤㅤ☆ @MPPSAVBOT ╰┈➤ rombak ㅤ➪★ @jjhvillage ㅤㅤ☆ @DSJHMPPSROBOT ╰┈➤ ACTIVE ㅤ➪★@NCT_SQUAD ㅤㅤ☆ @NEVSAWORKBOT ╰┈➤ ACTIVE ㅤㅤㅤSUB UNIT ㅤㅤㅤ★ @OFCNCTMENFESS ㅤ…

12 Jul 2022, 11:25 UTC69 viewsread 13 August 2026

ㅤ ㅤ✧ BLOOD SACRIFICE'S PARTNER ⌗⋆ PAGE O44 ㅤ➪★ @AZTEXICOFC ㅤㅤ☆ @AZTECLABELBOT ╰┈➤ ACTIVE ㅤ➪★ @ofcrpolympus ㅤㅤ☆ @Psolympus_bot ╰┈➤ ACTIVE ㅤ➪★ @Ghsschooll ㅤㅤ☆ @mppsgarudabot ╰┈➤ ACTIVE ㅤㅤSUB UNIT ㅤㅤㅤ★ @OFFICIALGES ㅤㅤㅤ☆ @mppsgarudabot ╰┈➤ ACTIVE ➪★ @JAEROSETOWN ㅤㅤ☆ @thetownmpps_bot ╰┈➤ ACTIVE ㅤ➪★ @OFCDRAKIOS ㅤㅤ☆ @dksmpps_bot ╰┈➤ ACTIVE ㅤ➪★ @ARKAMAYAOFC ㅤㅤ…

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

“ARSIP BSC” (@arsipbsc), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/arsipbsc.

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.