Channel
@cryptodurkaofficial
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
40,074subscribers
-3,447 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002060857464 |
|---|---|
| Type | Channel |
| Username | @cryptodurkaofficial |
| Description | Показываю как терять деньги 📈 Авторский канал Главный / main manager @moodymo0d Лайф https://t.me/+GkafG6-WlKU0NTEy managers: @tocatcrypto @fprizrak @egor_unique, @pepeadss @killhpx @nftcriptahueta |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/cryptodurkaofficial |
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 97% 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 |
|---|---|---|---|
| @cryptodurkaofficial/982 · this entry17 Jul 2026, 20:35 UTC | @cryptodurka_official/84517 Jul 2026, 20:35 UTC | 1.00 | under a minute |
| @cryptodurkaofficial/983 · this entry18 Jul 2026, 18:57 UTC | @cryptodurka_official/84618 Jul 2026, 18:57 UTC | 1.00 | under a minute |
| @cryptodurkaofficial/984 · this entry20 Jul 2026, 19:26 UTC | @cryptodurka_official/84720 Jul 2026, 19:26 UTC | 1.00 | under a minute |
| @cryptodurkaofficial/985 · this entry22 Jul 2026, 20:07 UTC | @cryptodurka_official/84822 Jul 2026, 20:07 UTC | 1.00 | under a minute |
| @cryptodurkaofficial/986 · this entry24 Jul 2026, 19:07 UTC | @cryptodurka_official/85024 Jul 2026, 19:08 UTC | 1.00 | under a minute |
| @cryptodurkaofficial/988 · this entry27 Jul 2026, 20:27 UTC | @cryptodurka_official/85227 Jul 2026, 20:27 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @cryptodurka_official | 20 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (20–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 21 comparable posts for this entry, running 9 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 @cryptodurkaofficial — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 8 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 |
|---|---|---|
| 19 Sept 2026, 00:17 | 40,074 | -170 |
| 16 Sept 2026, 14:41 | 40,244 | -96 |
| 14 Sept 2026, 20:21 | 40,340 | -163 |
| 13 Sept 2026, 09:40 | 40,503 | -169 |
| 11 Sept 2026, 15:40 | 40,672 | -156 |
| 9 Sept 2026, 01:39 | 40,828 | -266 |
| 5 Sept 2026, 18:57 | 41,094 | -179 |
| 3 Sept 2026, 15:40 | 41,273 | -119 |
| 2 Sept 2026, 06:12 | 41,392 | -84 |
| 1 Sept 2026, 06:57 | 41,476 | -117 |
| 31 Aug 2026, 06:34 | 41,593 | -83 |
| 30 Aug 2026, 03:25 | 41,676 | -67 |
| 29 Aug 2026, 04:13 | 41,743 | -86 |
| 28 Aug 2026, 06:34 | 41,829 | -82 |
| 27 Aug 2026, 05:28 | 41,911 | -62 |
| 26 Aug 2026, 02:26 | 41,973 | -98 |
| 24 Aug 2026, 22:59 | 42,071 | -126 |
| 23 Aug 2026, 12:24 | 42,197 | -182 |
| 21 Aug 2026, 20:17 | 42,379 | -87 |
| 20 Aug 2026, 17:05 | 42,466 | first reading |
44 posts held, back to 9 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 85 pages of 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 20 September 2026 |
|---|---|
| Posts held | 44 (9 July 2026 – 20 September 2026) |
| Views total | 89,500 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 11:00 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 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 6 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.
📞 Рынок растет? Нападайте на Иран! Только мы немного выдохнули и начали радоваться росту крипторынка, как наш пыл моментально остудили 🇺🇸 Появились слухи, что США готовят масштабную операцию против хуситов в Йемене, и рынок быстро скорректировался. BTC держится около $80 440, ETH торгуется по $2 580, а наш родной GRAM по $1,37 Лишь бы Донни не встал в шорт, тогда это точно окажется не слухами 👋
🤔На крипторынке происходит что-то странное Bitcoin за неделю поглотил сразу 5 негативных факторов: 🔴CLARITY Act провалился в Сенате 🔴ФРС повысила ставки 🔴Банк Японии повысил ставки 🔴DXY вернулся выше 100 🔴Нефть растёт И при этом BTC всё ещё выше уровня начала недели. Похожее было в 2023-м: негативные новости от SEC, иски к биржам, задержки ETF и повышение ставок ФРС но Bitcoin не обновлял минимумы. Когда рынок п…
🎩 BTC > $77k в моменте. Спонсор пампа - CEO NVIDIA с буллиш тезисами Пока делать выводы по рынку рано, но, смотря на реакцию на ФРС, то как будто повышение ставки уже было заложено, а вот Clarity фронтранили, но тут SEC и CFTC возьмут часть функций на себя. Поэтому с выводами не спешим, наблюдаем. А BlackRock под шумок отправили на Coinbase для продажи ETH на $131,7 млн и BTC на $153,8 млн.
💸BTC уже четвертый день держится в одном диапазоне и никак не хочет пробивать поддержку. Рынок сейчас выглядит крайне странно: с фундаментальной точки зрения всё как будто толкает цену вниз, но продавцы до сих пор не могут реализовать этот сценарий. BTC — это ещё тот «недоработанный» актив 😅 Иногда он движется строго по логике всего рынка, а иногда поступает с точностью до наоборот и просто игнорирует очевидные сиг…
💸 Как BTC связан с ВЫБОРАМИ? Трейдеры из X нашли «новую» стратегию заработка на BTC. Якобы достаточно торговать по календарю выборов в США: 2026: купить на промежуточных выборах 2027: продать 25% 2028: продать 50% на президентских выборах 2029: продать оставшиеся 25% 2030: снова закупиться 🎤 По утверждению её сторонников, с 2014 года результаты отличные, и в стратегии неважно, кто победит на выборах Главное, не г…
🐹 Запуск Байдена СРАБОТАЛ ...всех побрили! Токен LAPTOP от Хантера Байдена обвалился на 99% почти сразу после старта 🪒 Запустился он сразу с капитализацией в $300 млрд и стали закрываться о желающих закупиться Ранее Хантер жаловался на $15 млн долгов и говорил, что не знает, как их выплачивать Спасибо криптолудикам за то, что погасили его долги 🤔
Очередной мем на горизонте 😝 Сын Байдена Хантер решил сделать свой мем LAPTOP Старт планируется на 9 сентября на чейне Base, странно что не на робингуде. Также 30% будет привязано к прогнозам, если сбываются, токены сгорают, нет - идут на благотворительнось Хантер, ты ковбой. Патроны спрячь подальше на склад и забудь про своего папу..
😱 Сентябрь может обрушить рынки 16 числа ФРС примет решение по ставке и если снижения не произойдет — Донни снова начнет разжигать торговые войны Среди крупнейших стран, с которыми США может прекратить торговлю: Китай, Мексика, Канада, Германия, Япония, Южная Корея Рынок же закладывает больше вероятности в то, что ставку не только не снизят, но даже повысят, а это станет двойным ударом по рисковым активам, в т.ч. …
🤯 КАК МАСК ЗАСКАМИЛ ВЕСЬ X Скамеры взломали аккаунт матери детей Маска, придумали проект ShivoLink и запустили под него токен Маск, который уже сбился со счёта своих жён, не слишком вник и прокомментировал её пост смайликом «💯» Вскоре предупреждение о взломе отозвали, а на проект подписался популярный фан-аккаунт об Илоне — Doge Designer 🐹 Многие приняли всё это за подтверждение и начали скупать связанную с проек…
BTC уже ниже 80 000$ — рынок нормально вздрогнул🥹 Причина сегодняшнего движения — сильные данные по рынку труда США. В августе было создано +162 тыс. рабочих мест, хотя рынок ожидал лишь +55 тыс. Безработица при этом осталась на уровне 4,1% BTC < $80k, альты традиционно летят ещё веселее. Ну что, криптошники, выкупаем или ждём $75k? 👀
Обычный день криптана 📈 BTC растёт — «почему я не купил больше» 📉 BTC падает — «ну всё, медвежка» 📈 BTC снова растёт — «ладно, щас зайду» 📉 BTC падает сразу после покупки — «я так и знал» 💱 А иногда хочется просто: USDT → BTC BTC → ETH ETH → фиат, и чтобы без квеста уровня «пройдите 14 кругов ада, загрузите паспорт, сфоткайте паспорт с лицом и объясните происхождение 37 USDT» 🪦 🍌 Для таких случаев есть B…
😨 ХУДШИЙ МЕСЯЦ СТАЛ ЛУЧШИМ При исторической медианной доходности −6,99% август редко радует криптанов 🚀 Но в этом году Биткоин прибавил почти 25% и превратил худший месяц в лучший с ноября 2024 года Теперь главное, чтобы сентябрь не решил исправить это и затопить рынок кровавыми слезами 🤭
Showing the 12 most recent of 44 posts we hold for @cryptodurkaofficial. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 29 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Криптодурка 💊” (@cryptodurkaofficial), 40,074 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/cryptodurkaofficial.
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.