Telegram RegisterThe public register of Telegram
Telegram profile photo for TeleGram免费高速代理@zhun

Channel

TeleGram免费高速代理@zhun

@TGDaiLi5

On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

4,015subscribers

-592 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001223101041
TypeChannel
Username@TGDaiLi5
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/TGDaiLi5

Growth

4,0154,6074,3117 August 2026 — 4,607 subscribers8 August 2026 — 4,586 subscribers10 August 2026 — 4,491 subscribers13 August 2026 — 4,423 subscribers16 August 2026 — 4,320 subscribers20 August 2026 — 4,249 subscribers24 August 2026 — 4,217 subscribers27 August 2026 — 4,179 subscribers30 August 2026 — 4,114 subscribers2 September 2026 — 4,075 subscribers8 September 2026 — 4,015 subscribers7 August 20268 September 2026
11 measurements spanning 32 days, net -592. 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 3,926–4,696 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 07:204,015-60
2 Sept 2026, 23:054,075-39
30 Aug 2026, 11:474,114-65
27 Aug 2026, 07:554,179-38
24 Aug 2026, 02:354,217-32
20 Aug 2026, 02:014,249-71
16 Aug 2026, 17:564,320-103
13 Aug 2026, 13:374,423-68
10 Aug 2026, 22:314,491-95
8 Aug 2026, 04:354,586-21
7 Aug 2026, 12:484,607first reading

Engagement

20 posts held, back to 19 May 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 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 20 posts for this entry, the most recent from 13 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

60 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4066.7%
👍813.3%
👏46.67%
💔23.33%
😁23.33%
🤣23.33%
🥰23.33%

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

Measured over the 20 most recent posts we hold, published 19 May 2024 to 13 June 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

6 May 2025, 05:22 UTCviews —

TeleGram免费高速代理@zhun pinned «出售飞机高级匿名 888号码 联系 @heyu318»

19 Oct 2024, 16:21 UTC≈3,490 views2 reactionsread 8 August 2026

🇭🇰南宫NG😄壹号🇬🇹问鼎🇪🇹C7🇮🇲28圈🇭🇰NG体育🌐 下载地址 禁止多ip! 【送288】 每月1-10日为一个周期 每月11-20日为一个周期 每月21-31日为一个周期 🇪🇹联系客服:@NG28io 注册就送 🎌🎌 - 🎌🎌🎌元充值彩金 😄壹号官方 yht87.top 【100送100】🔥 600送288 壹号备用1 🇭🇰南宫官方 NG28.com 【600送288】 南宫备用1 备用2 🇬🇹 问鼎 官方 awd359.top 【100送100】 问鼎备用1 🇮🇲28圈 官方 28quan.clm 【28送28】 28圈备用1 备用2 🇪🇹C7娱乐 官方 C7yule.clm 【50送50】 C7备用1 备用2 🇭🇰NG体育 官方 NGtiyu.tty 【100送100】 NG体育备用注册 下载链接 打不开关VPN 或者

2

26 May 2024, 16:34 UTC≈7,890 views21 reactionsread 8 August 2026

🇭🇰南宫NG😄壹号🇬🇹问鼎🇪🇹C7🇮🇲28圈🇭🇰NG体育🌐 下载地址 禁止多ip! 【送288】 每月1-10日为一个周期 每月11-20日为一个周期 每月21-31日为一个周期 🇪🇹联系客服:@NG28io 注册就送 🎌🎌 - 🎌🎌🎌元充值彩金 😄壹号官方 yht87.top 【100送100】🔥 600送288 壹号备用1 备用2 🇭🇰南宫官方 ngh09.vip 【600送288】 南宫备用1 备用2 备用3 🇬🇹 问鼎 官方 awd359.top 【100送100】 问鼎备用1 🇮🇲28圈 官方 28quan.clm 【28送28】 28圈备用1 备用2 备用3 🇪🇹C7娱乐 官方 C7yule.clm 【50送50】 C7备用1 备用2 备用3 🇭🇰NG体育 官方 NGtiyu.tty 【100送100】 NG体育备用注

15👍4💔2

25 May 2024, 19:40 UTC≈6,890 views22 reactionsread 8 August 2026

免费送高速代理规则: 每分享一个人使用代理,可增加自己使用时间5天 怎么算分享成功呢? 你只需要把高速代理链接复制分享给需要的人,他开启使用后,你的代理免费使用时间就会自动增5天 香港极速代理① https://t.me/proxy?server=js.cos331.com&port=50085&secret=eee8035ec34047440db7fa2bafd76a6bbc62696e672e636f6d 香港② https://t.me/proxy?server=js.cos331.com&port=50085&secret=eeae85a903c4763dede6721dc7f164150662696e672e636f6d 香港③ https://t.me/proxy?server=js.cos331.com&port=50089&secret=ee2f055af18874da438015e0547d4d334f

11👏3👍2🤣2🥰2😁2

25 May 2024, 19:40 UTC≈4,570 views0 reactionsread 8 August 2026

代理线路已经全部更新完毕 并且升级了稳定!

23 May 2024, 16:48 UTC≈4,720 views5 reactionsread 8 August 2026

🇭🇰南宫NG😄壹号🇬🇹问鼎🇪🇹C7🇮🇲28圈 下载地址 首充100送100 活跃3天且充值600送288 禁止多ip! 【送288】 每月1-10日为一个周期 每月11-20日为一个周期 每月21-31日为一个周期 彩金派发 @NG28io 😄壹号官方 yht87.top 【100送100】🔥 600送288 壹号备用1 备用2 🇭🇰南宫官方 ngh09.vip 【600送288】 南宫备用1 备用2 备用3 🇬🇹 问鼎 官方 awd359.top 【100送100】 问鼎备用1 🇮🇲28圈 官方 28quan.clm 【28送28】 28圈备用1 备用2 备用3 🇪🇹C7娱乐 官方 C7yule.clm 【50送50】 C7备用1 备用2 备用3 打不开关VPN 或者 切换Wi-Fi/流量

5

21 May 2024, 15:01 UTC≈4,040 views5 reactionsread 8 August 2026

免费送高速代理规则: 每分享一个人使用代理,可增加自己使用时间5天 怎么算分享成功呢? 你只需要把高速代理链接复制分享给需要的人,他开启使用后,你的代理免费使用时间就会自动增5天 香港极速代理① https://t.me/proxy?server=js.cos331.com&port=50085&secret=eee8035ec34047440db7fa2bafd76a6bbc62696e672e636f6d 香港② https://t.me/proxy?server=js.cos331.com&port=50085&secret=eeae85a903c4763dede6721dc7f164150662696e672e636f6d 香港③ https://t.me/proxy?server=js.cos331.com&port=50089&secret=ee2f055af18874da438015e0547d4d334f

2👍2👏1

21 May 2024, 12:55 UTC≈2,750 views1 reactionsread 8 August 2026

免费送高速代理规则: 每分享一个人使用代理,可增加自己使用时间5天 怎么算分享成功呢? 你只需要把高速代理链接复制分享给需要的人,他开启使用后,你的代理免费使用时间就会自动增5天 切记切记❗️,如没有分享给他人使用,这边后台2天过后自动清除你的使用权 新加坡1 https://t.me/proxy?server=js.cos331.com&port=50085&secret=ee01ab225645982d996851646d59da017662696e672e636f6d 新加坡2 https://t.me/proxy?server=js.cos331.com&port=50085&secret=eeae85a903c4763dede6721dc7f164150662696e672e636f6d 新加坡3 https://t.me/proxy?server=js.cos331.com&port=50085&secre

1

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

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

“TeleGram免费高速代理@zhun” (@TGDaiLi5), 4,015 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/TGDaiLi5.

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.