Telegram RegisterThe public register of Telegram
Telegram profile photo for Arsip Bedros

Channel

Arsip Bedros

@bedrosarsip

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

1subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1001583900305
TypeChannel
Username@bedrosarsip
Created19 August 2021measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live3 September 2026
Measurements held2
On Telegramt.me/bedrosarsip

Growth

113 Aug 2026, 20:46 — 1 subscribers15 Aug 2026, 07:16 — 1 subscribers13 Aug 2026, 20:4615 Aug 2026, 07:16
2 measurements spanning 1 day. 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, 07:161no change
13 Aug 2026, 20:461first reading

Engagement

13 posts held, back to 19 August 2021the 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 13 posts for this entry, the most recent from 19 August 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

19 Aug 2021, 17:39 UTC56 viewsread 15 August 2026

❬ 𝐅𝐎𝐑𝐌𝐀𝐓 𝐃𝐀𝐅𝐓𝐀𝐑 ❭ Nn + Id : Devisi yang anda ambil : Alasan bergabung : Pegang berapa ch publik ( tidak ada? tidak perlu diisi) : send format to @BEDROSROBOT ((N)). Kalian akan di wawancarai oleh admin, di antaranya Kafathan dan Kazena. Dan kami tidak menerima alasan klasik.

19 Aug 2021, 17:34 UTC62 viewsread 15 August 2026

❬ 𝐀𝐃𝐌𝐈𝐍 𝐏𝐅𝐏/𝐒𝐅𝐒 ❭ ∅1. Gampanglah ya, pasti sudah pada tau bagaimana cara kerja admin pfp/sfs ini. Saya tau kalian pintar. ∅2. Memiliki minimal 10 LPM, tidak memiliki LPM? @listlpm ∅3. Niat dan tidak hanya rajin di awal saja. ∅4. Bersedia untuk melakukan pfp/sfs minimal 2× perminggu. ∅5. Aktive, kreatif, responsive, inovatif, talkactive dan konsisten dalam bertugas. ∅6. Dapat menyanggupi target sfs/psf perharinya

19 Aug 2021, 17:33 UTC71 viewsread 15 August 2026

❬ 𝐀𝐃𝐌𝐈𝐍 𝐌𝐏𝐏𝐒 ❭ ∅1. Paham dan mengerti sistem kerjasama mpps, apabila tidak mengerti ataupun hanya sedikit paham mau untuk belajar. ∅2. Memiliki attitude yang baik. ∅3. Dapat menjaga kepercayaan dan dapat dipercaya. ∅4. Responsif dalam membalas pesan dari partnership. ∅5. Bersedia untuk mencari partnership minimal 10 perminggu. ∅6. Bersedia untuk menghadiri segala party yang di adakan oleh partnership, jika pendi

19 Aug 2021, 17:33 UTC90 viewsread 15 August 2026

❬ 𝐀𝐃𝐌𝐈𝐍 𝐄𝐃𝐈𝐓 ❭ ∅1. Memiliki banyak ide kreatif dan tidak kaku saat berdiskusi. ∅2. Berpengalaman dan mengerti sistem edit mengedit. ∅3. Dapat mengedit poster, twibbon dan kebutuhan channel lainnya. ∅4. Aktive, kreatif, responsive, inovatif, talkactive, dan konsisten dalam bertugas. ∅5. Bersedia untuk open request minimal 2× perminggu. ∅6. Dapat memegang tanggung jawab penuh sebagai admin edit. ∅7. Dapat membagi

19 Aug 2021, 17:32 UTC116 viewsread 15 August 2026

❬ 𝐑𝐔𝐋𝐄𝐒 𝐔𝐓𝐀𝐌𝐀 ❭ ∅1. Tentunya yang pertama adalah NIAT, NIAT dan NIAT. ∅2. Wajib subs @OFCBEDROS dan @SHITPOSTBEDROS ∅3. Tidak hanya niat di awal saja. ∅4. Bukan akun clone atau mata mata. ∅5. Tidak dalam masa L/H/D. ∅6. Dapat berbaur dengan adminlain. ∅7. Bersedia menerima kritik/saran, dan bersedia memberikan saran tidak perlu ragu. ∅8. Bertanggung jawab sebagaimana admin pada umumnya. ∅9. Minimal menghandle 2 sq

19 Aug 2021, 15:54 UTC112 viewsread 15 August 2026
File

put dn : 𖥻𝆬𝐁𝕽𝐃 ( ditaruh dibelakang ) contoh : Raska 𖥻𝆬𝐁𝕽𝐃 ((N)). untuk IDC boleh di taruh di ch.

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

“Arsip Bedros” (@bedrosarsip), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/bedrosarsip.

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.