Telegram RegisterThe public register of Telegram
Telegram profile photo for Alephium Whales

Channel

Alephium Whales

@alphwhalesalert

On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

293subscribers

-5 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-1001672968330
TypeChannel
Username@alphwhalesalert
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/alphwhalesalert

Growth

293298295.57 August 2026 — 298 subscribers8 August 2026 — 298 subscribers14 August 2026 — 297 subscribers22 August 2026 — 294 subscribers29 August 2026 — 293 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net -5. 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 292–299 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 17:15293-1
22 Aug 2026, 13:16294-3
14 Aug 2026, 13:48297-1
8 Aug 2026, 08:04298no change
7 Aug 2026, 09:36298first reading

Engagement

20 posts held, back to 16 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
8.35%
avg views ÷ 293 subscribers
Avg views / post
24.5
11 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 20 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 2 August 2026
Posts held20 (16 July 20262 August 2026)
Views total269
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 08:04 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

2 Aug 2026, 19:07 UTC26 viewsread 8 August 2026

💸 💸 💸 💸 💸 399.00K $ALPH transferred (0 -> 0) 17W...69X to Bitget.com (15.50K USDT) TX link Featured article: Asset Permission System

2 Aug 2026, 18:53 UTC26 viewsread 8 August 2026

💸 💸 💸 💸 💸 200.00K $ALPH transferred (0 -> 0) 17W...69X to Bitget.com (7.87K USDT) TX link Featured article: Time to Finality

2 Aug 2026, 18:51 UTC25 viewsread 8 August 2026

🟢 🟢 🟢 🟢 🟢 199.00K $ALPH transferred (2 -> 0) Mexc.com to 17W...69X (7.83K USDT) TX link Featured article: Account Model meets UTXO

2 Aug 2026, 18:51 UTC26 viewsread 8 August 2026

🟢 🟢 🟢 🟢 🟢 200.00K $ALPH transferred (2 -> 0) Mexc.com to 17W...69X (7.87K USDT) TX link Featured article: Alephium by Coingecko

2 Aug 2026, 18:37 UTC22 viewsread 8 August 2026

🟢 🟢 🟢 🟢 🟢 200.00K $ALPH transferred (2 -> 0) Mexc.com to 17W...69X (7.79K USDT) TX link Featured article: Asset Permission System

2 Aug 2026, 02:18 UTC24 viewsread 8 August 2026

💸 💸 💸 💸 💸 107.64K $ALPH transferred (0 -> 0) 17J...4nH to Bitget.com (3.88K USDT) TX link Featured article: Transactions Per Second (TPS)

2 Aug 2026, 01:59 UTC23 viewsread 8 August 2026

🟢 🟢 🟢 🟢 🟢 107.64K $ALPH transferred (2 -> 0) Gate.io to 17J...4nH (3.87K USDT) TX link Featured article: Asset Permission System

1 Aug 2026, 21:03 UTC24 viewsread 8 August 2026

183.29K $ALPH transferred (2 -> 0) 1Fx...wx3 to 12n...tD9 (6.57K USDT) TX link Featured article: Alphred Virtual Machine

1 Aug 2026, 12:04 UTC24 viewsread 8 August 2026

180.00K $ALPH transferred (2 -> 3) 3cU...w:2 to 14H...WDu (6.53K USDT) TX link Featured article: Transactions Per Second (TPS)

1 Aug 2026, 08:17 UTC24 viewsread 8 August 2026

🟢 🟢 🟢 🟢 🟢 180.00K $ALPH transferred (2 -> 2) Mexc.com to 3cU...w:2 (6.32K USDT) TX link Featured article: Account Model meets UTXO

1 Aug 2026, 07:29 UTC25 viewsread 8 August 2026

322.87K $ALPH transferred (2 -> 3) 3cU...w:2 to 14H...WDu (12.44K USDT) TX link Featured article: Alphred Virtual Machine

30 Jul 2026, 19:32 UTC27 viewsread 8 August 2026

💸 💸 💸 💸 💸 100.09K $ALPH transferred (1 -> 2) 112...UmQ to Gate.io (3.84K USDT) TX link Featured article: Stateful UTXO

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

XDAO | Official channel 💠
@xdaoapp · 2,291,332
Telegram ranks this channel #31 of 76 here — alongside 75 others — read 23 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Alephium Whales” (@alphwhalesalert), 293 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/alphwhalesalert.

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.