Telegram RegisterThe public register of Telegram

Channel

RULES HIRMIN DRKTH

@arsipdrkth

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

1subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1001179809324
TypeChannel
Username@arsipdrkth
Created11 May 2021measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/arsipdrkth

Growth

111 August 2026 — 1 subscribers14 August 2026 — 1 subscribers11 August 202614 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:031no change
11 Aug 2026, 03:151first reading

Engagement

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

What this channel posts

Photos
1
Links
1

Lifetime counters from Telegram’s own channel header, read 14 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

18 Oct 2021, 13:36 UTC784 viewsread 14 August 2026
Photo

pakai di ava utama, jika sedang mengikuti hirmin/opmem di lain bisa di grid saja, putdn #CALMINDRKTH

7 Jul 2021, 03:06 UTC≈1,630 viewsread 14 August 2026

ㅤㅤㅤㅤㅤㅤㅤ 𝗙𝗢𝗥𝗠𝗔𝗧 ━━━━━━━━━ ✯ ★ ✰ ━━━━━━━━━ nama & usernme : divisi yang di pilih : memegang berapa ch publik ( bukan ch pribadi ) sebutkan : alasan mengapa mendaftar & memilih divisi itu : jika sudah mengisi format dengan benar send ke @hrmindrkthbot diharap memakai atb yg telah disediakan. n.) trainee selection & interview system. di harapkan untuk yg memilih div edit kirim contoh editan kamu min 2.

7 Jul 2021, 02:04 UTC≈1,670 viewsread 14 August 2026

ㅤㅤ 𝗥𝗨𝗟𝗘𝗦 𝗞𝗢𝗡𝗧𝗘𝗡 / 𝗨𝗣𝗗𝗔𝗧𝗘 ━━━━━━━━━ ✯ ★ ✰ ━━━━━━━━━ ✯ niat niat dan niat ✯ tidak rajin di awal ✯ bisa ngonten min 2 kali dalam seminggu ✯ kreatif dan mempunyai banyak ide ✯ all gender allowed ✯ selalu update setiap berita baru tentang kim taehyung ✯ mempunyai media seperti twitter, instagram, weveres ✯ kembali ke rules utama

7 Jul 2021, 01:57 UTC≈1,700 viewsread 14 August 2026

ㅤㅤㅤㅤㅤㅤ𝗥𝗨𝗟𝗘𝗦 𝗘𝗗𝗜𝗧 ━━━━━━━━━ ✯ ★ ✰ ━━━━━━━━━ ✯ niat niat dan niat ✯ mampu membuat editan untuk kepentingan ch foto, gif ataupun video ✯ kreatif dan mempunyai banyak ide ✯ all gender allowed ✯ bertanggung jawab ✯ dapat menguasai apk edit seperti Vn Capcut Am dan Ibis paint dll ✯ kembali ke rules utama

7 Jul 2021, 01:51 UTC≈1,870 viewsread 14 August 2026

ㅤㅤㅤㅤㅤ𝗥𝗨𝗟𝗘𝗦 𝗦𝗙𝗦 / 𝗣𝗙𝗣 ━━━━━━━━━ ✯ ★ ✰ ━━━━━━━━━ ✯ niat niat dan niat ✯ tidak rajin di awal ✯ bisa sfs 2 ch sekaligus ✯ all gender allowed ✯ bertanggung jawab ✯ dapat sfs 30 subs dalam sehari ✯ bila full akan di beri nokos dari pihak kami ✯ pfp diharapkan mempunyai bot sendiri khusus pfp ✯ dapat pfp seminggu 2 kali ✯ bekerja sesuai jadwal yang di tentukan ✯ kembali ke rules utama

7 Jul 2021, 01:45 UTC≈2,230 viewsread 14 August 2026

ㅤㅤㅤㅤㅤㅤ𝗥𝗨𝗟𝗘𝗦 𝗠𝗣𝗣𝗦 ━━━━━━━━━ ✯ ★ ✰ ━━━━━━━━━ ✯ niat niat dan niat ✯ tidak rajin di awal ✯ all gender allowed ✯ mengerti cara kerja divisi mpps ✯ teliti dan bertanggung jawab ✯ kembali ke rules utama

Showing the 12 most recent of 18 posts we hold for @arsipdrkth. 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 2 registered channels — 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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“RULES HIRMIN DRKTH” (@arsipdrkth), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/arsipdrkth.

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.