Telegram RegisterThe public register of Telegram
Telegram profile photo for DeFi Risk Radar

Channel

DeFi Risk Radar

@DeFiriskradar

On this record: Growth · Engagement · Posts · Citations · Cite this entry

410subscribers

-71 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1004408192208
TypeChannel
Username@DeFiriskradar
CreatedBetween 1 June 2026 and 5 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/DeFiriskradar

Growth

410481445.56 August 2026 — 481 subscribers6 August 2026 — 481 subscribers14 August 2026 — 410 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net -71. 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 399–492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 20:27410-71
6 Aug 2026, 21:15481no change
6 Aug 2026, 19:47481first reading

Engagement

15 posts held, back to 5 July 2026the 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.

ERR · 30 days
65.4%
avg views ÷ 410 subscribers
Avg views / post
268
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 15 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 17 July 2026
Posts held15 (5 July 202617 July 2026)
Views total536
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 19:47 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.

Recent posts

17 Jul 2026, 14:10 UTC273 viewsread 6 August 2026
Photo

0xab0cA0a9F3AB778eb5C7bc8AeE599761Cd9eddC1 Stau off honeypot

17 Jul 2026, 13:50 UTC263 viewsread 6 August 2026
Photo

HONEYPOT / MALICIOUS TOKEN 0xc996e514b784169Ee4E6d8296659E89613768981 STAY CLEAR

12 Jul 2026, 00:01 UTC27 viewsread 6 August 2026
Photo

Swing is a malicious token launch on the the v4 paid 0x89Cf5C1b3bc04ea54795B37A85258F1dfC9c31dF Report to blockaid and flagged by blockaid Be careful

11 Jul 2026, 23:46 UTC170 viewsread 6 August 2026
Photo

🚨HONEYPOT ALERT – $BLINK Chain: Ethereum CA: 0x6340B52F00ffAa6547eF9e95646Ef2E4f2AA942c ⚠️ Flagged as a HONEYPOT. Buyers may not be able to sell. Owner wallet controls 48.75% of the supply. Trade at your own risk and always verify before aping. Stay safe. DYOR.

11 Jul 2026, 20:38 UTC169 viewsread 6 August 2026
Video

DEFI RISK RADAR $FrogCat has landed on our radar. The chart shows highly erratic price action with repeated spikes and reversals that may indicate heavy intervention rather than sustained organic buying. On top of that, multiple community members have linked the deployer/team to previous rug pulls. We have not verified those allegations independently, but the combination of the chart behavior and those reports is

10 Jul 2026, 00:19 UTC168 viewsread 6 August 2026
Photo

0xa2D6e595Df8b7130458eC30963C0933D105085C9 Stay out!! DM @ethdisciple to report or Fix An Issue

10 Jul 2026, 00:08 UTC204 viewsread 6 August 2026
Photo

$STARMIND MALICIOUS 0xa2D6e595Df8b7130458eC30963C0933D105085C9 ‼️⚠️

7 Jul 2026, 10:12 UTC171 viewsread 6 August 2026
Video

🚨MALICIOUS TOKEN ALERT – $GOOB 🚨 Our security review has flagged $GOOB as a malicious token. Interacting with this contract could expose you to significant risks, including potential loss of funds. ⚠️Avoid buying, swapping, or interacting with this token until it has been thoroughly verified. Contract Address: 0x93ec8c50db87468f83037c3a135b54bab5a0749b 🔍Always verify token contracts before investing. Don’t let hy

7 Jul 2026, 10:09 UTC171 viewsread 6 August 2026
Video

🚨POTENTIAL HONEYPOT ALERT – $DISABULL 🚨 Our initial review has flagged $DISABULL as a potential honeypot. There are concerning signs that could prevent buyers from selling their tokens after purchase. ⚠️We strongly advise everyone to exercise extreme caution before interacting with this token. Do not FOMO into the trade without thoroughly reviewing the contract and verifying the risks yourself. 📊 DexScreener: http

7 Jul 2026, 00:46 UTC165 viewsread 6 August 2026
Video

🚨MALICIOUS TOKEN ALERT 🚨 Chain: Ethereum CA: 0x5c36660fd54f1775234c95d8af2faed1c18cbeea ❌FLAGGED AS MALICIOUS This contract has been flagged as malicious. Avoid buying, approving, or interacting with this token until it has been independently verified as safe. ⚠️ Stay vigilant. Always .

7 Jul 2026, 00:43 UTC160 viewsread 6 August 2026
Video

MALICIOUS TOKEN ALERT Token: 0xwormhole Chain: Ethereum CA: 0x5e5B5a53Aa83C9AA0441E939F4075F95A7A99DbB ❌ BLOCKAID FLAGGED THIS TOKEN AS MALICIOUS Do NOT buy, trade, or interact with this contract. Stay safe and DYOR. ⚠️

Showing the 12 most recent of 15 posts we hold for @DeFiriskradar. 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

Citation-graph rank — 1,228,460 of 1,481,217entries 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.

Mentions

Named by 1 registered channel — 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.

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

“DeFi Risk Radar” (@DeFiriskradar), 410 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/DeFiriskradar.

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.