Telegram RegisterThe public register of Telegram

Channel

反欺诈-曝光频道

@scam472

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

360subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002357917434
TypeChannel
Username@scam472
Description如果你在Telegram交易遭遇诈骗 请向:@scam472Bot 投稿(注意投稿规则) 核实后会公之于众。 tg交易有风险,请万分谨慎!
Created9 March 2025measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/scam472

Growth

3607 Aug 2026, 15:22 — 360 subscribers8 Aug 2026, 06:33 — 360 subscribers7 Aug 2026, 15:228 Aug 2026, 06:33
2 measurements taken within a single day. 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 359–361 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 06:33360no change
7 Aug 2026, 15:22360first reading

Engagement

5 posts held, back to 9 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 5 posts for this entry, the most recent from 3 July 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
7
Links
2

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

Reaction mix

23 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 56.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1356.5%
521.7%
👏313.0%
😢14.35%
🤬14.35%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 3 of the 5 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 23reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 9 March 2025 to 3 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

3 Jul 2025, 04:59 UTC541 views6 reactionsread 8 August 2026
Photo

#国人骗子 受害人:匿名 被骗金额:48.1USDT 具体事项:我在尼日利亚羊毛群聊发布需要App Store礼品卡的信息,骗子找到我行骗。付款后就拖延和跑路。之后发现此人在几个月前就进行过类似诈骗,甚至没有更改头像与名称(根据群友提供的信息)。 更多聊天记录点我查看 ⚠️诈骗犯用户名(可能随时更改):@xx_528 ⚠️tg永久链接:tg://user?id=6262064680 ❔曝光原因: 聊天记录存在,付款记录存在,支付后诈骗犯以各种理由不发货,企图继续诈骗。真实诈骗率:99.9%,曝光成功。 曝光/申诉频道:@scam472 曝光投稿:@scam472Bot

👍6

29 Mar 2025, 03:10 UTC≈1,120 views10 reactionsread 8 August 2026
Photo

#尼日利亚骗子 受害人:匿名 被骗金额:7USDT 具体事项:尼哥黑鬼骗子,准备买10000naira ngn gift card付完钱就删消息跑路。 ⚠️诈骗犯用户名(可能随时更改):@hellstarq ⚠️tg永久链接:tg://user?id=7262030444 ❔曝光原因: 聊天记录存在,付款记录存在,支付后诈骗犯24小时未有任何回复,消息未读,真实诈骗率:90%,曝光成功。 曝光/申诉频道:@scam472 曝光投稿:@scam472Bot

👍5👏3🤬1😢1

9 Mar 2025, 07:42 UTC≈2,980 views7 reactionsread 8 August 2026

在 @mdmhome / @hezu2 或相似群交易时遇 到诈骗 向 @scam472Bot 投稿,曝光骗子 注意事项: 1️⃣仅处理交易诈骗(收钱不办事),不处理交易纠纷。 2️⃣举报范围在 @mdmhome / @hezu2 或相似群,而非全平台。

5👍2

Showing the 5 most recent of 5 posts we hold for @scam472. 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.

Mentions

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

“反欺诈-曝光频道” (@scam472), 360 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/scam472.

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.