Наибыстрейший информационный по крипте 24/7
@cryptoattackbot - мгновенный агрегатор данных с профессиональных терминалов 🤖
@cryptoarsenal - bot data
@cryptoattack - дайджест
@pro_demo - инфо о боте
@Attackconnect_bot - сотрудничество (также API/WS)
Created
Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 93% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
17 measurements spanning 16 days, net -280. 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 56,661–57,027 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
21 Aug 2026, 21:54
56,705
-8
20 Aug 2026, 14:38
56,713
+10
19 Aug 2026, 13:53
56,703
-35
18 Aug 2026, 12:55
56,738
-17
17 Aug 2026, 09:52
56,755
-26
15 Aug 2026, 20:05
56,781
-23
14 Aug 2026, 09:47
56,804
-26
13 Aug 2026, 03:47
56,830
-27
12 Aug 2026, 01:32
56,857
-14
11 Aug 2026, 03:32
56,871
-28
10 Aug 2026, 06:10
56,899
-23
9 Aug 2026, 05:02
56,922
-16
8 Aug 2026, 04:37
56,938
-23
7 Aug 2026, 05:12
56,961
-21
6 Aug 2026, 08:30
56,982
-3
6 Aug 2026, 01:37
56,985
no change
6 Aug 2026, 00:48
56,985
first reading
Engagement
326 posts held, back to 5 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 35 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
7.43%
avg views ÷ 56,705 subscribers
Avg views / post
4,210
326 posts measured
Reaction rate
0.402%
reactions ÷ views · ER floor
Posts in window
326
of 326 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. It is computed over the 324 of 326 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 22 August 2026
Posts held
326 (5 August 2026 – 22 August 2026)
Views total
1,373,894
Reactions total
5,506
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 13:32 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.
What this channel posts
Photos
≈19,900
Videos
≈2,240
Links
≈59,100
Lifetime counters from Telegram’s own channel header, read 22 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
2m 34s
Average length
15s
Measured directly from 10 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
5,166 reactions across 305 posts, in 29 distinct kinds. The most used accounts for 46.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
😁
2,421
46.9%
❤
1,028
19.9%
🥰
266
5.15%
🔥
220
4.26%
👍
183
3.54%
🐳
154
2.98%
😱
135
2.61%
🫡
126
2.44%
🏆
87
1.68%
💯
67
1.30%
🤔
58
1.12%
😨
57
1.10%
🙏
54
1.05%
✍
46
0.89%
🗿
42
0.813%
😎
40
0.774%
⚡
29
0.561%
🍾
22
0.426%
🎉
21
0.407%
🤝
21
0.407%
9 further kinds
89
1.72%
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 324 of the 326 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 5,506reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 326 most recent posts we hold, published 5 August 2026 to 22 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.
Telegram Stars
Stars received
8
across the posts below
Posts paid on
8
of 326 we hold a reading for · 2%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @cryptoattack24. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 326 most recent posts we hold for this entry, published 5 August 2026 to 22 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
💬 Grayscale: Токенизированное финансирование ранее сталкивалось с препятствиями из-за неясности регулирования. Если новые правила SEC стимулируют выпуск токенов, это привлечет больше американских эмитентов и инвесторов в блокчейн, что будет способствовать возврату капитала в ETH, SOL и BNB. При этом более высокая активность в сети не гарантирует роста цен на токены.
🤟🧯 #UNI Вчера Uniswap установили рекорд по дневному объёму сжигания UNI (~$590 тыс), что стало новым историческим максимумом в долларовом выражении. Всего за день было сожжено ~ 150 тыс UNI. Из них на Ethereum ~ $267k, на Base — $165k и на Robinhood Chain — $87k.
🏴☠️👀 #SAND Согласно последним данным мониторинга PeckShield по возможному взлому The Sandbox, на двух адресах было выпущено около 14,9 млрд SAND — вместо ранее озвученных 500 млн токенов.
🏴☠️ Кошелёк потерял $2 млн в результате «отравления адреса»: хакер отправил транзакцию, чтобы подделать адрес, а жертва скопировала и вставила неверный адрес.
📊 #ENA Santiment: с 17 августа ENA вырос на ~69%. Открытый интерес за тот же период увеличился более чем вдвое, с ~$113 млн до ~$237 млн.
Количество активных адресов за день достигло 1946, что в ~2,5 раза превышает августовский базовый уровень и является самым высоким показателем за этот период.
Ранее: Памп ENA на >55% 🚀
🇺🇸🇨🇦 #торговыевойны США приостановили переговоры с Канадой и вводят 50% пошлины на некоторые виды канадского импорта, которые вступают в силу немедленно.
🔍 loracle.hl за последние 3 месяца потерял >$70 млн на #HYPE.
Если цена #HYPE достигнет $101,15, его текущий шорт в 685 744 #HYPE ($54,88 млн) будет ликвидирован.
🤔 #BTC CEO Bitget прогнозирует, что к концу года курс BTC останется на уровне, близком к текущему, и сомневается, что США будут покупать BTC. cointelegraph.com
🍒Дайджест за сегодня и события на выходных – https://t.me/cryptoattack/21377
❤1🥰1
Showing the 12 most recent of 326 posts we hold for @cryptoattack24. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@cryptoattack24 edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
8 August 2026
Most recent edit
19 August 2026
Citation-graph rank
Citation-graph rank — 1,359 of 1,583,249entries 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 63 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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.
MarketTwits @markettwits · 334,548 Telegram ranks this channel #4 of 95 here — alongside 94 others — read 10 August 2026
Mr Mozart @mr_mozart · 130,614 Telegram ranks this channel #9 of 95 here — alongside 94 others — read 13 August 2026
Crypto Headlines @crypto_hd · 133,053 Telegram ranks this channel #9 of 95 here — alongside 94 others — read 13 August 2026
ForkLog @forklog · 93,023 Telegram ranks this channel #11 of 95 here — alongside 94 others — read 16 August 2026
Coin Post – Деньги, инвестиции, биткоин @Coin_Post · 293,956 Telegram ranks this channel #12 of 94 here — alongside 93 others — read 10 August 2026
Ондрей Гойчев (DFW Bals) @ondreigoichev · 160,636 Telegram ranks this channel #13 of 72 here — alongside 71 others — read 12 August 2026
Trader 80/20 @tradertrend · 61,040 Telegram ranks this channel #14 of 96 here — alongside 95 others — read 22 August 2026
Incrypted @incrypted · 108,771 Telegram ranks this channel #14 of 97 here — alongside 96 others — read 14 August 2026
H O R I Z O N @horizonweb · 265,817 Telegram ranks this channel #15 of 55 here — alongside 54 others — read 19 August 2026
Crypto Daily – биткоин, криптовалюта @cryptodaily · 86,843 Telegram ranks this channel #15 of 93 here — alongside 92 others — read 18 August 2026
РБК Крипто @RBCCrypto · 133,067 Telegram ranks this channel #15 of 93 here — alongside 92 others — read 13 August 2026
Drops Analytics @drops_analytics · 676,540 Telegram ranks this channel #15 of 95 here — alongside 94 others — read 10 August 2026
Crypto Falcon @falconinvestors · 82,341 Telegram ranks this channel #16 of 92 here — alongside 91 others — read 18 August 2026
001k.Trade @trade001k · 108,243 Telegram ranks this channel #16 of 92 here — alongside 91 others — read 15 August 2026
Криптопатолог | Новости | Инвестиции @criptopatolog · 79,734 Telegram ranks this channel #18 of 95 here — alongside 94 others — read 18 August 2026
SANCHO D.T. @SANCHO_DT · 65,703 Telegram ranks this channel #19 of 80 here — alongside 79 others — read 21 August 2026
Crypto | Azam @crypto_azam · 137,035 Telegram ranks this channel #19 of 88 here — alongside 87 others — read 13 August 2026
Binance Новости @binance_ru · 96,928 Telegram ranks this channel #20 of 96 here — alongside 95 others — read 16 August 2026
BYBIT Новости @BybitRussian_News · 119,233 Telegram ranks this channel #20 of 94 here — alongside 93 others — read 14 August 2026
PIFAGOR TRADE @pifagortrade · 85,761 Telegram ranks this channel #23 of 95 here — alongside 94 others — read 18 August 2026
Gerchik Trading Ecosystem @AlexanderGerchik · 75,676 Telegram ranks this channel #24 of 88 here — alongside 87 others — read 19 August 2026
Invest Network | Криптоновости @investnetworkai1 · 60,087 Telegram ranks this channel #26 of 85 here — alongside 84 others — read 22 August 2026
Binance Futures Liquidations @BinanceLiquidations · 182,753 Telegram ranks this channel #27 of 95 here — alongside 94 others — read 12 August 2026
10 долларов Баффетта @buff_10 · 60,545 Telegram ranks this channel #29 of 95 here — alongside 94 others — read 22 August 2026
This channel appears in 40 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 21 August 2026 — this
entry's latest reading, not the date you are reading this.
“КриптоАтака 24 ⚡️” (@cryptoattack24), 56,705 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/cryptoattack24.
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.