Channel
@cryptoc
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
18,028subscribers
+3,611 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001148754562 |
|---|---|
| Type | Channel |
| Username | @cryptoc |
| Description | ⚡️ Последние новости рынка криптовалют на сегодня. Обзоры, аналитика, ICO, IEO и другое. Менеджер по рекламе @sashulka7 Наш Инстаграм 📲 https://www.instagram.com/criptoval/ Биржа: @birzha_reklami_cryptovalyuti |
| Created | 29 July 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/cryptoc |
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 10 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @cryptoc/13699 · this entry30 Jul 2026, 14:31 UTC | @kripto_zhara/195331 Jul 2026, 06:37 UTC | 1.00 | 16 hours |
| @cryptoc/13702 · this entry31 Jul 2026, 14:32 UTC | @kripto_zhara/19541 Aug 2026, 05:44 UTC | 1.00 | 15 hours |
| @cryptoc/13706 · this entry2 Aug 2026, 14:40 UTC | @kripto_zhara/19563 Aug 2026, 05:37 UTC | 1.00 | 15 hours |
| @cryptoc/13709 · this entry3 Aug 2026, 14:24 UTC | @kripto_zhara/19574 Aug 2026, 06:01 UTC | 1.00 | 16 hours |
| @cryptoc/13712 · this entry4 Aug 2026, 14:34 UTC | @kripto_zhara/19585 Aug 2026, 04:29 UTC | 1.00 | 14 hours |
| @cryptoc/13718 · this entry6 Aug 2026, 14:34 UTC | @kripto_zhara/19607 Aug 2026, 06:03 UTC | 1.00 | 15 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @kripto_zhara | 6 (6/6 hand-verifiable sample passed) | 1.00 | 15 hours | this entry (6–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 22 comparable posts for this entry, running 29 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @cryptoc — which is this entry. That is a statement about our reading window, not a claim of authorship.
18,800 average views per post against 15,071 subscribers — an engagement rate of 124.8%. Across the 24,466 registered channels in the same cohort — 10,001–31,619 subscribers, posting mainly in Russian — the middle half sit between 5.58% and 23.3%, with a median of 11.7%.
| Window | 30 days (21 July 2026 – 20 August 2026) |
|---|---|
| Posts measured | 37 of 37 published in the window (0 exact, 37 rounded by Telegram) |
| Views totalled | 696,150 |
| Mature posts only | 126.6% over 36 posts read at least 24h after publication |
| Subscribers | 15,071 measured 20 August 2026 |
| Cohort | b10000:rus · 24,466 channels · p10 2.70% · p25 5.58% · p50 11.7% · p75 23.3% · p90 41.6% |
| Position in cohort | 99.587th percentile · 10.7× the cohort median |
| Uncertainty | ±0.193% of the figure, from Telegram’s rounding |
| Post language | Russian · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the keys clone_source · err_high, last confirmed 20 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 16:14 | 18,028 | +459 |
| 21 Aug 2026, 08:47 | 17,569 | +2,498 |
| 20 Aug 2026, 12:05 | 15,071 | +1,948 |
| 19 Aug 2026, 14:12 | 13,123 | -44 |
| 18 Aug 2026, 12:18 | 13,167 | -100 |
| 17 Aug 2026, 13:25 | 13,267 | -152 |
| 16 Aug 2026, 03:25 | 13,419 | -209 |
| 14 Aug 2026, 16:48 | 13,628 | -91 |
| 13 Aug 2026, 10:14 | 13,719 | -69 |
| 12 Aug 2026, 07:32 | 13,788 | -99 |
| 11 Aug 2026, 05:03 | 13,887 | -115 |
| 10 Aug 2026, 06:04 | 14,002 | -135 |
| 9 Aug 2026, 05:05 | 14,137 | -78 |
| 8 Aug 2026, 03:17 | 14,215 | -161 |
| 7 Aug 2026, 00:05 | 14,376 | -41 |
| 6 Aug 2026, 04:00 | 14,417 | no change |
| 6 Aug 2026, 03:53 | 14,417 | first reading |
39 posts held, back to 29 July 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 31 pagesof 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 22 August 2026 |
|---|---|
| Posts held | 39 (29 July 2026 – 22 August 2026) |
| Views total | 715,380 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 22: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.
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.
💰Ралли биткоина связано с цепной ликвидацией шортов на фьючерсах Binance, считает контрибьютор CryptoQunat под псевдонимом BorisD. Так, в ноябре 2024 года индикатор Short Squeeze Value на Binance достиг 5,38. На этой неделе аналогичный показатель составил 6,94 — максимум за два года. Тем не менее аналитик предупредил о риске резкого отката в случае слабого спотового спроса.
📊💲 В июле объём переводов USDC составил $3,6 трлн Аналитики предполагают, что разрыв с 💲USDT объясняется более сильными позициями 💲USDC в институциональных и платёжных расчётах благодаря лицензии MiCA в 🇪🇺ЕС и интеграциям с 💳Visa и 💳Mastercard.
🇨🇳 Шанхайская технологическая компания Zhibao Technology закупила 2 380 BTC ($155 000 000) — и сразу ворвалась в топ-40 публичных компаний по запасам биткоина.
🏴Банк Англии начинает тестировать стейблкоины и другие цифровые валюты для международных платежей — регулятор хочет проверить, могут ли они сделать трансграничные расчёты быстрее и дешевле. Если эксперимент окажется успешным, цифровые деньги могут начать встраивать прямо в традиционную банковскую инфраструктуру.
📊 Резко выросла активность китов в токене LINK. Santiment пишет, что крупные держатели продолжают покупать.
💰 Крупнейшие игроки крипторынка призывают дать Bitcoin-разработчикам ранний доступ к передовым AI-моделям Инициаторы считают, что нынешние ограничения могут создавать парадоксальную ситуацию: легальные исследователи не всегда могут использовать ИИ на полную для поиска уязвимостей, в то время как злоумышленники могут работать с локальными и менее ограниченными моделями. Письмо уже поддержали Coinbase, Strategy, Bloc…
🪙 Solana обновила исторический максимум — за сутки сеть обработала более 172 млн реальных транзакций без учёта голосований. Фактическая пропускная способность при этом достигла примерно 2000 транзакций в секунду.
📊 Притоки в спотовые BTC ETF выросли до максимума за 4 месяца — BBG
💸 MARA, крупнейший в мире Bitcoin-майнер, сообщает о продаже 23 093 BTC ($1.6 млрд) в первой половине 2026 года по средней цене $70 631 за 1 BTC. Компания по-прежнему владеет 35 577 BTC ($2 млрд).
☠️ Хакеры взломали криптоплатежный сервис Coinsbuy на $7 900 000. Также взломан DeFi-протокол Bifrost на $720 000.
🇸🇦 Tether запускает в Саудовской Аравии платформу для токенизации недвижимости — права на объекты будут превращать в цифровые токены и продавать инвесторам через блокчейн. Позже эту же модель планируют использовать для энергетики, инфраструктуры и других реальных активов.
🎣 Фишинговый сайт Trezor вчера оказался первым рекламным результатом в Google и маскировался под официальный сервис. После массовых жалоб объявление удалили.
Showing the 12 most recent of 39 posts we hold for @cryptoc. 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 — 987,129 of 1,584,142entries 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.
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.
Named by 5 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.
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.
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.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Криптовалюты” (@cryptoc), 18,028 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/cryptoc.
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.