Telegram RegisterThe public register of Telegram
Telegram profile photo for Demon Slayer : Kimetsu No Yaiba

Channel

Demon Slayer : Kimetsu No Yaiba

@Demon_Slayer_Dual

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

163,875subscribers

-2,341 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001493986200
TypeChannel
Username@Demon_Slayer_Dual
Created11 July 2020measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live2 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/Demon_Slayer_Dual

Topic

Gaming — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 82% 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

163,875166,216165,045.56 August 2026 — 166,216 subscribers6 August 2026 — 166,216 subscribers7 August 2026 — 166,198 subscribers8 August 2026 — 166,079 subscribers9 August 2026 — 166,017 subscribers10 August 2026 — 165,911 subscribers11 August 2026 — 165,800 subscribers11 August 2026 — 165,688 subscribers12 August 2026 — 165,641 subscribers14 August 2026 — 165,529 subscribers15 August 2026 — 165,420 subscribers17 August 2026 — 165,282 subscribers18 August 2026 — 165,156 subscribers19 August 2026 — 165,016 subscribers20 August 2026 — 164,963 subscribers21 August 2026 — 164,887 subscribers23 August 2026 — 164,760 subscribers24 August 2026 — 164,595 subscribers25 August 2026 — 164,543 subscribers26 August 2026 — 164,506 subscribers27 August 2026 — 164,437 subscribers28 August 2026 — 164,397 subscribers29 August 2026 — 164,303 subscribers30 August 2026 — 164,187 subscribers31 August 2026 — 164,079 subscribers1 September 2026 — 163,962 subscribers2 September 2026 — 163,875 subscribers6 August 20262 September 2026
27 measurements spanning 27 days, net -2,341. 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 163,524–166,567 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
2 Sept 2026, 16:37163,875-87
1 Sept 2026, 18:12163,962-117
31 Aug 2026, 20:17164,079-108
30 Aug 2026, 19:48164,187-116
29 Aug 2026, 19:04164,303-94
28 Aug 2026, 20:59164,397-40
27 Aug 2026, 22:08164,437-69
26 Aug 2026, 21:55164,506-37
25 Aug 2026, 19:52164,543-52
24 Aug 2026, 18:24164,595-165
23 Aug 2026, 03:59164,760-127
21 Aug 2026, 13:23164,887-76
20 Aug 2026, 12:26164,963-53
19 Aug 2026, 11:33165,016-140
18 Aug 2026, 09:36165,156-126
17 Aug 2026, 10:26165,282-138
15 Aug 2026, 16:18165,420-109
14 Aug 2026, 00:58165,529-112
12 Aug 2026, 20:15165,641-47
11 Aug 2026, 21:33165,688first reading

Engagement

2 posts held, back to 11 July 2020the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 59 pages 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 2 posts for this entry, the most recent from 16 August 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 2 most recent of 2 posts we hold for @Demon_Slayer_Dual. 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

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.

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

“Demon Slayer : Kimetsu No Yaiba” (@Demon_Slayer_Dual), 163,875 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/Demon_Slayer_Dual.

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.