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

Channel

DAFTAR HITAM.

@DaftarHitam

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

31,424subscribers

+1,061 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 live23 October 2026
Measurements held48
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/DaftarHitam

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

30,36031,42430,8926 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 subscribers8 September 2026 — 30,787 subscribers11 September 2026 — 30,852 subscribers13 September 2026 — 30,885 subscribers14 September 2026 — 30,928 subscribers16 September 2026 — 30,955 subscribers18 September 2026 — 31,019 subscribers25 September 2026 — 31,006 subscribers4 October 2026 — 31,014 subscribers8 October 2026 — 31,118 subscribers13 October 2026 — 31,195 subscribers14 October 2026 — 31,240 subscribers15 October 2026 — 31,261 subscribers16 October 2026 — 31,267 subscribers17 October 2026 — 31,278 subscribers18 October 2026 — 31,297 subscribers19 October 2026 — 31,307 subscribers20 October 2026 — 31,343 subscribers21 October 2026 — 31,372 subscribers22 October 2026 — 31,409 subscribers23 October 2026 — 31,424 subscribers6 August 202623 October 2026
48 measurements spanning 78 days, net +1,061. 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,200–31,584 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
23 Oct 2026, 19:1831,424+15
22 Oct 2026, 17:1731,409+37
21 Oct 2026, 09:0031,372+29
20 Oct 2026, 04:1931,343+36
19 Oct 2026, 07:4031,307+10
18 Oct 2026, 08:1731,297+19
17 Oct 2026, 09:5531,278+11
16 Oct 2026, 12:5631,267+6
15 Oct 2026, 15:3731,261+21
14 Oct 2026, 12:3731,240+45
13 Oct 2026, 00:3131,195+77
8 Oct 2026, 13:5831,118+104
4 Oct 2026, 04:0131,014+8
25 Sept 2026, 08:1531,006-13
18 Sept 2026, 21:5831,019+64
16 Sept 2026, 16:3730,955+27
14 Sept 2026, 19:1830,928+43
13 Sept 2026, 02:1730,885+33
11 Sept 2026, 06:3930,852+65
8 Sept 2026, 13:1930,787first reading

Engagement

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

ERR · 30 days
1.72%
avg views ÷ 31,424 subscribers
Avg views / post
539
78 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
78
of 172 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 23 October 2026
Posts held172 (4 August 2026 – 23 October 2026)
Views total42,068
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Oct 2026, 03:40 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,610
Videos
≈13
Links
≈2,070

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

23 Oct 2026, 01:56 UTC235 viewsread 24 October 2026
Photo

#CASE 2636. PENIPUAN AI CLAUDE. Kronologi: Aku & temenku mau beli AI claude, dia diawal ga bilang ada deposit dll hanya kirim pl. Aku & temenku bayar lah 50k tbtb disuruh bayar deposit sebesar 50k, temenku yang udh login email tbtb ke lock dn bayar 100 untuk unlock, aku minta refund aja dia tolak karena katanya dari website gt. Dan tbtb block+ clear roomchat Penipu/Pelaku Nama: Neira Username: @nayyvlune Id account…

23 Oct 2026, 01:42 UTC159 viewsread 24 October 2026
Photo

KORBAN KEDUA. PENIPUAN ADOBE PHOTOSHOP. Kronologi: aku lagi urgent bgt cari2 adobe photoshop untuk nugas (https://t.me/MoneyFess/3534614) gak mikir panjang langsung beli aja karena beneran kepepet. terus after tf katanya proses tapi prosesnya lama karena pas dia komen di foto pertama grid itu prosesnya cuma 15-45 menit. terus, pas aku cek gaada results, testi, channel store sekalipun tuh gaada. udah spamchat dan ga…

21 Oct 2026, 15:18 UTC353 viewsread 24 October 2026
Photo

#CASE 2635. PENIPUAN JOKI TUGAS. Kronologi: niatnya mau joki tugas karna emg gada laptop deadline pagi jam 9, aku cek cek cs orang orang ajaa emg salah aku ya menfess dulu, terus ketemu lah menurut aku oke ajaa (keliatannya amanah) aku sempet nanya "ada result atau hasil jadinya gak di ch" dia bilang gada baru mau buka bisnis gitu katanya terus harga aku emg di anjlokin (bagian bbc ini di hapus sama dia) udah paymen…

19 Oct 2026, 11:45 UTC494 viewsread 22 October 2026
Photo

#CASE 2634. PENIPUAN CONVERT Kronologi: Awalnya saya memang mencari jasa convert untuk membayar makanan. kemudian saya menemukan pelaku di https://t.me/MoneyFess/3538954?comment=12837623 dan saya tertarik karena melihat testi yang sangat meyakinkan. Setelah saya payment pelaku langsung block akun saya, saya gedor rc nya di akun yang lain, di block, teman saya gedor akun nya juga ikut di block. Kronologi lengkap @wf…

19 Oct 2026, 04:24 UTC442 viewsread 22 October 2026
Photo

#CASE 2633. NFT USERNAME TELEGRAM Kronologi: Pada 17 Oktober 2026, saya menghubungi @nawraya untuk menanyakan rate NFT username Telegram seharga Rp135.000. Sebelum transaksi, saya meminta bukti transaksi sebelumnya dan seller mengirimkan screenshot My Bid History dari Fragment. Setelah sepakat, saya membayar melalui QRIS. Setelah pembayaran, saya mengikuti instruksi seller untuk memproses username @ shedior. Namun…

19 Oct 2026, 03:27 UTC378 viewsread 22 October 2026
Photo

#CASE 2632. PENIPUAN NOKTEL V2L Kronologi: aku lagi nyari noktel di @MoneyFess dan lihat komen pelaku di https://t.me/MoneyFess/3540737?comment=12925378 jadi aku hit. Pas aku hit pelakunya fast respon banget sampe payment. Giliran pas udah kelar bayar tbtb slr banget. Aku cek jejak dia di MoneyFess dikit dan dia online, komen di menfess lain tapi ga balas chatku. Btw ini ada qris pelaku terlampir dan bukti pembayara…

Showing the 12 most recent of 172 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 7 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
12 October 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 38 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 23 October 2026 — this entry's latest reading, not the date you are reading this.

“DAFTAR HITAM.” (@DaftarHitam), 31,424 subscribers as measured 23 October 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.