Telegram RegisterThe public register of Telegram
Telegram profile photo for Criminal Cyber.

Channel

Criminal Cyber.

@tindakkejahatan

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

81subscribers

+43 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-1002373367000
TypeChannel
Username@tindakkejahatan
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live15 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/tindakkejahatan

Growth

388159.57 August 2026 — 38 subscribers10 August 2026 — 38 subscribers15 August 2026 — 56 subscribers22 August 2026 — 74 subscribers29 August 2026 — 78 subscribers7 September 2026 — 77 subscribers15 September 2026 — 81 subscribers7 August 202615 September 2026
7 measurements spanning 39 days, net +43. 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 32–87 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 07:1881+4
7 Sept 2026, 12:1977-1
29 Aug 2026, 03:5978+4
22 Aug 2026, 19:2674+18
15 Aug 2026, 15:1456+18
10 Aug 2026, 20:4538no change
7 Aug 2026, 03:4738first reading

Engagement

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

Recent posts

10 Aug 2026, 11:52 UTC380 viewsread 10 August 2026

Korban ketujuh Hari dan Tanggal Kejadian: August 1, 2026 Nama dan Username Pelaku: D @Donjuanitoh / @Dameraraw (ID: 8611257066) Laporan: Unpleasant behavior Link Menfess: - Kronologi Kejadian: Previously, i never left a single trace on those friendship menfess anywhere but all of a sudden someone messaged me asking to be friends, ini aneh karena terakhir aku aktif di base tersebut July 13, 2026. Sempat aku konfront

10 Aug 2026, 11:45 UTC404 viewsread 10 August 2026

Hari dan Tanggal Kejadian: 03 Juni 2026 Nama dan Username Pelaku: Loren @lorensks (8692139374) Laporan: Tindak laku tidak menyenangkan Link Menfess: - Kronologi Kejadian: aduh aku jujur lupaa kayanya bukan berawal dari ducy karena waktu itu posisinya aku lagi sering mangkal di beberapa base jadi ga bisa mastiin apakah itu dari ducy atau ngga jadi awalnya itu kan tiba tiba dia ini chat aku dengan bilang katanya mood

10 Aug 2026, 07:32 UTC413 viewsread 10 August 2026

Korban keenam Nama dan Username Pelaku: D @Donjuanitoh (ID: 8611257066) Laporan: sexual harrasement Link Menfess: - Kronologi kejadian: Awalnya dari sini, ducy emang lg sesi send bio dan gua ada send. Ada beberapa reach out gua termasuk dia, chatlah dia begini. Pertamanya dia gak tanya ke ranah NSFW atau FWA, cuma dia sering kyk say hi say hi aja atau sesekali dia manjang topik. Gua bales seadanya karena udah merasa

10 Aug 2026, 07:18 UTC303 viewsread 10 August 2026

Korban ketiga Tanggal kejadian: 28 July 2026 Kejadian: mungkin aku gabisa bikin laporan seperti yang lainnya karena memang bukan dari dunia cyber melainkan aku lat mf fwa BIASA di salah satu menfess pada base lain. beliau hit aku dan memang mengaku kalau bukan sender dari menfess tersebut. dari awal kenalan dia minta untuk kenalan pakai foto mukaku lalu aku tolak dia dan dia bilang “yah kecewa” dari situ kita chat b

10 Aug 2026, 06:04 UTC347 viewsread 10 August 2026

Korban kedua Hari dan Tanggal Kejadian: Sabtu, 25 Juli 2026 Nama dan Username Pelaku: Lan @Perkkeo Laporan: Sexual harassment Link Menfess: - Kronologi Kejadian: jadi aku awalnya mangkal di salah satu base, pure mangkal dan sama sekali nggak pernah lat di mf konteks nsfw, tiba tiba orang ini dateng dengan chat seperti di foto, aku kira dia memang suka, salfok jadi aku apresiasi, turns out dia ada tujuan aneh yang bi

10 Aug 2026, 05:26 UTC≈1,080 viewsread 10 August 2026

Hari dan Tanggal Kejadian: Friday, 31 July 2026 Nama dan Username Pelaku: Lan & @Perkkeo (id: 6346433947) Laporan: Sexual harassment Link Menfess: - Kronologi Kejadian: Awalnya aku di reach out sama seseorang yang mengaku melihat aku di Ducy, FYI aku tidak pernah leaving trace ke menfess yang mencari FWA with NSFW things mana pun. Lalu ybs secara tiba-tiba reply story aku seperti yang terlampir, di awal aku sudah mer

10 Aug 2026, 04:04 UTC446 viewsread 10 August 2026
Photo

Setelah adanya laporan ini, terbukti pelaku langsung melarikan diri dengan menghapus akunnya. Tapi tetap, tolong untuk terus siaga, hindari, dan apabila ada aktivitas tidak menyenangkan dan akun yang menyerupai pelaku mohon segera laporkan kepada kami. Kepada para korban, dari hati terdalam kami menyampaikan kesedihan dan turut merasakan kekecewaan atas pengalaman buruk yang diterima dari tindak laku perilaku. Semoga

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Criminal Cyber.” (@tindakkejahatan), 81 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/tindakkejahatan.

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.