Telegram RegisterThe public register of Telegram
Telegram profile photo for Даниил Гридасов

Channel

Даниил Гридасов

@gridasov_daniil

On this record: Topic · Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

16,539subscribers

-1,076 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002079685645
TypeChannel
Username@gridasov_daniil
DescriptionПо вопросам сотрудничества (реклама, консультации): @Gridasov_consult_bot По юридическим вопросам(консультация, выезд адвоката): @LegalCrypto01
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/gridasov_daniil

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 the other topics.

Growth

16,52417,61517,069.516,5397 August 202615 November 2026
63 measurements spanning 100 days, net -1,076. 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 16,360–17,779 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
15 Nov 2026, 00:1516,539-22
11 Nov 2026, 20:5616,561-12
9 Nov 2026, 21:1716,573-10
8 Nov 2026, 09:1016,583-12
7 Nov 2026, 07:1616,595-2
6 Nov 2026, 06:5816,597-5
5 Nov 2026, 03:2716,602+4
2 Nov 2026, 08:4716,598-3
1 Nov 2026, 11:1616,601-5
31 Oct 2026, 10:2716,606-10
30 Oct 2026, 13:0916,616-4
29 Oct 2026, 12:2116,620-3
28 Oct 2026, 14:4516,623-8
27 Oct 2026, 17:1116,631-3
26 Oct 2026, 19:4816,634+4
25 Oct 2026, 23:1816,630-3
24 Oct 2026, 22:2916,633-5
23 Oct 2026, 23:0816,638-6
23 Oct 2026, 00:5816,644-11
21 Oct 2026, 22:5916,655first reading

Engagement

66 posts held, back to 16 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 84 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
19.2%
avg views ÷ 16,539 subscribers
Avg views / post
3,180
27 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
29
of 66 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 17 November 2026
Posts held66 (16 July 2026 – 17 November 2026)
Views total85,951
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 18:39 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
394
Videos
54
Links
528

Lifetime counters from Telegram’s own channel header, read 17 November 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.

Video runtime
6m 56s
Average length
2m 19s

Measured directly from 3 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.

Advertising

Ad load
1.52%
1 of 66 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
1,260
over 1 measured post
Median views · rest
2,630
over 62 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 66 most recent posts we hold, published 16 July 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 29 posts held from the last 30 days (6.90%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 15:36 UTC961 viewsread 17 November 2026

Ответы на частные вопросы по ВЭД в 2027 У нас есть пул клиентов. Они ставят нам нал/безнал, мы конвертируем его в крипту. Отправляем её в КГС/Турцию, Дубай, а местная компания оплачивает поставку в нужной нам стране. Как нам продолжить работу с текущими клиентами? Без получения статуса ОООЦВ никак. С лета 2027 любая систематическая конвертация фиата в крипту, без соответсвующей лицензии будет уголовно наказуема. По…

17 Nov 2026, 10:18 UTC≈1,620 viewsread 17 November 2026
Photo

У нас нет страховки от дурака По моей статистике, подавляющее большинство заблокированных по 161 ФЗ не дропы под чернуху и даже не p2p-трейдеры, а просто случайные люди оказавшиеся не в то время, не с тем контрагентом в сделке. Обыватель до сих пор, в 2026 году, пользуется P2P для выводы денег с крипты в фиат. Обыватель знать не знает то, о чем говорят крипто-юристы. Он подписан на каналы с сигналами и на этом его …

17 Nov 2026, 08:38 UTC≈2,320 viewsread 17 November 2026
Photo

Про терпил, потерпевших и 161 ФЗ К вопросу об ужесточении банковских блокировок по жалобе отправителя. Обычный человек - айтишник - получил оплату за выполненный проект в крипте на свой Bybit. Недолго думая, он зашел в P2P-раздел и продал крипту за СБП-перевод себе на карту.(Так делать не надо) На следующий день все его карты оказались в блоке по 161-ФЗ, а на WhatsApp стали приходить сообщения от озлобленного терп…

16 Nov 2026, 21:01 UTC≈2,990 viewsread 17 November 2026

Как не попасть банковскую блокировку если вы нормальный человек? Новость о том, что в Госдуму внесли законопроект системы «Антидроп» – аналога ЗСК для физиков, уже облетела весь около юридический интернет. Усиление банковского контроля, внедрение ИИ и тд и тп. Но что с этой информацией делать нормальным людям - решительно непонятно. Если вкратце. ЦБ поделит физиков на уровни риска (как в системе светофор для юрик…

14 Nov 2026, 13:09 UTC≈3,540 viewsread 17 November 2026
Forwarded from @aurum_cryptopay

AURUM теперь работает без VPN 🎉 Большое обновление AURUM Надоело, что для оплаты покупки нужен Telegram, а для Telegram — VPN? Забудьте об этом! Кошелёк AURUM теперь работает прямо в браузере и как приложение на телефоне — без Telegram и без VPN. 🇷🇺 Оплата по QR СБП прямо с камеры телефона 💸Вывод на карту и по номеру телефона 🪙 Пополнение USDT в TRC-20, BEP-20 и TON 📲 Приложение на Android и iPhone — без магазино…

14 Nov 2026, 12:20 UTC≈3,510 viewsread 17 November 2026
Forwarded from @zudiloff1Photo

Коллеги, пришло время выходить за рамки закрытого сообщества! Уже больше года мы работаем в закрытой группе Pump&Dump, занимаясь торговлей на фьючерсном рынке. На большой дистанции наша работа показывает положительный результат. В этом году мы также планируем командой участвовать в WSOT на Bybit и бороться за призовые места. Параллельно мы запустили публичный портфель, чтобы каждый мог самостоятельно наблюдать за …

12 Nov 2026, 14:13 UTC≈4,530 viewsread 17 November 2026
Photo

Знакомьтесь, НЕКСУС. Поможем вашему обменнику перейти в легальное поле. На канале CPI часто мелькают репосты из загадочной для читателя организации - НЕКСУС. Организация эта будет очень полезна тем, кто решится на легализацию своего криптобизнеса и сегодня я вам о ней поведаю, тк работаю в компании учредителе этой организации. Нексус - проект по созданию профессионального сообщества участников рынка криптообмена.)…

9 Nov 2026, 11:35 UTC≈3,270 viewsread 17 November 2026
Forwarded from @zudiloff1

Коллеги, в последнее время попал в полосу непростых жизненных ситуаций, связанных с семьёй и здоровьем. Сейчас приходится решать много вопросов, в том числе финансовых. Поэтому, если кто-то из вас давно планировал пойти ко мне на обучение, сейчас самое подходящее время. Готов предложить хорошие скидки на свои образовательные программы. Направления обучения: Арбитраж фандинга Консервативная работа на фьючерсном рынк…

7 Nov 2026, 20:19 UTC≈3,550 viewsread 17 November 2026

Правило DVP. То, что изменит весь рынок ВЭДа и криптообмена Новость это настолько важная, что взбудоражила умы всех тех, кто хочет в легальное поле, но прошла мимо СМИ. Правило DVP, в соответствии с разъяснениями ЦБ: криптообменники обязаны проводить расчеты по принципу одновременного или незамедлительного встречного исполнения обязательств, сопоставимого со схемой «поставка против платежа» на рынке ценных бумаг. …

29 Oct 2026, 18:01 UTC≈3,150 viewsread 17 November 2026
Photo

Как не сесть за P2P? На словах всё красиво: купил дешевле, продал дороже, заработал на разнице. Но иногда у этой истории появляется ещё один участник — человек, чьи деньги украли мошенники. А перевод пришёл вам. В новом выпуске адвокат Антон Пивоваров разбирает, как устроены такие истории и почему фраза «я просто менял крипту» не завершает разговор с полицией. Отдельная большая тема — процессинг. Если по-простому:…

27 Oct 2026, 21:01 UTC≈3,040 viewsread 17 November 2026
Forwarded from @rightsidelegalPhoto

❤️ Банки, крипта и цена ошибки: о чем говорили во 2 части Crypto Legal Forum ➡️ В третьей сессии форума Александр Нам (МТС Финтех), Венера Шайдуллина (исследовательский центр Аналитика. Бизнес. Право), Сергей Юдаков («Тот самый 115-ФЗ») и Дмитрий Зикрацкий (Cifra Markets) обсудили взаимодействие банков и криптокомпаний и затронули счета, банковский комплаенс и платежную инфраструктуру. Еще одна большая тема: послед…

27 Oct 2026, 17:36 UTC≈3,100 viewsread 17 November 2026
Photo

Арбитражный спред до 4% по закрытому сервису 😯 Сейчас сохраняется возможность выкупать USDT через закрытый сервис на 2–3 ₽ ниже среднерыночной стоимости и реализовывать объём через ABCEX с суммарным спредом до 4%. Итоговую прибыль вы забираете наличными в офисе или на свой баланс. 👨‍💻Механика на примере расчетов за 13 октября: 1. Закупка: приобретаете USDT через закрытый сервис по курсу 84,59 ₽. 2. Перевод: зачисля…

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

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

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.

Satoshkin
@satoshkin · 31,392
Telegram ranks this channel #1 of 66 here — alongside 65 others — read 5 September 2026
Cartesius channel
@LexagencyLawStream · 30,007
Telegram ranks this channel #4 of 62 here — alongside 61 others — read 8 September 2026
Питупи
@mediap2p · 88,959
Telegram ranks this channel #7 of 65 here — alongside 64 others — read 17 August 2026
Bitpapa Media
@bitpapa_io · 107,777
Telegram ranks this channel #20 of 47 here — alongside 46 others — read 21 September 2026
Тот самый 115-ФЗ
@tot115fz · 26,649
Telegram ranks this channel #34 of 70 here — alongside 69 others — read 12 September 2026
Arbitrage Scanner (official)
@arbitragescanner_eng · 19,526
Telegram ranks this channel #42 of 68 here — alongside 67 others — read 30 September 2026
Spread Maker | Арбитраж криптовалют
@SpreadMaker · 22,714
Telegram ranks this channel #56 of 77 here — alongside 76 others — read 30 September 2026
Arbitrage Services
@Arbitrage_Services · 22,824
Telegram ranks this channel #56 of 71 here — alongside 70 others — read 30 September 2026
Менделеевщина!
@mendeleevshina · 24,175
Telegram ranks this channel #65 of 72 here — alongside 71 others — read 17 September 2026

This channel appears in 9 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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“Даниил Гридасов” (@gridasov_daniil), 16,539 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/gridasov_daniil.

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.