Photo, posted without a caption
❤120🔥106😁98🎉94👍89

Channel
@duizhang258
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,545subscribers
-3,572 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001526013867 |
|---|---|
| Type | Channel |
| Username | @duizhang258 |
| Created | 8 April 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/duizhang258 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 19:16 | 6,545 | -3,385 |
| 23 Aug 2026, 17:35 | 9,930 | -78 |
| 22 Aug 2026, 02:49 | 10,008 | -9 |
| 20 Aug 2026, 18:36 | 10,017 | -4 |
| 19 Aug 2026, 17:38 | 10,021 | -11 |
| 18 Aug 2026, 14:24 | 10,032 | -5 |
| 17 Aug 2026, 14:26 | 10,037 | -7 |
| 16 Aug 2026, 07:43 | 10,044 | -15 |
| 14 Aug 2026, 18:36 | 10,059 | -7 |
| 13 Aug 2026, 06:25 | 10,066 | -11 |
| 12 Aug 2026, 04:12 | 10,077 | -7 |
| 11 Aug 2026, 04:18 | 10,084 | -7 |
| 10 Aug 2026, 06:32 | 10,091 | -9 |
| 9 Aug 2026, 06:43 | 10,100 | -12 |
| 8 Aug 2026, 09:04 | 10,112 | -3 |
| 7 Aug 2026, 06:30 | 10,115 | -2 |
| 7 Aug 2026, 02:00 | 10,117 | no change |
| 7 Aug 2026, 01:48 | 10,117 | first reading |
15 posts held, back to 8 April 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 32 pagesof 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 15 posts for this entry, the most recent from 1 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
6,547 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 34.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 2,267 | 34.6% | |
| 🔥 | 1,209 | 18.5% | |
| 🤩 | 1,061 | 16.2% | |
| 👏 | 929 | 14.2% | |
| ❤ | 800 | 12.2% | |
| 😁 | 98 | 1.50% | |
| 🎉 | 94 | 1.44% | |
| 👍 | 89 | 1.36% |
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 5 of the 15 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 6,547reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 8 April 2022 to 1 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.
Photo, posted without a caption
❤120🔥106😁98🎉94👍89
😀超级群 (Supergroup) 的拉群优势 超级群则是正规项目运营、大社区维护、公域流量池的唯一选择。 😀【容纳海量用户,打造热闹氛围】:20万的人数上限,可以让你把所有流量集中在一个大池子里。配合“慢速模式(Slow Mode)”,可以有效防止黑客或竞争对手用垃圾机器人刷屏,方便真人用户交流。 😀【完美的沉淀与转化】:新人进群可以看到所有的历史聊天记录、置顶公告和过往的项目资质。这种“透明度”能极大提高项目的信任度,适合用来做长期转化和客户维护。 😀【方便业务交割(转让群主)】:在群组买卖或代拉人业务中,超级群支持彻底转让所有权。你帮客户把群人数拉上去后,可以一键把群主转让给客户,完成安全的业务交割。
😀原始群(普通群)的拉群优势 虽然原始群人数少且功能简陋,但它是批量暴力拉人、强拉韭菜群、炒群项目的“神兵利器”。 😀【超强的抗封能力】:因为原始群在 TG 服务器的底层架构里权限很低,Telegram 对原始群的监控远比超级群宽松。你用脚本往原始群里疯狂拉陌生人,触发 PeerFloodError(限流)或被封号的概率要低得多。 😀【适合做矩阵裂变】:很多跨境工作室喜欢用大批量的养号,疯狂创建几百个原始群,每个群只拉 150-190 人。这种“小群矩阵”不仅能绕过超级群的严格风控,而且即便其中几个群被举报封掉了,其他群依然活着,风险极低。 😀出售2022-2025原始群组 😀队长唯一联系方式: @DZ008 #原始群 #普群 #普通群
🔤🔤🔤🔤🔤 🔤🔤🔤 🔤🔤🔤🔤
😀 2023年真实老群,1号拖10群,现货秒发,量大地板价~ ———————————- 😀队长唯一联系方式: @DZ008
😀新到一些2022年的老群组,一个账号带30-50个老群,有需要的联系我。
🥰927🔥852🤩763👏561❤278
🛫Telegram老群少量到货🛫 😀2016年 😀2019年 😀2020年 😀2021年 😀2022年 😀2023年 ———————————- 😀队长唯一联系方式: @DZ008 😀双向联系: @DuizhangBot
🥰1,340❤401👏368🤩298🔥251
Channel name was changed to «队长|业务总频道|订阅通知 |@duizhang | @DZ008»
😀2023年4月份老群 😀还有8个老群号,1号10个群。 😀可单独出售,也可打包出售。 😀队长唯一联系方式: @DZ008 😀双向联系: @DuizhangBot
❤1
😀正规代开TG会员😀 😀【3个月会员】 13U/$ 😀【6个月会员】 17U/$ 😀【12个月会员】 30U/$ ———————————————— 😀只需提供用户名,正规开通,官方可查,未到期也可直接续费! 😀队长唯一联系方式: @DZ008 😀双向联系: @DuizhangBot
😀TG老群出售 😀2个月老群 😀6个月老群 😀12个月老群
😀 全球TG手机号码拉群 😀 全球TG手机号码拉群 😀 全球TG手机号码拉群 😀 全球TG手机号码拉群 😀 全球TG手机号码拉群 😀一手工作室 😀每天拉百万
Showing the 12 most recent of 15 posts we hold for @duizhang258. 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 — 334,492 of 1,622,129entries 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.
Named by 2 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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“队长|业务总频道|订阅通知 |@duizhang | @DZ008” (@duizhang258), 6,545 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/duizhang258.
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.