Telegram RegisterThe public register of Telegram
Telegram profile photo for —

Channel

@D3M0NS1

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

633subscribers

-71 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-1003006929072
TypeChannel
Username@D3M0NS1
Created18 September 2025measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/D3M0NS1

Topic

Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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

633704668.57 August 2026 — 704 subscribers8 August 2026 — 704 subscribers8 August 2026 — 703 subscribers16 August 2026 — 685 subscribers24 August 2026 — 667 subscribers1 September 2026 — 653 subscribers11 September 2026 — 643 subscribers18 September 2026 — 633 subscribers7 August 202618 September 2026
8 measurements spanning 42 days, net -71. 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 622–715 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 21:21633-10
11 Sept 2026, 04:38643-10
1 Sept 2026, 18:46653-14
24 Aug 2026, 23:55667-18
16 Aug 2026, 20:38685-18
8 Aug 2026, 11:45703-1
8 Aug 2026, 02:18704no change
7 Aug 2026, 18:30704first reading

Engagement

6 posts held, back to 18 September 2025the 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 6 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 1 post, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5325509376864187710250.0%
custom 5328131299779573307250.0%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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

Measured over the 6 most recent posts we hold, published 18 September 2025 to 1 August 2026, 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

30 Mar 2026, 10:00 UTC≈1,080 viewsread 8 August 2026

наш новый канал. все сз и участников туда. https://t.me/DEMONS1FML

Signed 𝑲𝑨𝒀.

25 Mar 2026, 15:32 UTC≈1,400 viewsread 8 August 2026

разрыв всех союзов. — позже наши администраторы сами напишут за перезаключением. Нам нужна разгрузка, приносим извинения за неудобства.

Signed ramil.

28 Feb 2026, 16:32 UTC≈1,510 views4 reactionsread 8 August 2026
Photo

⭐️⭐️✔️ 𝐏𝐀𝐓𝐄𝐍𝐓 ✔️⭐️⭐️ Семья «DEMONS» официально заявляет: имя «DEMONS» принадлежит только нам и отныне находится под нашей защитой и контролем. Это не просто название, это знак чести, силы и верности кодексу семьи. Мы закрепляем его за собой по закону и по праву тех, кто стоит за этим именем спиной к спине. Любая попытка использовать имя «DEMONS» без нашего разрешения будет считаться нарушением и встретит решительный

custom 53255093768641877102custom 53281312997795733072

Signed Karma.

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 registered channels — 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.

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.

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

“—” (@D3M0NS1), 633 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/D3M0NS1.

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.