Telegram RegisterThe public register of Telegram

Channel

𝖣𝖺𝗇 𝖧𝖾𝗇𝗀 `無名

@DanHeng_LiChe

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

47subscribers

+5 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004443049489
TypeChannel
Username@DanHeng_LiChe
CreatedBetween 1 June 2026 and 26 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/DanHeng_LiChe

Growth

424744.58 August 2026 — 42 subscribers10 August 2026 — 42 subscribers14 August 2026 — 47 subscribers8 August 202614 August 2026
3 measurements spanning 7 days, net +5. 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 41–48 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:4447+5
10 Aug 2026, 17:1642no change
8 Aug 2026, 07:1642first reading

Engagement

19 posts held, back to 26 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
74.4%
avg views ÷ 47 subscribers
Avg views / post
34.9
19 posts measured
Reaction rate
21.2%
reactions ÷ views · ER floor
Posts in window
19
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 16 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held19 (26 July 20269 August 2026)
Views total664
Reactions total117
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 17:16 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

117 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 36.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4336.8%
🕊2823.9%
🍓2218.8%
🍾1613.7%
🎄75.98%
💔10.855%

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

Measured over the 19 most recent posts we hold, published 26 July 2026 to 9 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

9 Aug 2026, 17:23 UTC17 views3 reactionsread 10 August 2026

🌟🧁🧁🧁 ❨ 🤩🤩 ❩ 🧁🧁🧁 🌟 Я отправился в Город Морской. Конечно, в Городе Плоском, думаю, было бы больше магазинов с подходящими для меня товарами, однако мне захотелось заглянуть именно в Морской. 🤩 В вечернее время пейзажи там ещё более красивы! Я успел застать неописуемый вид на берегу, озарённом ярким уходящим солнцем. Один только этот вид стоил моей поездки туда. Но мне всё же повезло даже приобрести пару товаров — кни

1🍾1🕊1

9 Aug 2026, 15:52 UTC21 views3 reactionsread 10 August 2026

🌟🧁🧁🧁 ❨ 😅😅😅 ❩ 🧁🧁🧁 🌟 Совет № 🔤: прежде, чем ложитесь спать убедитесь, что находитесь в безопасности. И что поблизости нет никого, кто мог бы вам навредить. 🪷 Я не подвергался никаким нападениям и не пострадал во сне, не волнуйтесь. Случилось другое: двое «гениальных» друзей решили, что моё лицо — отличный холст для их художеств. Я оставлю это без комментариев. 🪷 🌟🌟И поговорю с вами на более важную тему. В последнее вр

1🍓1🕊1

1 Aug 2026, 14:00 UTC47 views11 reactionsread 10 August 2026

🌟❨ #sistem ❩ | 😅 на этой прекрасной ноте наш интерактив заканчивается! буду благодарен отдаче в виде реакций и/или комментариев, благодарю за прочтение 🤩 саппорт возвращается в обычный режим с завтрашнего дня, спасибо за внимание.

4🍓4🎄3

1 Aug 2026, 13:42 UTC46 views10 reactionsread 10 August 2026
Photo

😊😊😊😊😊😊😊😊😊😊😊😊 🌟🌟🌟🌟🌟🌟🤩🤩🤩🌟 🎀 — Что, стесняешься меня? 🎀 — Мне... немного неловко. Не каждый день такое происходит. 🎀 — Это можно исправить. 🎀 — .... 🌟 Отношения это всегда про взаимную инициативу, верно? В отношениях каждый должен любить и быть любимым одновременно, иначе это не более чем мучение для обоих. Неловкие шаги со стороны Дань Хэна немного смешат и одновременно умиляют Блэйда. Разве можно злиться на этого не

4🍾3🍓1🎄1🕊1

31 Jul 2026, 20:32 UTC32 views5 reactionsread 10 August 2026

Пишу только сейчас, за что прошу прощения. Всё это время был... с ним.. Теперь мы, кажется, вместе. Ощущение, словно что-то что долго гложило мою душу наконец-то ушло. Такая лёгкость и нежность, не могу не радоваться. Хоть нам и многое предстоит впереди, не скажу, что этого раньше не было. Как камень с души. Ну и потрепал же он мои нервы перед признанием.

2🍓1🍾1🕊1

31 Jul 2026, 20:27 UTC30 views6 reactionsread 10 August 2026
Photo

🌟😊😊😊😊😊😊😊😊😊 🌟🌟🌟🌟🌟🌸🌸🌟🌟 🌟Самой судьбой уготована эта долгожданная встреча. Самой судьбой предначертано совместное будущее. Самой судьбой уготовано множество препятствий и сюрпризов для двух спутников. Пока они рядом им ничего не страшно. Пока они рядом, они смогут узнать и понять множество вещей: себя, друг друга, людей вокруг, мир за пределами собственного тела. Что бы ни было в их прошлом, что бы ни было в их будущем

2🍓2🕊2

30 Jul 2026, 15:46 UTC34 views8 reactionsread 10 August 2026
Photo

🌟😊😊😊😊😊😊😊😊😊😊 🌟🌟🌟🌟🌟🌸🌸🌸🌸🌟🌟 🌟В груди что-то обжигает сердце. Сердце, давно переставшее чувствовать что-либо помимо боли. Сердце, хранившее в себе вечную память о друге из прошлой жизни. Голубо-зелёные глаза, чёрт бы их побрал, уставились прямо на него, отражая всю тревогу видьяхарского сердца. Нежные пальцы поглаживают щёки, лоб сталкивается с другим. Как же много Блэйд упускал, гоняясь за ним столько лет, но никогда не

🕊32🍾2🍓1

30 Jul 2026, 15:19 UTC29 views7 reactionsread 10 August 2026
Photo

🌟😊😊😊😊😊😊😊😊😊😊 🌟🌟🌟🌟🌟🤩🤩🤩🌟🌟 🌟Он обнял меня. Обнял... Сразу при встрече. Я прошу прощения, что рассказываю обо всём не сразу, но я только сейчас могу это сделать. До этого.. Я отходил от всех вчерашних и сегодняшних событий. Он просто обнял меня. Молча, аккуратно, словно боялся сломать или навредить мне. И сразу успокоился. До того, как он это сделал я хотел спросить как он себя чувствует, но понял всё и без слов. Наверно

3🍾2🍓1🕊1

29 Jul 2026, 15:12 UTC32 views7 reactionsread 10 August 2026
Photo

😊😊😊😊😊 😊😊 😊😊😊😊 🌟🌟🌟🌟🌟🌸🌸🌸🌟🌟 🌟Всю ночь и день в голове крутилось множество мыслей. Я не мог перестать думать о нём и о том, что будет между нами. Не знаю почему так резко мне стало настолько не всё равно на это. Я думал, что несмотря на то, сколько мы прошли я смогу отпустить его в случае чего. Но я... ошибался. С его появлением на Двумернии я понял, что не могу просто отпускать его пока не буду уверен, что он в порядке

3🕊2🍓1🍾1

29 Jul 2026, 00:23 UTC30 views7 reactionsread 10 August 2026

Не могу уснуть. Чувствую себя странно. Смешанные чувства теперь по поводу этого всего. Наверное, стоит выпить успокаивающий чай и снова попытаться уснуть.

3🕊2🍾1💔1

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

Citation-graph rank

Citation-graph rank — 198,586 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 10 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.

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

“𝖣𝖺𝗇 𝖧𝖾𝗇𝗀 `無名” (@DanHeng_LiChe), 47 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/DanHeng_LiChe.

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.