Telegram RegisterThe public register of Telegram
Telegram profile photo for DAFTAR HITAM.

Channel

DAFTAR HITAM.

@DaftarHitam

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

30,770subscribers

+407 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001314736671
TypeChannel
Username@DaftarHitam
DescriptionDaftar Hitam: @MoneyFess & @GoldFess Contact: @Nakalrobot
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live5 September 2026
Measurements held28
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/DaftarHitam

Growth

30,36030,77030,5656 August 2026 — 30,363 subscribers7 August 2026 — 30,360 subscribers8 August 2026 — 30,389 subscribers8 August 2026 — 30,404 subscribers9 August 2026 — 30,426 subscribers10 August 2026 — 30,435 subscribers11 August 2026 — 30,449 subscribers12 August 2026 — 30,464 subscribers14 August 2026 — 30,472 subscribers15 August 2026 — 30,493 subscribers16 August 2026 — 30,529 subscribers17 August 2026 — 30,526 subscribers18 August 2026 — 30,556 subscribers19 August 2026 — 30,583 subscribers21 August 2026 — 30,617 subscribers22 August 2026 — 30,635 subscribers23 August 2026 — 30,665 subscribers25 August 2026 — 30,666 subscribers26 August 2026 — 30,678 subscribers27 August 2026 — 30,686 subscribers28 August 2026 — 30,708 subscribers29 August 2026 — 30,717 subscribers30 August 2026 — 30,716 subscribers31 August 2026 — 30,727 subscribers1 September 2026 — 30,734 subscribers2 September 2026 — 30,732 subscribers3 September 2026 — 30,744 subscribers5 September 2026 — 30,770 subscribers6 August 20265 September 2026
28 measurements spanning 30 days, net +407. 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 30,299–30,832 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
5 Sept 2026, 09:1730,770+26
3 Sept 2026, 10:1630,744+12
2 Sept 2026, 06:0730,732-2
1 Sept 2026, 06:1830,734+7
31 Aug 2026, 05:5330,727+11
30 Aug 2026, 03:2530,716-1
29 Aug 2026, 02:0630,717+9
28 Aug 2026, 04:2830,708+22
27 Aug 2026, 05:1730,686+8
26 Aug 2026, 04:1430,678+12
25 Aug 2026, 03:2630,666+1
23 Aug 2026, 23:1530,665+30
22 Aug 2026, 04:3530,635+18
21 Aug 2026, 00:1530,617+34
19 Aug 2026, 21:0330,583+27
18 Aug 2026, 23:5230,556+30
17 Aug 2026, 20:2430,526-3
16 Aug 2026, 20:5630,529+36
15 Aug 2026, 08:2630,493+21
14 Aug 2026, 00:4530,472first reading

Engagement

73 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 61 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.60%
avg views ÷ 30,770 subscribers
Avg views / post
799
58 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
58
of 73 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 September 2026
Posts held73 (4 August 20266 September 2026)
Views total46,362
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Sept 2026, 22:23 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
3,510
Videos
13
Links
2,020

Lifetime counters from Telegram’s own channel header, read 6 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

6 Sept 2026, 13:53 UTC156 viewsread 6 September 2026
Photo

#CASE 2589. PENIPU ROBUX Kronologi : Aku mau beli robux via username dan nemu dia juga ikut ngepm https://t.me/MoneyFess/3461273?comment=9114265 Untuk harga sendiri aku tidak curiga karena temen jual juga dengan harga segitu. Dan setelah pembayaran, akun tiba-tiba diblokir. Saat aku cek lagi, sepertinya dia telah nonaktifkan channel storenya padahal tadi siang-sore masih ada. Penipu/Pelaku Nama: Naoi Username: @na

4 Sept 2026, 08:30 UTC581 viewsread 6 September 2026
Photo

#CASE 2588. PENIPU ROBUX Kronologi: Pada 2 September sore, saya mencari penjual Robux via send di comsect dan sepakat membeli 337 Robux seharga Rp47.000. Setelah bayar via QRIS dan kirim bukti transfer, penjual meminta akun Roblox saya lalu bilang 'proses'. Karena menunggu lama tanpa kepastian, saya mencoba chat pelaku. lalu saya cek rank di channel store pelaku. Banyak akun tidak aktif, dan akun aktif yang saya cha

4 Sept 2026, 04:23 UTC554 viewsread 6 September 2026
Photo

#CASE 2587. PENIPU AKUN IG/INSTAGRAM Kronologi: Pada tgl 27 agust aku nyri acc ig dan ketemu lah di https://t.me/MoneyFess/3445730?comment=8304553 aku hit dia dan aku tnya" dl, ada testi apa g? sm dia di send testinya yg emng cuma bbrp doang. dan ak jg sempet nnya avrek g? trs ktanya bs tpi aku milih g rekber. nah ak nnya jg ke dia bisa nyicil ga? katanya bs, tpi ak agak ragu bkl ditipu trs dia ngeyakinin aku dgn ab

3 Sept 2026, 15:57 UTC481 viewsread 6 September 2026
Photo

#CASE 2586. PENIPUAN JOKI TUGAS. Pada tanggal 1 september saya mencari jasa joki tugas, lalu saya menemukan @kpesempatan lat di mf saya, lalu saya chat utk order jasa dia. Awalnya ragu mau order krn dia minta full pay di awal, terus saya minta testi dikasih sama dia tapi dalam bentuk screenshot, biasanya kan di ch testi. Tapi karena kepepet, saya tetap order dan langsung pay. Setelah pay dia bilang langsung proses,

2 Sept 2026, 15:47 UTC636 viewsread 6 September 2026
Photo

#CASE 2585. PENIPUAN ROBUX. kronologi jadi pagi di hari rabu 2 september aku niat mau cari seller buat beli robux dengan nominal banyak menurutku dan aku lagi cari yang fsr dan bisa inrush kebetulan ada beberapa seller dan bot yang aku chat buat aku jajan du store nya beli robux itu tapi dari banyak nya yang akku chat cuma dia yang bales nya cepet dan ternyata lebih murah, akhirnya aku ajak pake rekber karena emang

1 Sept 2026, 14:50 UTC678 viewsread 6 September 2026
Photo

#CASE 2584 PENIPU MEMULIHKAN AKUN IG Kronologi: Pada tanggal 13 agustus saya mencari jasa untuk memulihkan akun ig saya yang terkena hack, lalu @dakwahW komen di mf saya dan saya chat orang ini untuk menanyakan jasa tersebut. Jujur awalnya agak ragu karena dia berulang kali menanyakan jadi tidaknya saya order ke dia. Karena akun ig tersebut sudah saya gunakan dari 2016 jadi sayang kalo tidak bisa balik, jadi akhirny

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

Posts edited after publishing

@DaftarHitam edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
23 August 2026
Most recent edit
4 September 2026

Forward network

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 35 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“DAFTAR HITAM.” (@DaftarHitam), 30,770 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/DaftarHitam.

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.