The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

Channel
海通跑分动态频道
@paofenpianzibg
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
89subscribers
-7 since we began measuring on 28 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001604241875 |
|---|---|
| Type | Channel |
| Username | @paofenpianzibg |
| Created | Between 1 December 2021 and 9 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 11 November 2026 |
| On Telegram | t.me/paofenpianzibg |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 67% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 15:36 | 89 | -1 |
| 27 Oct 2026, 11:15 | 90 | -1 |
| 21 Oct 2026, 07:36 | 91 | -2 |
| 13 Oct 2026, 19:38 | 93 | -2 |
| 5 Oct 2026, 05:41 | 95 | -1 |
| 28 Sept 2026, 19:22 | 96 | no change |
| 28 Sept 2026, 18:48 | 96 | first reading |
Engagement
15 posts held, back to 9 January 2023 — 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 15 posts for this entry, the most recent from 8 June 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 24s
- Average length
- 12s
Measured directly from 2 videos 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.
Reaction mix
14 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 85.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 12 | 85.7% | |
| 👎 | 1 | 7.14% | |
| 😁 | 1 | 7.14% |
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 9 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 14 reactions 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 9 January 2023 to 8 June 2023, 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
海通跑分持续爆单 在别的平台没量 赚不到钱 可以尝试海通平台 日量饱满
👍2😁1
Signed 小默【海通跑分总代理】
群里某老板 越做越大 想赚钱 赶紧私聊 开户专员开户吧
👍4
Signed 小默【海通跑分总代理】
海通跑分祝大家元宵节快乐 吉祥如意 欢迎各位老板 卡商 车队 团队来对接
Signed 小默【海通跑分总代理】
群里某老板 开工了一直安排下级上来 一天比一天赚得更多
👍1
Signed 小默【海通跑分总代理】
年已过, 想赚钱的老板 都在一直发展下级 越赚越多
👎1
Signed 小默【海通跑分总代理】
海通跑分祝大家初五迎财神上门今年一路发,顺顺利利, 顺便海通欢迎车队,散户,来对接 量大 纯BC料,司法极少,保司法👍
Signed 小默【海通跑分总代理】
新的一年 想赚钱的老板 已经开始努力 发展周边朋友了 你还躺在床上 刷着视频 笑嘻嘻
Signed 小默【海通跑分总代理】
鞭炮一响黄金万两,烟花一放子孙满堂,年糕一蒸职位就升,福字这么一贴上,福气财源都茂盛,海通跑分祝君新年快乐,除夕快乐!健康开心,招财进宝!
Signed 小默【海通跑分总代理】
你要暴富,唯有在海通,纯净的体育BC料,是所有有跑分者最喜爱的料,安全可靠,量大无忧。能长期做是能持续暴富的原因,每天都在爆单,每天都在暴富式的增加收入,想要快速加入的小伙伴,请联系开户专员
Signed 小默【海通跑分总代理】
想赚钱的老板 都会一直推荐身边朋友来 自己还能抽取中间的佣金
👍1
Signed 小默【海通跑分总代理】
在别的平台没有量, 量不够吃? 海通跑分春节期间日量持续爆满,欢迎各位老板来对接
👍2
Signed 小默【海通跑分总代理】
Showing the 12 most recent of 15 posts we hold for @paofenpianzibg. 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“海通跑分动态频道” (@paofenpianzibg), 89 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/paofenpianzibg.
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.