Telegram RegisterThe public register of Telegram
Telegram profile photo for DemonLord三角洲(DL)

Channel

DemonLord三角洲(DL)

@DLerend

On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

24,609subscribers

+12,788 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002358152447
TypeChannel
Username@DLerend
Created1 October 2024 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live10 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/DLerend

Topic

Gaming — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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.

Previous handles

@DLerend was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@XXLQNB6
held 9 August 2026 – 9 August 2026

Growth

11,82124,63418,227.59 August 2026 — 11,821 subscribers9 August 2026 — 11,821 subscribers10 August 2026 — 11,931 subscribers11 August 2026 — 11,926 subscribers12 August 2026 — 12,338 subscribers13 August 2026 — 13,791 subscribers14 August 2026 — 15,040 subscribers16 August 2026 — 15,877 subscribers17 August 2026 — 16,734 subscribers18 August 2026 — 16,940 subscribers19 August 2026 — 17,177 subscribers20 August 2026 — 17,420 subscribers21 August 2026 — 17,700 subscribers22 August 2026 — 17,924 subscribers24 August 2026 — 18,343 subscribers25 August 2026 — 18,461 subscribers26 August 2026 — 18,524 subscribers27 August 2026 — 18,682 subscribers28 August 2026 — 18,772 subscribers29 August 2026 — 19,162 subscribers30 August 2026 — 19,238 subscribers31 August 2026 — 19,549 subscribers1 September 2026 — 19,920 subscribers2 September 2026 — 20,141 subscribers3 September 2026 — 20,241 subscribers6 September 2026 — 20,715 subscribers9 September 2026 — 21,517 subscribers11 September 2026 — 21,892 subscribers13 September 2026 — 22,140 subscribers15 September 2026 — 22,467 subscribers17 September 2026 — 22,925 subscribers26 September 2026 — 23,409 subscribers4 October 2026 — 23,689 subscribers9 October 2026 — 23,724 subscribers13 October 2026 — 23,822 subscribers14 October 2026 — 23,935 subscribers15 October 2026 — 23,973 subscribers16 October 2026 — 23,961 subscribers17 October 2026 — 24,061 subscribers19 October 2026 — 24,029 subscribers20 October 2026 — 24,023 subscribers21 October 2026 — 24,044 subscribers22 October 2026 — 24,063 subscribers23 October 2026 — 24,053 subscribers24 October 2026 — 24,067 subscribers25 October 2026 — 24,001 subscribers26 October 2026 — 24,064 subscribers27 October 2026 — 24,105 subscribers28 October 2026 — 24,087 subscribers29 October 2026 — 24,079 subscribers30 October 2026 — 24,126 subscribers31 October 2026 — 24,180 subscribers1 November 2026 — 24,509 subscribers2 November 2026 — 24,605 subscribers4 November 2026 — 24,595 subscribers4 November 2026 — 24,634 subscribers5 November 2026 — 24,616 subscribers6 November 2026 — 24,622 subscribers10 November 2026 — 24,410 subscribers10 November 2026 — 24,609 subscribers24,6099 August 202610 November 2026
60 measurements spanning 93 days, net +12,788. 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 9,899–26,556 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
10 Nov 2026, 18:1124,609+199
10 Nov 2026, 04:2224,410-212
6 Nov 2026, 23:1524,622+6
5 Nov 2026, 21:4624,616-18
4 Nov 2026, 23:2624,634+39
4 Nov 2026, 00:1424,595-10
2 Nov 2026, 21:0924,605+96
1 Nov 2026, 20:5624,509+329
31 Oct 2026, 17:1724,180+54
30 Oct 2026, 17:1724,126+47
29 Oct 2026, 18:5924,079-8
28 Oct 2026, 19:4124,087-18
27 Oct 2026, 21:3024,105+41
26 Oct 2026, 22:4624,064+63
25 Oct 2026, 20:5924,001-66
24 Oct 2026, 18:3824,067+14
23 Oct 2026, 21:0824,053-10
22 Oct 2026, 22:3724,063+19
21 Oct 2026, 19:5124,044+21
20 Oct 2026, 17:2024,023first reading

Engagement

168 posts held, back to 1 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 106 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.211%
avg views ÷ 24,609 subscribers
Avg views / post
52.0
82 posts measured
Reaction rate
31.8%
reactions ÷ views · ER floor
Posts in window
82
of 168 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 November 2026
Posts held168 (1 October 2024 – 10 November 2026)
Views total4,267
Reactions total1,356
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 04:22 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.

What this channel posts

Video runtime
3m 23s
Average length
41s

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

2,358 reactions across 152 posts, in 9 distinct kinds. The most used accounts for 93.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2,19593.1%
❤913.86%
😭361.53%
🤩100.424%
💯70.297%
🙏60.254%
🥰50.212%
🎉40.17%
🔥40.17%

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

Measured over the 168 most recent posts we hold, published 1 October 2024 to 10 November 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

Telegram’s own ‘edited’ marker: 1 of 82 posts held from the last 30 days (1.22%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 03:48 UTC180 views46 reactionsread 10 November 2026

预计今天或者明天发布!公益

👍32🤩5❤3💯3🥰3

10 Nov 2026, 03:38 UTC≈1,290 views42 reactionsread 10 November 2026
Video

- 震撼首发|即将上线 ❤️三角洲DL公益全新算法解密注入写法 (无视现有的全部加密) 完全公益!完全公益!完全公益! 🌟DL功能介绍: 😳适配全部机型: 只要手机root了就能使用 🥵自研AI自瞄算法: 稳定使用无需搭配任何端口 🤯独家算法解密思路: ✅不闪框 ✅不卡框 ✅不遁地 ✈️更新频道: @DLerend ✈️交流群组: @DLerenl6

👍27❤7🤩5🎉3

7 Nov 2026, 15:29 UTC12 views45 reactionsread 7 November 2026
Forwarded from @pj7645

狗头公益实力破解项目如下: 如果下面也有你想玩的收费项目可以支持一下狗头破解! 🎮🎮❤️🎮🎮🎮 和平: 起源、止痛药追踪2.4.3、Faith范围、小熊维尼漏追v8.3、iosCORE、7k至臻版、黑曼巴引擎定制版、NL黑金版本、包子容器直装、02内部断点、反水追索、内核、急救包至臻版、超人强直装4.0、ME追锁内核、乌托邦容器直装、黑曼巴定制容器直装、黑曼巴注入、Aiultra俱乐部特供、ios和平精英、M416容器直装、千禾秒刷美化4.1、阿尔法直装、SK追踪内核、007pro内核、美国范围、七奉定制拦截1.2版本、Faith裸奔范围、英法国循环拦截1.6、仁济美化2.05 王者: Angel天使算法解密、千夕美化 天神hook、玄策pro解密版、千汐全局美化、EN指针版、LMK王者文件、c11解密内核、四叶草算法解密、Soul_kernel解密版、EN内部解密版本脱离服务器、ROG解密算法10.19、MG解密内核、gr…

👍45

7 Nov 2026, 10:54 UTC54 views54 reactionsread 7 November 2026

✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀

👍53❤1

Signed TGBot Pro

6 Nov 2026, 22:54 UTC32 views13 reactionsread 7 November 2026

✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀

👍13

Signed TGBot Pro

6 Nov 2026, 19:45 UTC51 views17 reactionsread 7 November 2026

半夜想要看片👀找不到资源可以进群搜索 🔍 关键词:萝莉 黑丝 御姐 少萝 白丝 老师 洛丽塔 JK 等等 ⬇️⬇️⬇️⬇️⬇️⬇️⬇️ https://t.me/sos73781 https://t.me/sos73781 https://t.me/sos73781

👍17

6 Nov 2026, 17:05 UTC41 views31 reactionsread 7 November 2026
Forwarded from @kuluomi886

🎮库洛米 v39.0.0 11.6最新更新内容 🤩库洛米公益雷达点我查看 适配新赛季版本 解决最新加密 解决最新迷雾 更新算法解密一 解决三方问题 修复陀螺仪自瞄拉闸 依旧大小地图/Ai 压枪/掩体漏打/算法解密/CPU,GPU 渲染 下载地址: https://drive.uc.cn/s/316265f7583f4?public=1 公益通用卡密: @kuluomi999 🎮工艺暗区版本点我查看 ❗️❗️➡️点我加入官方频道 ❗️❗️➡️点我加入官方群组

👍30❤1

6 Nov 2026, 10:54 UTC56 views46 reactionsread 6 November 2026

✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀

👍46

Signed TGBot Pro

5 Nov 2026, 22:54 UTC35 views13 reactionsread 6 November 2026

✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀

👍13

Signed TGBot Pro

5 Nov 2026, 10:54 UTC79 views32 reactionsread 5 November 2026

✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀

👍32

Signed TGBot Pro

4 Nov 2026, 22:57 UTC189 views16 reactionsread 5 November 2026
Photo

大肥鱼1.8三角洲公益算法/udp双解密 已适配三角洲新赛季 大肥鱼1.8下载地址: https://drive.uc.cn/s/316265f7583f4?public=1 本次更新内容如下 适配新赛季 公益卡密: @BIGFATFISH6 ❗️❗️➡️ @BIGFATFISH6 ❗️❗️➡️ @dfy998

👍13❤3

4 Nov 2026, 22:53 UTC40 views14 reactionsread 5 November 2026

✅频道主推荐 🔍TG最全soso资源搜索群🔍 https://t.me/addlist/szCQddiAA4MxZGI1 🥰点击链接一键加入🥰 😀😀😀😀😀

👍13❤1

Signed TGBot Pro

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

Posts edited after publishing

@DLerend edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
11 August 2026
Most recent edit
11 August 2026

Posts recorded as deleted after publishing

We recorded 4 posts on @DLerend as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
11 August 2026
Most recent seen missing
14 August 2026
Median time before seen missing
48 hours
Seen missing in the last 30 days
0

Forward network

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

“DemonLord三角洲(DL)” (@DLerend), 24,609 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/DLerend.

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.