Channel
@whalealertsio
On this record: Growth · Engagement · Posts · Citations · Cite this entry
438subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003929408513 |
|---|---|
| Type | Channel |
| Username | @whalealertsio |
| Created | Between 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/whalealertsio |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 20:38 | 438 | -4 |
| 8 Aug 2026, 05:05 | 442 | no change |
| 8 Aug 2026, 04:23 | 442 | +2 |
| 7 Aug 2026, 19:09 | 440 | first reading |
19 posts held, back to 7 August 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 1 pageof 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 8 August 2026 |
|---|---|
| Posts held | 19 (7 August 2026 – 8 August 2026) |
| Views total | 10,457 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 05:05 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.
WHALE ACCUMULATES 1.35K $BTC WORTH $87M A whale received 1,345.55 $BTC (~$87.36M) over the last day, including 614.95 $BTC from Galaxy Digital. Address: 167YVrHeroj8yuiH8ZmMFazQjn5sPjKBa7 ~ @whalealertsio
Binance - #SOXLB - Unusual selling activity 946K USDT in 13 minutes (11%) P: 139 🔴 (0.38%) 24H Vol: 9.53M USDT Last alert: 15 hours ago (5/7D)
Binance - #XLM - Unusual buying activity 532K USDT in 22 seconds (11%) P: 0.1636 ❇️ (0.68%) 24H Vol: 5.16M USDT Last alert: 14 hours ago (3/7D)
WHALE WITHDRAWS 30,000 $ETH FROM COINBASE A whale accumulated and withdrew 30K $ETH (~$57.21M) from Coinbase Prime and split the funds across three fresh wallets. Addresses: 0x53242ee9951DA20d5C6CF587D9753042249E23D4 0x7A71F135F23F4a84b7658788541F6a22a75644e6 0x40187986A4228e2dd1f3E319d5716d81250528a5 ~ @whalealertsio
Binance - #DASH - Unusual buying activity 629K USDT in 12 seconds (39%) P: 30.68 🔴 (0.94%) 24H Vol: 2.23M USDT Last alert: 3 days ago (2/7D)
FRESH WALLET WITHDRAWS $10.69M $HYPE FROM COINBASE A newly created wallet withdrew 197.36K $HYPE (~$10.69M) from Coinbase 1 hour ago. Address: 0xf6000bB2E7579D4eAa741dDb0195187325380c3E ~ @whalealertsio
WHALE BUYS $95.7M $ETH FROM FIDELITY A whale bought 50K $ETH (~$95.73M) from a Fidelity-linked wallet yesterday, then moved 36.53K $ETH (~$69.94M) to a new address 3 hours ago. Based on the whale’s previous transaction pattern, these funds may later be sent to Coinbase for sale. Address: 0x951A4d24BA0F038B9872F253C380836Db9E67D53 ~ @whalealertsio
BLACKROCK BOUGHT NEARLY HALF A BILLION DOLLARS OF BITCOIN THIS WEEK Their IBIT Bitcoin ETF withdrew 1.84K $BTC (~$118.9M) from Coinbase Prime today. Weekly accumulation: 7.32K $BTC (~$478.5M) Entity:
🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 179,527,736 $USDC (179,538,687 USD) transferred from Unknown Whale 1 to #Aave
Binance - #WBTC - Unusual buying activity 546K USDT in 7 minutes (11%) P: 64,930 ❇️ (0.03%) 24H Vol: 5.27M USDT Last alert: 6 hours ago (7/7D)
🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 179,500,000 $USDC (179,511,039 USD) transferred from #Aave to Unknown Whale 1
🚨 🚨 🚨 771 $BTC (50,072,816 USD) transferred from #Kraken to unknown wallet
Showing the 12 most recent of 19 posts we hold for @whalealertsio. 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 — 1,313,451 of 1,480,688entries 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 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“WhaleAlerts.io” (@whalealertsio), 438 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/whalealertsio.
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.