Channel
@hdscammer
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
617subscribers
-9,444 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001425870658 |
|---|---|
| Type | Channel |
| Username | @hdscammer |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/hdscammer |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 06:21 | 617 | -8,909 |
| 17 Sept 2026, 07:18 | 9,526 | -1 |
| 13 Sept 2026, 05:40 | 9,527 | -27 |
| 9 Sept 2026, 10:20 | 9,554 | -46 |
| 3 Sept 2026, 16:20 | 9,600 | -83 |
| 31 Aug 2026, 04:33 | 9,683 | -87 |
| 28 Aug 2026, 05:17 | 9,770 | -29 |
| 25 Aug 2026, 12:48 | 9,799 | -34 |
| 22 Aug 2026, 13:42 | 9,833 | -14 |
| 19 Aug 2026, 11:28 | 9,847 | -37 |
| 16 Aug 2026, 19:03 | 9,884 | -17 |
| 13 Aug 2026, 07:26 | 9,901 | -74 |
| 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 |
8 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 36 pages 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 8 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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: @usdt66999999 , @ipttttt group [ @abcinrtousdt ] Identity: inr usdt exchange scam Amount Involved (USDT / INR): 148.5usdt Scammer UPI / Wallet Address: THe3TLvyd7QpkLuKYL1VXfNB42UwfQoo8K 📌 Incident Summary: funds sending and run, asking big order try to scam more ⚠️Please be extremely cautious of anyone who sends funds before the transaction details, exc…
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @Parbhu67 @USDTjiejie Identity: inr usdt exchange scam Amount Involved (USDT / INR): 41088inr Scammer UPI / Wallet Address: 7P916K8005@mairtel 📌 Incident Summary: I TRUSTED HIM AND PAID INR but after few minutes he deleted chat and blocked me i have proofs so i am posting it if someone find any thing about him please let me know @Nottillnow if someone ca…
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @ACEPAYGir1 Identity: prepay scam Amount Involved (USDT / INR): 505USDT Scammer UPI / Wallet Address: 0x25481E6Df8fd302E6611759bdEE4363Bab450534 📌 Incident Summary: usdt exchange to fund hacker and mix fund he take usdt and blocked me ⚠️Please be extremely cautious of anyone who sends funds before the transaction details, exchange rate, and payment terms …
#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 8 most recent of 8 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Huidu.io Scam Alert ⚠️” (@hdscammer), 617 subscribers as measured 26 September 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.