10 Dec 2025, 12:01 UTC≈1,580 viewsread 8 August 2026
Photo
Всем привет Сегодня не торгую из-за новостного фона
Channel
Kai
@dynastykai
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
462subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002132792399 |
|---|---|
| Type | Channel |
| Username | @dynastykai |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/dynastykai |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 20:25 | 462 | -2 |
| 24 Aug 2026, 19:45 | 464 | -3 |
| 16 Aug 2026, 18:05 | 467 | -1 |
| 8 Aug 2026, 04:47 | 468 | no change |
| 7 Aug 2026, 12:37 | 468 | first reading |
Engagement
18 posts held, back to 26 June 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 10 December 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
8 Dec 2025, 13:17 UTC≈1,610 viewsread 8 August 2026
Смущало, что сразу после закрепления пришли в nPOC, дождался выход из 5m имба и заходил маркетом
8 Dec 2025, 13:16 UTC≈1,540 viewsread 8 August 2026
FDAX1! https://www.tradingview.com/x/rUdPLomG/ Набирал позицию от значений VAL в дисбаланс прошлого дня Ожидаю поход в следующий дисбаланс : https://www.tradingview.com/x/HwGooLJO/
2 Dec 2025, 11:52 UTC≈1,200 viewsread 8 August 2026
DAX https://www.tradingview.com/x/BPKZRyBB/ OTD
26 Nov 2025, 12:44 UTC≈1,200 viewsread 8 August 2026
Video
Video, posted without a caption
26 Nov 2025, 12:44 UTC≈1,080 viewsread 8 August 2026
Про это тоже не забыл, в ближайшее время запишу
26 Nov 2025, 12:42 UTC≈1,050 viewsread 8 August 2026
DAX https://www.tradingview.com/x/VIVWrSuu/ Вчера набирал позицию до VAH прошлого дня. https://www.tradingview.com/x/3SrK8sKC/
26 Nov 2025, 12:37 UTCviews —
Posted without readable text
26 Nov 2025, 12:31 UTC805 viewsread 8 August 2026
Всем привет банда! Давно не выходил на связь — был период, когда нужно было отключиться и навести порядок как в трейдинге, так и в личных делах. Это время я использовал как перезагрузку — она нужна каждому трейдеру. Сейчас я возвращаюсь с новыми идеями, свежей энергией и улучшенной стратегией. Спасибо тем, кто оставался здесь — дальше будет гораздо интереснее.
30 Jul 2025, 13:33 UTC≈2,020 viewsread 8 August 2026
Так же, планирую сделать разбор позиций по профилю, которые набирались в последние месяца. Сейчас чарт мне не нравится, так что оставил до лучших времен
30 Jul 2025, 13:32 UTC≈1,950 viewsread 8 August 2026
Всем привет. Скоро сажусь записывать видео про ТПО. На рынке ничего интересного - нет. Так, что времени свободного много, а это значит, что готов снова сопровождать своих учеников на пути становления трейдером. Работаем до результата, первым двум, кто берет - сделаю хорошую скидку. Связь : @kaiifx
25 Jul 2025, 15:24 UTC≈1,900 viewsread 8 August 2026
Информация будет от А - Я Так, что постарайтесь с реакциями там
Showing the 12 most recent of 18 posts we hold for @dynastykai. 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.
Mentions
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.
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.
Kahramanov | Crypto 📈
@kahramanov_trader · 58,584
Telegram ranks this channel #23 of 60 here — alongside 59 others — read 22 August 2026
@kahramanov_trader · 58,584
Telegram ranks this channel #23 of 60 here — alongside 59 others — read 22 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Kai” (@dynastykai), 462 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/dynastykai.
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.