Telegram RegisterThe public register of Telegram

Channel

CryptoQuant Alert

@cryptoquant_alert

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

71,894subscribers

-154 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001246846205
TypeChannel
Username@cryptoquant_alert
Created27 July 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/cryptoquant_alert

Growth

71,89472,04871,9716 August 2026 — 72,048 subscribers6 August 2026 — 72,048 subscribers7 August 2026 — 72,042 subscribers8 August 2026 — 72,007 subscribers9 August 2026 — 71,990 subscribers10 August 2026 — 71,958 subscribers11 August 2026 — 71,930 subscribers12 August 2026 — 71,906 subscribers13 August 2026 — 71,894 subscribers6 August 202613 August 2026
9 measurements spanning 6 days, net -154. 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 71,871–72,071 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:3771,894-12
12 Aug 2026, 06:3771,906-24
11 Aug 2026, 03:1971,930-28
10 Aug 2026, 01:3171,958-32
9 Aug 2026, 00:5471,990-17
8 Aug 2026, 01:4372,007-35
7 Aug 2026, 01:1072,042-6
6 Aug 2026, 17:4572,048no change
6 Aug 2026, 17:3972,048first reading

Engagement

30 posts held, back to 13 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
9.05%
avg views ÷ 71,894 subscribers
Avg views / post
6,510
28 posts measured
Reaction rate
0.605%
reactions ÷ views · ER floor
Posts in window
28
of 30 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 12 August 2026
Posts held30 (13 July 202612 August 2026)
Views total182,190
Reactions total1,102
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 19:02 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.

Reaction mix

1,170 reactions across 30 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤔1,170100.0%

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 30 of the 30 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 1,170reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 30 most recent posts we hold, published 13 July 2026 to 12 August 2026, 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

12 Aug 2026, 10:59 UTC≈1,830 views30 reactionsread 12 August 2026

🐳🐳 2,703.00 #BTC ($173,353,694) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔30

11 Aug 2026, 22:03 UTC≈2,440 views36 reactionsread 12 August 2026

🐳 1,000.29 #BTC ($63,665,694) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔36

11 Aug 2026, 17:22 UTC≈2,870 views31 reactionsread 12 August 2026

🐳🐳 2,376.04 #BTC ($150,768,019) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔31

10 Aug 2026, 19:56 UTC≈3,290 views36 reactionsread 12 August 2026

🐳 1,751.48 #BTC ($112,035,309) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔36

10 Aug 2026, 13:42 UTC≈3,630 views33 reactionsread 12 August 2026

🐳🐳 2,000.07 #BTC ($129,721,599) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔33

10 Aug 2026, 11:04 UTC≈3,540 views35 reactionsread 12 August 2026

🐳 1,014.69 #BTC ($65,928,504) aggregated inflows to #Okx View Chart | @cryptoquant_alert

🤔35

10 Aug 2026, 09:08 UTC≈3,770 views38 reactionsread 12 August 2026

🐳🐳 2,280.73 #BTC ($148,728,477) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔38

9 Aug 2026, 18:33 UTC≈3,860 views37 reactionsread 12 August 2026

🐳 1,033.77 #BTC ($67,418,631) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔37

8 Aug 2026, 16:26 UTC≈4,420 views38 reactionsread 12 August 2026

🐳 1,046.40 #BTC ($68,104,117) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔38

7 Aug 2026, 17:02 UTC≈4,890 views47 reactionsread 12 August 2026

🐳 1,982.32 #BTC ($128,543,518) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔47

6 Aug 2026, 17:27 UTC≈5,590 views40 reactionsread 12 August 2026

🐳 1,840.66 #BTC ($119,037,626) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔40

6 Aug 2026, 09:11 UTC≈5,580 views45 reactionsread 12 August 2026

🐳 1,239.49 #BTC ($80,412,687) aggregated inflows to #Binance View Chart | @cryptoquant_alert

🤔45

Showing the 12 most recent of 30 posts we hold for @cryptoquant_alert. 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 — 112,379 of 1,160,990entries 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.

Forward network

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 9 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.

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.

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.

Whale Alert
@whale_alert_io · 304,563
Telegram ranks this channel #3 of 99 here — alongside 98 others — read 10 August 2026
WhaleBot Alerts 🐳
@whalebotalerts · 146,457
Telegram ranks this channel #4 of 96 here — alongside 95 others — read 13 August 2026
Binance Futures Liquidations
@BinanceLiquidations · 183,475
Telegram ranks this channel #6 of 95 here — alongside 94 others — read 12 August 2026
The Bull
@thebull_crypto · 178,808
Telegram ranks this channel #18 of 88 here — alongside 87 others — read 12 August 2026
CoinMarketCap Announcements
@CoinMarketCapAnnouncements · 252,597
Telegram ranks this channel #28 of 91 here — alongside 90 others — read 10 August 2026
Watcher Guru
@WatcherGuru · 627,120
Telegram ranks this channel #51 of 94 here — alongside 93 others — read 8 August 2026
Crypto VIP ЯR ™
@CryptoRROFFICAIL · 185,996
Telegram ranks this channel #72 of 91 here — alongside 90 others — read 11 August 2026
Whales Crypto Guide
@Whalesguide · 202,290
Telegram ranks this channel #73 of 91 here — alongside 90 others — read 11 August 2026
Crypto VIP Signal
@CryptoVIPsignalTA · 328,162
Telegram ranks this channel #73 of 89 here — alongside 88 others — read 10 August 2026
Wu Blockchain News
@wublockchainenglish · 254,073
Telegram ranks this channel #82 of 91 here — alongside 90 others — read 10 August 2026
The Crypto Express
@thecryptoexpress · 269,886
Telegram ranks this channel #90 of 90 here — alongside 89 others — read 10 August 2026

This channel appears in 11 seed channels' Telegram-generated recommendation lists 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“CryptoQuant Alert” (@cryptoquant_alert), 71,894 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/cryptoquant_alert.

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.