Telegram RegisterThe public register of Telegram
Telegram profile photo for dzantetsu

Channel

dzantetsu

@dzaaaantetsu

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

18subscribers

-1 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-1002079710561
TypeChannel
Username@dzaaaantetsu
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live4 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 4 October 2026
On Telegramt.me/dzaaaantetsu

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 1 October 2026 and assigned it the closest of 31 fixed categories, at 90% 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

181918.57 August 2026 — 19 subscribers11 August 2026 — 19 subscribers9 September 2026 — 18 subscribers7 August 20269 September 2026
3 measurements spanning 33 days, net -1. 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 18–19 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 14:5818-1
11 Aug 2026, 16:4619no change
7 Aug 2026, 14:1819first reading

Engagement

20 posts held, back to 30 May 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 20 posts for this entry, the most recent from 3 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
17s
Average length
9s

Measured directly from 2 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

63 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2742.9%
❤69.52%
😁69.52%
✍34.76%
😎34.76%
😭34.76%
🤡34.76%
🤪34.76%
🤯34.76%
🙊23.17%
🫡23.17%
👏11.59%
🤣11.59%

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 17 of the 20 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 63 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 30 May 2025 to 3 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

3 Nov 2025, 18:09 UTC165 views3 reactionsread 11 August 2026

Кто то мне когда то сказал Что в крипте можно денег заработать Это правда ? Или это ложь??

❤3

14 Jul 2025, 07:17 UTC225 views5 reactionsread 11 August 2026

Когда все радуются и думают что бычка началась видя по альте +7% Это самый главный грин флаг что до бычки еще есть много времени

🤡3🔥2

8 Jul 2025, 19:24 UTC163 views5 reactionsread 11 August 2026
Photo

Короче про монад разблядовка Так как ничего нового там бля не происходит мы как дрочим транзы так и продолжаем Но! —Вчера в куру зафандрайзили 11мили $ И мne пришла интересная активность как можно поактивничать Мы берем все подпроекты на монаде куда занесли деньги А их не много (magma apri kuru kintsu И так далее) А что если взять и раскинуть туда по 100 тестовых монет И даже если монад не раздаст есть шанс что р…

😎3👏1😁1

4 Jul 2025, 19:58 UTC146 views3 reactionsread 11 August 2026

Добавлю разблядовку к прошлому посту ⬆️ Что сейчас ретро дрочилы идут нахуй очень сильно есть ощущение что им самые копейки скидывают с проект дропа а зачастую вообще просто яйца в рот кладут А кто реально хоть как то держится на плову так это типочки которые гриндят роли в дс занимаются Амбассадорством и шилом в твиттере

🫡2❤1

4 Jul 2025, 06:41 UTC136 views5 reactionsread 11 August 2026
Photo

Самая тупая и самая полезная активность где ты можешь хоть что то налутать Треды япы и посты в твиттер 1 почему это так полезно одним тредом ты ебешь Kaito у тебя шилится проект о котором ты пишешь оф акк может тебя заметить и ты сможешь стать абмбой этого же проекта + сам аккаунт в х становится мощнее 2 помимо того что ты зацепил кайто так же под проекты цепляются на кайто тот же virtual.io но это такая лагающая …

🔥4😁1

25 Jun 2025, 08:14 UTC127 views2 reactionsread 11 August 2026

АХАХАХАХАХ ЭТО ПИЗДААААА

❤2

25 Jun 2025, 08:14 UTC130 views3 reactionsread 11 August 2026
Voice message

Voice message, posted without a caption

🤪3

20 Jun 2025, 06:06 UTC139 views4 reactionsread 11 August 2026
Photo

Рубрика сибилворкер Че вообще ща делаю мои мувы Стараюсь ежедневно закрывать все таски по монаду (kuro io dusted итд…) Все гейминг активности в абстракте Прошлая неделя показала что если жечь usdc в таракане сыпят больше икспы Jupiter stake Ноубрейн активность для меня Пока туда лью все копейки с кошельков Так же голосования на их платформе Drip проект который юпитер выкупили По типу magiceden людей вообще не…

🔥3😁1

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

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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“dzantetsu” (@dzaaaantetsu), 18 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/dzaaaantetsu.

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.