Telegram RegisterThe public register of Telegram
Telegram profile photo for TG代理 免费代理 每日分享免费高速代理

Channel

TG代理 免费代理 每日分享免费高速代理

@DLTG8

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

30,581subscribers

+13,700 since we began measuring on 20 August 2026

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

Register entry

Telegram ID-1004424760315
TypeChannel
Username@DLTG8
Created13 August 2026 — measured — dated from the channel’s first post
First recorded20 August 2026
Last confirmed live28 October 2026
Measurements held40
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/DLTG8

Topic

Software piracy — 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 99% 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

16,88130,58123,73120 August 2026 — 16,881 subscribers20 August 2026 — 16,881 subscribers21 August 2026 — 16,889 subscribers22 August 2026 — 16,933 subscribers24 August 2026 — 18,485 subscribers25 August 2026 — 18,510 subscribers26 August 2026 — 18,540 subscribers27 August 2026 — 18,593 subscribers28 August 2026 — 18,642 subscribers28 August 2026 — 18,674 subscribers29 August 2026 — 18,744 subscribers30 August 2026 — 18,786 subscribers31 August 2026 — 18,826 subscribers2 September 2026 — 18,847 subscribers3 September 2026 — 18,880 subscribers5 September 2026 — 18,958 subscribers8 September 2026 — 19,142 subscribers11 September 2026 — 19,320 subscribers13 September 2026 — 19,507 subscribers14 September 2026 — 19,584 subscribers16 September 2026 — 19,686 subscribers19 September 2026 — 19,810 subscribers25 September 2026 — 20,196 subscribers4 October 2026 — 20,693 subscribers8 October 2026 — 20,912 subscribers13 October 2026 — 25,164 subscribers14 October 2026 — 25,216 subscribers15 October 2026 — 25,239 subscribers16 October 2026 — 25,275 subscribers17 October 2026 — 25,310 subscribers18 October 2026 — 25,346 subscribers19 October 2026 — 25,378 subscribers20 October 2026 — 25,404 subscribers21 October 2026 — 25,435 subscribers22 October 2026 — 25,463 subscribers23 October 2026 — 25,489 subscribers24 October 2026 — 30,512 subscribers26 October 2026 — 30,548 subscribers27 October 2026 — 30,550 subscribers28 October 2026 — 30,581 subscribers20 August 202628 October 2026
40 measurements spanning 68 days, net +13,700. 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 14,826–32,636 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 40
Measured (UTC)SubscribersChange
28 Oct 2026, 06:1030,581+31
27 Oct 2026, 02:3830,550+2
26 Oct 2026, 01:1130,548+36
24 Oct 2026, 23:2730,512+5,023
23 Oct 2026, 23:4425,489+26
22 Oct 2026, 20:4625,463+28
21 Oct 2026, 15:3625,435+31
20 Oct 2026, 10:5625,404+26
19 Oct 2026, 08:0125,378+32
18 Oct 2026, 09:0925,346+36
17 Oct 2026, 12:1425,310+35
16 Oct 2026, 12:1425,275+36
15 Oct 2026, 13:0625,239+23
14 Oct 2026, 13:0425,216+52
13 Oct 2026, 03:0725,164+4,252
8 Oct 2026, 22:1620,912+219
4 Oct 2026, 11:2020,693+497
25 Sept 2026, 20:5620,196+386
19 Sept 2026, 06:3619,810+124
16 Sept 2026, 21:5719,686first reading

Engagement

94 posts held, back to 13 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 57 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.18%
avg views ÷ 30,581 subscribers
Avg views / post
1,890
36 posts measured
Reaction rate
0.458%
reactions ÷ views · ER floor
Posts in window
36
of 94 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 35 of 36 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 27 October 2026
Posts held94 (13 August 2026 – 27 October 2026)
Views total68,035
Reactions total309
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Oct 2026, 23:13 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
1m 12s
Average length
8s

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

397 reactions across 63 posts, in 8 distinct kinds. The most used accounts for 74.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍29474.1%
❤7819.6%
👎153.78%
💩30.756%
🤣30.756%
🤩20.504%
🤔10.252%
🤷‍♀10.252%

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

Measured over the 94 most recent posts we hold, published 13 August 2026 to 27 October 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

27 Oct 2026, 22:45 UTC32 views5 reactionsread 27 October 2026
Photo

10月28日免费代理已更新 🔔【延迟超低型&适用于办公业务】 😉主线路1: tg://proxy?server=45.207.197.98&port=5201&secret=eed05fc7ed6bb2638d56fe6dffd5b41e4b617a7572652e6d6963726f736f66742e636f6d 😉主线路2: tg://proxy?server=45.207.197.98&port=5202&secret=ee09fa4311dc1af4f7f55e16447cacad1d617a7572652e6d6963726f736f66742e636f6d 😊主线路3: tg://proxy?server=45.207.197.98&port=5203&secret=ee66fd0b155a00471ccc36cbeb3d442520617a7572652e6d6963726f736f66742e636f6d …

❤3👍2

27 Oct 2026, 14:30 UTC275 views9 reactionsread 27 October 2026

#频道互推 #相似推荐 ------------------------------ 📢 飞机代理|高速代理|免费代理|加速器 📢 🪩TG代理高速网-免费公益高速代理节点VPN 📢 高速代理-VPN-加速器 📢 🥇高速代理- VPN -加速器直连 📢 高速代理-免费代理-飞机代理-代理 📢 免费代理–高速代理–加速器-直连代理 📢 免费代理 高速VPN 飞机代理节点 高速代理 代理 📢 高速代理-飞机代理-免费代理-公益加速器-公益节点 📢 安卓软件破解/梯子机场 📢 青枫资源分享 | 每日免费节点分享 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励

👍7❤1🤔1

27 Oct 2026, 00:15 UTC558 viewsread 27 October 2026

#频道互推 #相似推荐 ------------------------------ 📢 北冥改文件主频道 📢 快斗美化 📢 三角洲内核频道 📢 旺财作图 街机 P图软件(官方代理) 📢 ROOT玩机资源库/Magisk/LSPosed模块分享 📢 落叶公益内核 📢 阿樂·破解软件资源分享【WhatsApp·LINE·赖· 📢 九龙•微信多开|分身|双开|WhatsApp 📢 专业服务器/cdn/域名/证书 📢 阿里云账号 阿里云国际站 阿里云服务器 阿里云代充值 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励

23 Oct 2026, 18:39 UTC≈1,770 views8 reactionsread 27 October 2026
Photo

10月24日免费代理已更新 🔔【延迟超低型&适用于办公业务】 😉主线路1: tg://proxy?server=45.207.197.98&port=5201&secret=eed05fc7ed6bb2638d56fe6dffd5b41e4b617a7572652e6d6963726f736f66742e636f6d 😉主线路2: tg://proxy?server=45.207.197.98&port=5202&secret=ee09fa4311dc1af4f7f55e16447cacad1d617a7572652e6d6963726f736f66742e636f6d 😊主线路3: tg://proxy?server=45.207.197.98&port=5203&secret=ee66fd0b155a00471ccc36cbeb3d442520617a7572652e6d6963726f736f66742e636f6d …

❤7👍1

23 Oct 2026, 13:45 UTC≈1,410 views13 reactionsread 27 October 2026
Photo

点我连接最新下载型代理

👍13

23 Oct 2026, 07:49 UTC≈1,710 views3 reactionsread 27 October 2026
Photo

10月23日免费代理已更新 🔔【延迟超低型&适用于办公业务】 😉主线路1: tg://proxy?server=45.207.197.98&port=5201&secret=eed05fc7ed6bb2638d56fe6dffd5b41e4b617a7572652e6d6963726f736f66742e636f6d 😉主线路2: tg://proxy?server=45.207.197.98&port=5202&secret=ee09fa4311dc1af4f7f55e16447cacad1d617a7572652e6d6963726f736f66742e636f6d 😊主线路3: tg://proxy?server=45.207.197.98&port=5203&secret=ee66fd0b155a00471ccc36cbeb3d442520617a7572652e6d6963726f736f66742e636f6d …

👍3

19 Oct 2026, 23:19 UTC≈2,510 views7 reactionsread 27 October 2026
Photo

10月20日免费代理已更新 🔔【延迟超低型&适用于办公业务】 😉主线路1: tg://proxy?server=45.207.197.98&port=5201&secret=eed05fc7ed6bb2638d56fe6dffd5b41e4b617a7572652e6d6963726f736f66742e636f6d 😉主线路2: tg://proxy?server=45.207.197.98&port=5202&secret=ee09fa4311dc1af4f7f55e16447cacad1d617a7572652e6d6963726f736f66742e636f6d 😊主线路3: tg://proxy?server=45.207.197.98&port=5203&secret=ee66fd0b155a00471ccc36cbeb3d442520617a7572652e6d6963726f736f66742e636f6d …

❤7

18 Oct 2026, 23:21 UTC≈2,230 views7 reactionsread 27 October 2026
Photo

10月19日免费代理已更新 🔔【延迟超低型&适用于办公业务】 😉主线路1: tg://proxy?server=45.207.197.98&port=5201&secret=eed05fc7ed6bb2638d56fe6dffd5b41e4b617a7572652e6d6963726f736f66742e636f6d 😉主线路2: tg://proxy?server=45.207.197.98&port=5202&secret=ee09fa4311dc1af4f7f55e16447cacad1d617a7572652e6d6963726f736f66742e636f6d 😊主线路3: tg://proxy?server=45.207.197.98&port=5203&secret=ee66fd0b155a00471ccc36cbeb3d442520617a7572652e6d6963726f736f66742e636f6d …

👍7

16 Oct 2026, 19:58 UTC≈2,360 views12 reactionsread 27 October 2026
Video

全宇宙最强私人代理,速度吊打全网付费代理VPN不服来战 https://fahaigg.cn

👍8👎4

16 Oct 2026, 19:57 UTC≈2,470 views6 reactionsread 27 October 2026
Photo

10月17日免费代理已更新 🔔【延迟超低型&适用于办公业务】 😉主线路1: tg://proxy?server=45.207.197.98&port=5201&secret=eed05fc7ed6bb2638d56fe6dffd5b41e4b617a7572652e6d6963726f736f66742e636f6d 😉主线路2: tg://proxy?server=45.207.197.98&port=5202&secret=ee09fa4311dc1af4f7f55e16447cacad1d617a7572652e6d6963726f736f66742e636f6d 😊主线路3: tg://proxy?server=45.207.197.98&port=5203&secret=ee66fd0b155a00471ccc36cbeb3d442520617a7572652e6d6963726f736f66742e636f6d …

👍5❤1

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

@DLTG8 edited 2 posts 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
21 August 2026
Most recent edit
21 August 2026

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

“TG代理 免费代理 每日分享免费高速代理” (@DLTG8), 30,581 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/DLTG8.

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.