Channel
@hdscammer
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9,975subscribers
-86 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001425870658 |
|---|---|
| Type | Channel |
| Username | @hdscammer |
| Description | Scam Exposure Channel | Huidu.io Official This channel is dedicated to exposing scams, fraudulent providers, and unsafe transactions within the iGaming and digital services community. Report: @HDtyler9 Escrow: @HuiduEscrow Chat : @huidu_india |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/hdscammer |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 02:26 | 9,975 | -40 |
| 9 Aug 2026, 01:40 | 10,015 | -29 |
| 8 Aug 2026, 00:16 | 10,044 | -17 |
| 7 Aug 2026, 06:46 | 10,061 | first reading |
5 posts held, back to 21 June 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 15 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 5 (21 June 2026 – 10 August 2026) |
| Views total | 230 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 14:37 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.
Lifetime counters from Telegram’s own channel header, read 12 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @lakshay4192 @Rocky00115 @nrpay888 @Mufasa159 Identity: N R PAY TECHNOLOGY BHOPAL (OPC) PRIVATE LIMITED Website: https://nrpay.co.in/ Laksya WhatsApp: +97152803 4192 Amount Involved (USDT / INR): 5 Lakh (5000 USDT) Scammer UPI / Wallet Address: nrpaytechnology355746.aps@sbi rausiaxpriva359542.aps@sbi rausiaxpriv359542.apy@kotakpay 📌 Incident Summary: We ar…
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @matias6aga Identity: data selling scam Amount Involved (USDT / INR): 600usdt Scammer UPI / Wallet Address: TBW2cnedgFcvTXtK138jywC3bdoSStBKno 📌 Incident Summary: TOOK payment and after sending hash, deleted and blocked me. suppose to send over 10k database of contacts ⚠️ Please be extremely cautious of anyone who sends funds before the transaction detai…
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @LucidPay_Kenzai -He is main fraud who cheated on me @LucidPay_Garry @LucidPay_Spencer - New Username : @Spencer_0138 @LucidPay_Anny - New Username : @Anny_3892 Identity: inr usdt exchange scam Amount Involved (USDT / INR): 5000u Scammer UPI / Wallet Address: 📌 Incident Summary: Promised me that they we will send Gaming Fund in exchange of USDT but After…
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @GOPAY88888 @gopay918 Identity: deposit scam Amount Involved (USDT / INR): 4000u Scammer UPI / Wallet Address: TPKSb2oqSTKERYf9SruaEadPNTNoKf4Xcu 📌 Incident Summary: Long time business with Gopay,but they cheat with me and my friend circle, lots of usdt cheated by us My friend lose almost 11000 usdt and i lose 4000usdt.. He offer me added my wallets but n…
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @HKPAYaXin @KOOLPAY_Ling @KOOLPAY_XY @koolpayddd @KOOLPAY666 @KOOLPAYxiaoyu @KOOLPAYxiaoyu @KOOLPAYss @koolpayqingyan338 @koolpayqingyan338 @KOOLPAYahao1 @ZQpay0001 @ZQpay0002 @ZQPAY0005 @ZQPAY0003 Identity: deposit scam Amount Involved (USDT / INR): 4500u Scammer UPI / Wallet Address: TK9hydHABp9MCPEibLujSjijr3RfvtoA5M 📌 Incident Summary: The victim report…
Showing the 5 most recent of 5 posts we hold for @hdscammer. 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.
Citation-graph rank — 790,451 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Huidu.io Scam Alert ⚠️” (@hdscammer), 9,975 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/hdscammer.
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.