Channel
@DL_182ty
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,588subscribers
+896 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004300832309 |
|---|---|
| Type | Channel |
| Username | @DL_182ty |
| Created | 16 July 2026 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/DL_182ty |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 07:36 | 1,588 | -117 |
| 10 Sept 2026, 21:21 | 1,705 | -61 |
| 5 Sept 2026, 10:38 | 1,766 | -21 |
| 1 Sept 2026, 18:35 | 1,787 | -32 |
| 29 Aug 2026, 22:45 | 1,819 | -40 |
| 26 Aug 2026, 16:26 | 1,859 | -38 |
| 23 Aug 2026, 19:37 | 1,897 | -43 |
| 20 Aug 2026, 00:22 | 1,940 | -45 |
| 16 Aug 2026, 19:23 | 1,985 | -32 |
| 13 Aug 2026, 10:14 | 2,017 | +1,365 |
| 7 Aug 2026, 07:54 | 652 | -40 |
| 6 Aug 2026, 18:15 | 692 | no change |
| 6 Aug 2026, 18:04 | 692 | first reading |
2 posts held, back to 16 July 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 1 page 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 2 posts for this entry, the most recent from 16 July 2026. An engagement rate over an empty window would be a number about nothing.
182体育 诚招代理 2026年世界杯指定投注平台 佣金比例扶持：佣金比例直达55% 人头费扶持：300–800/个 代理介绍代理: 享受4%-8%分红 辅助代理发展: 首存彩金+日存彩金+支持vip等级平移 新平台，新机遇！ 平台不饱和容易拉新 独立代理后台和专属推广短域名 会员进行游戏无需绑定手机号、不限ip 会员提款可直接提虚拟币，无需银行卡 零成本开通代理，无需任何实名认证 待遇绝对行业最高，佣金绝对行业最稳！ 选择大于努力，182体育将是您实现财富自由的不二之选！ 代理咨询： @DL182ty 双向用户点击： @DL182ty_bot 代理注册网址： 1820341.com
Channel created
Showing the 2 most recent of 2 posts we hold for @DL_182ty. 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.
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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“182体育官方招商、诚招代理合作共赢” (@DL_182ty), 1,588 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/DL_182ty.
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.