✅✅✅✅✅尊敬的老板: 8608 支付宝移动网厅(无纠纷) 8602 支付宝iOS移动网厅H5 8601 支付宝H5双端移动网厅 通道统一规则‼️: 扛投、全层、查单24h、支付时间120秒 1.包重复支付 2.包修改支付方式(会员直接转账这种不包) 3.包修改金额(多充回调订单,少充充值金额扣预付) 4.包骚扰 5.超时支付不退不补。 【禁止使用他人代付账户付款,导致掉单不退不补】 以上通道正常开启‼️‼️‼️‼️ @所有人 联通维护中 @所有人 ‼️‼️‼️‼️ 联通维护中 @所有人 ‼️‼️‼️‼️ 联通维护中 @所有人 ‼️‼️‼️‼️ 联通维护中 @所有人 ‼️‼️‼️‼️

Channel
海棠支付广播频道
@haitangzhifuguangbo
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
90subscribers
+1 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003462708471 |
|---|---|
| Type | Channel |
| Username | @haitangzhifuguangbo |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/haitangzhifuguangbo |
Topic
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 00:45 | 90 | +2 |
| 3 Oct 2026, 09:01 | 88 | -1 |
| 1 Sept 2026, 10:24 | 89 | -1 |
| 25 Aug 2026, 02:14 | 90 | +1 |
| 16 Aug 2026, 19:30 | 89 | no change |
| 16 Aug 2026, 19:15 | 89 | first reading |
Engagement
20 posts held, back to 27 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 20 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
通道106 支付宝联通商城0掉单,50 100 200各面值成功率稳定!加速冲‼️‼️‼️ 各位老板,成功率稳定50+ + ! 老板们开起来 加速冲‼️‼️‼️@所有人
通道106 支付宝联通商城0掉单,50 100 200各面值成功率稳定!加速冲‼️‼️‼️ 各位老板,成功率稳定50+ + ! 老板们开起来 加速冲‼️‼️‼️@所有人
通道106 支付宝联通商城0掉单,50 100 200各面值成功率稳定!加速冲‼️‼️‼️ 各位老板,成功率稳定50+ + ! 老板们开起来 加速冲‼️‼️‼️@所有人
通道106 支付宝联通商城0掉单,50 100 200各面值成功率稳定!加速冲‼️‼️‼️ 各位老板,成功率稳定50+ + ! 老板们开起来 加速冲‼️‼️‼️@所有人
✅✅✅✅✅尊敬的老板: 8612 支付宝联通网厅 8611 微信联通网厅 8610 微信原生H5 8609 支付宝联通商城原生 8608 支付宝移动网厅(无纠纷) 8606 支付宝三网联通H5 8602 支付宝iOS移动网厅H5 8601 支付宝H5双端移动网厅 通道统一规则‼️: 扛投、全层、查单24h、支付时间120秒 1.包重复支付 2.包修改支付方式(会员直接转账这种不包) 3.包修改金额(多充回调订单,少充充值金额扣预付) 4.包骚扰 5.超时支付不退不补。 【禁止使用他人代付账户付款,导致掉单不退不补】 以上通道正常开启‼️‼️‼️‼️ @所有人
✅✅✅✅✅尊敬的老板: 8612 支付宝联通网厅 8611 微信联通网厅 8610 微信原生H5 8609 支付宝联通商城原生 8608 支付宝移动网厅(无纠纷) 8606 支付宝三网联通H5 8602 支付宝iOS移动网厅H5 8601 支付宝H5双端移动网厅 通道统一规则‼️: 扛投、全层、查单24h、支付时间120秒 1.包重复支付 2.包修改支付方式(会员直接转账这种不包) 3.包修改金额(多充回调订单,少充充值金额扣预付) 4.包骚扰 5.超时支付不退不补。 【禁止使用他人代付账户付款,导致掉单不退不补】 以上通道正常开启‼️‼️‼️‼️ @所有人
❌❌❌尊敬的老板: 8612 支付宝联通网厅 8611 微信联通网厅 8610 微信原生H5 8609 支付宝联通商城原生 8608 支付宝移动网厅(无纠纷) 8606 支付宝三网联通H5 8602 支付宝iOS移动网厅H5 8601 支付宝H5双端移动网厅 所有通道 将在 23时30分 进行日切,麻烦各位老板们准时调整一下!!过点继续再战!!! 祝各位老板财源广进 八方来财 @所有人
通道106 支付宝联通商城0掉单,50 100 200各面值成功率稳定!加速冲‼️‼️‼️ 各位老板,成功率稳定50+ + ! 老板们开起来 加速冲‼️‼️‼️@所有人
✅✅✅✅✅尊敬的老板: 8612 支付宝联通网厅 8611 微信联通网厅 8610 微信原生H5 8609 支付宝联通商城原生 8608 支付宝移动网厅(无纠纷) 8606 支付宝三网联通H5 8602 支付宝iOS移动网厅H5 8601 支付宝H5双端移动网厅 通道统一规则‼️: 扛投、全层、查单24h、支付时间120秒 1.包重复支付 2.包修改支付方式(会员直接转账这种不包) 3.包修改金额(多充回调订单,少充充值金额扣预付) 4.包骚扰 5.超时支付不退不补。 【禁止使用他人代付账户付款,导致掉单不退不补】 以上通道正常开启‼️‼️‼️‼️ @所有人
通道106 支付宝联通商城0掉单,50 100 200各面值成功率稳定!加速冲‼️‼️‼️ 各位老板,成功率稳定50+ + ! 老板们开起来 加速冲‼️‼️‼️@所有人
通道106 支付宝联通商城0掉单,50 100 200各面值成功率稳定!加速冲‼️‼️‼️ 各位老板,成功率稳定50+ + ! 老板们开起来 加速冲‼️‼️‼️@所有人
Showing the 12 most recent of 20 posts we hold for @haitangzhifuguangbo. 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.
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.
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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“海棠支付广播频道” (@haitangzhifuguangbo), 90 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/haitangzhifuguangbo.
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.