Channel
@sdtzpd
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
5,441subscribers
-81 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001619058639 |
|---|---|
| Type | Channel |
| Usernames | @sdtzpd @shandianzhifuxitong |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/sdtzpd |
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 12:17 | 5,441 | +9 |
| 18 Sept 2026, 09:21 | 5,432 | +2 |
| 15 Sept 2026, 06:58 | 5,430 | +1 |
| 14 Sept 2026, 02:59 | 5,429 | -31 |
| 11 Sept 2026, 19:00 | 5,460 | -7 |
| 10 Sept 2026, 01:40 | 5,467 | +3 |
| 7 Sept 2026, 01:35 | 5,464 | -9 |
| 4 Sept 2026, 13:38 | 5,473 | -7 |
| 2 Sept 2026, 01:32 | 5,480 | no change |
| 1 Sept 2026, 00:05 | 5,480 | -5 |
| 29 Aug 2026, 18:02 | 5,485 | -7 |
| 29 Aug 2026, 04:58 | 5,492 | -27 |
| 26 Aug 2026, 20:11 | 5,519 | -3 |
| 26 Aug 2026, 00:45 | 5,522 | no change |
| 25 Aug 2026, 23:30 | 5,522 | no change |
| 25 Aug 2026, 23:15 | 5,522 | first reading |
20 posts held, back to 19 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 2 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 2 August 2026. An engagement rate over an empty window would be a number about nothing.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 2 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 2 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 July 2026 to 2 August 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.
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
❤1
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
【通道名称】：支付宝固额话费原生 【通道编码】：113 【通道金额】：50 100 200 【通道成率】：70+ 【通道规则】：扛投全层120秒支付时间，包5分钟超时 收到就补，只收bc qp料。查单24小时内
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
【通道名称】：支付宝固额话费原生 【通道编码】：113 【通道金额】：50 100 200 【通道成率】：70+ 【通道规则】：扛投全层120秒支付时间，包5分钟超时 收到就补，只收bc qp料。查单24小时内
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
⚡️闪电支付开启通道： 产品金额：（50~100~200） 103 支付宝移动网厅 成率60+ 105 支付宝旗舰 成率50+ 109 支付宝电信网厅 成率60+ 111 支付宝ios话费 成率70+ 300 网厅三包话费 成率60+ 609 抖音快充话费 成率40+ 501 超级微信话费 成率50+ 506 微信联通商城原生 成率50+ 112 支付宝联通商城原生（100、200） 成率70+ 113 支付宝联通商城原生 成率70+ 116 支付宝商城原生固额10、20、30 成率70+ 119 微信商城原生固额20、30 成率60+ 203 QQ转账（100~2000） 成率40+ 204 抖音转账（100~10000） 成率40+ 303 数字人民币小额（10~100）成率70+ 304 数字人民币大额（100~3000）成率60+ 322 银联扫码（100~500）…
Showing the 12 most recent of 20 posts we hold for @sdtzpd. 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 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“闪电官方时时通知频道 永不失联：@sdtzpd” (@sdtzpd), 5,441 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/sdtzpd.
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.