Telegram RegisterThe public register of Telegram
Telegram profile photo for 感谢支持,红楼定不负所托。

Channel

感谢支持,红楼定不负所托。

@dedonicon

3 usernames

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

3,104subscribers

-2,880 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002532888421
TypeChannel
Usernames@dearmite @dedonicon @xingyonghonglou
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live10 November 2026
Measurements held49
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/dedonicon

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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

3,1045,9844,54412 August 2026 — 5,984 subscribers12 August 2026 — 5,984 subscribers12 August 2026 — 5,976 subscribers13 August 2026 — 5,961 subscribers16 August 2026 — 5,895 subscribers16 August 2026 — 5,894 subscribers20 August 2026 — 5,842 subscribers20 August 2026 — 5,842 subscribers23 August 2026 — 5,829 subscribers23 August 2026 — 5,831 subscribers26 August 2026 — 5,815 subscribers26 August 2026 — 5,817 subscribers29 August 2026 — 5,814 subscribers30 August 2026 — 5,804 subscribers1 September 2026 — 5,765 subscribers1 September 2026 — 5,757 subscribers4 September 2026 — 5,743 subscribers6 September 2026 — 5,722 subscribers9 September 2026 — 5,458 subscribers11 September 2026 — 4,677 subscribers13 September 2026 — 4,399 subscribers14 September 2026 — 4,301 subscribers17 September 2026 — 3,951 subscribers18 September 2026 — 3,698 subscribers26 September 2026 — 5,650 subscribers28 September 2026 — 5,509 subscribers5 October 2026 — 5,051 subscribers5 October 2026 — 4,977 subscribers11 October 2026 — 4,743 subscribers12 October 2026 — 4,695 subscribers14 October 2026 — 4,540 subscribers15 October 2026 — 4,515 subscribers17 October 2026 — 4,325 subscribers18 October 2026 — 4,322 subscribers20 October 2026 — 4,297 subscribers21 October 2026 — 4,292 subscribers23 October 2026 — 4,277 subscribers24 October 2026 — 4,258 subscribers26 October 2026 — 4,229 subscribers27 October 2026 — 4,081 subscribers28 October 2026 — 3,988 subscribers30 October 2026 — 3,752 subscribers31 October 2026 — 3,694 subscribers3 November 2026 — 3,611 subscribers3 November 2026 — 3,601 subscribers6 November 2026 — 3,443 subscribers6 November 2026 — 3,439 subscribers9 November 2026 — 3,170 subscribers10 November 2026 — 3,104 subscribers12 August 202610 November 2026
49 measurements spanning 90 days, net -2,880. 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 2,672–6,416 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 49
Measured (UTC)SubscribersChange
10 Nov 2026, 08:163,104-66
9 Nov 2026, 18:093,170-269
6 Nov 2026, 14:463,439-4
6 Nov 2026, 10:463,443-158
3 Nov 2026, 16:463,601-10
3 Nov 2026, 03:193,611-83
31 Oct 2026, 19:313,694-58
30 Oct 2026, 23:353,752-236
28 Oct 2026, 22:393,988-93
27 Oct 2026, 23:494,081-148
26 Oct 2026, 01:294,229-29
24 Oct 2026, 15:104,258-19
23 Oct 2026, 08:284,277-15
21 Oct 2026, 09:294,292-5
20 Oct 2026, 14:044,297-25
18 Oct 2026, 04:174,322-3
17 Oct 2026, 23:284,325-190
15 Oct 2026, 08:204,515-25
14 Oct 2026, 17:574,540-155
12 Oct 2026, 18:074,695first reading

Engagement

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

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

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

Measured over the 10 most recent posts we hold, published 10 August 2026 to 12 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

12 Aug 2026, 11:16 UTC23 viewsread 12 August 2026
Photo

1️⃣大圈/熟客/对版/好评✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

12 Aug 2026, 11:11 UTC23 viewsread 12 August 2026
Photo

1️⃣大圈/熟客/对版✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

12 Aug 2026, 11:03 UTC21 viewsread 12 August 2026
Photo

1️⃣大圈/预约/熟客/对版✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

11 Aug 2026, 17:46 UTC66 viewsread 12 August 2026
Photo

1️⃣大圈➕中圈/熟客/对版✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

11 Aug 2026, 16:02 UTC69 views1 reactionsread 12 August 2026
Photo

1️⃣大圈/对版/好评✔️🏅 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

❤1

11 Aug 2026, 11:06 UTC68 viewsread 12 August 2026
Photo

2️⃣中圈/🈚套/对版✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

10 Aug 2026, 15:04 UTC98 viewsread 12 August 2026
Photo

3️⃣小圈/熟客/对版✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

10 Aug 2026, 14:49 UTC96 viewsread 12 August 2026
Photo

1️⃣大圈/亲大哥/对版✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

10 Aug 2026, 12:41 UTC87 viewsread 12 August 2026
Photo

1️⃣大圈/对版✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

10 Aug 2026, 11:15 UTC79 viewsread 12 August 2026
Photo

1️⃣大圈/熟客/对版✔️ 👑 谢谢您选择红楼,您的信任是我们前行的动力。👍 🏅官 方 认 证 频 道 红 楼 精 选👍 ─────────────── 💡大 哥 给 的 好 评 一 键 查 看👌 ─────────────── 👠双向神器 😃 👠红楼客服

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

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

“感谢支持,红楼定不负所托。” (@dedonicon), 3,104 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/dedonicon.

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.