#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @Iceberg_cj Identity: inr usdt exchange scam Amount Involved (USDT / INR): 722U Scammer UPI / Wallet Address: TK69c3JiHQfysV8kwuEnFDYvy8AM4m9Dqk 📌 Incident Summary: This individual claims to be the owner of a Chinese company and convinces people that he operates a legitimate business, asserting that he requires bank accounts to handle various stock and ga…

Channel
Huidu.io Scam Alert ⚠️
@hdscammer
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
5,706subscribers
-4,355 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001425870658 |
|---|---|
| Type | Channel |
| Username | @hdscammer |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/hdscammer |
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 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 14:58 | 5,706 | -667 |
| 9 Nov 2026, 22:59 | 6,373 | -440 |
| 6 Nov 2026, 21:56 | 6,813 | -34 |
| 3 Nov 2026, 18:39 | 6,847 | +2 |
| 31 Oct 2026, 15:04 | 6,845 | -2 |
| 28 Oct 2026, 13:26 | 6,847 | +3 |
| 25 Oct 2026, 06:07 | 6,844 | -8 |
| 22 Oct 2026, 14:26 | 6,852 | -7 |
| 19 Oct 2026, 12:39 | 6,859 | -9 |
| 16 Oct 2026, 02:58 | 6,868 | -5 |
| 13 Oct 2026, 13:29 | 6,873 | -38 |
| 7 Oct 2026, 19:16 | 6,911 | +6,294 |
| 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 | first reading |
Engagement
13 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 46 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 7.05%
- avg views ÷ 5,706 subscribers
- Avg views / post
- 402
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 13 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.
| Window | Rolling 30 days · latest post in window 27 October 2026 |
|---|---|
| Posts held | 13 (21 June 2026 – 27 October 2026) |
| Views total | 402 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 13:49 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
- Video runtime
- 37s
- Average length
- 12s
Measured directly from 3 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @Rocky7361 telegram number : +919797137290 Account link : +919086116535 second account : +918899081450 Identity: otp work scam by clint Amount Involved (USDT / INR): 50000inr Scammer UPI / Wallet Address: Scammer account deatils : Account number: 0534041000000381 Holder name : mohsin Ahmad Bhat User id:MOHSIN11121208 Second account :Jk银行 持有人姓名:Amir Hussain…
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @Queen77293 Identity: usdt inr exchange scam Amount Involved (USDT / INR): 30000inr Scammer UPI / Wallet Address: 📌 Incident Summary: asked advance to exchange hacker fund to USDT advance inr we send him 30,000, he blocked us after receiving it (Describe what happened Victim @ACEPAY1011 ⚠️Please be extremely cautious of anyone who sends funds before th…
🎮 India’s cricket market is heating up. With 2027 approaching, traffic, brands and business opportunities around cricket will only get more competitive. Get in early with HUIDU: ✔️ Verification & Brand Trust ✔️ Multi-Channel Exposure ✔️ Clear Transaction Records Build trust early. Convert faster. 🌐 HUIDU.in Connecting India’s iGaming Ecosystem ✅ OPEN YOUR Huidu.io Escrow Group Contact: @hdtyler9
#Scam 🚨 [SCAM ALERT] New scammer reported User handle: @PayEurasia Identity: commission failed to pay Amount Involved (USDT / INR): 6000usdt Scammer UPI / Wallet Address: 📌 Incident Summary: (PayEurasia offered me a Nagad Unlimited agent wallet and promised a 4.5% commission for the transactions processed through the wallet. They also clearly informed me that the commission would be paid between 8:00 PM and 1…
#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…
Showing the 12 most recent of 13 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
@hddb_bg · 13,52512 postshuidu.in |Gaming 🇮🇳【GGC2027】
@huidu_india · 33,50912 postsHuidu.io Global iGaming🎰【GGC2027】
@huiduGlobal · 21,36312 postsHuidu.io Escrow Service - Terms & Rules
@HUiDUGuarantee · 9,01312 postsINR Long Term Exchange USDT
@abcinrtousdt · 4,4931 postReaeeman
@matias6aga · 11 post
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.
Handles this channel named that no longer answer
- Dead references
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 3
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@hdscammer named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 4 posts, 8 August 2026 – 15 August 2026 · confirmed gone 14 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 4 posts, 8 August 2026 – 15 August 2026 · confirmed gone 15 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 4 posts, 8 August 2026 – 15 August 2026 · confirmed gone 15 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 November 2026 — this entry's latest reading, not the date you are reading this.
“Huidu.io Scam Alert ⚠️” (@hdscammer), 5,706 subscribers as measured 15 November 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.