Channel
@bipian
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
3,115subscribers
+2,200 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002100175791 |
|---|---|
| Type | Channel |
| Username | @bipian |
| Created | 10 February 2024 — measured — dated from the channel’s first post |
| First recorded | 24 August 2026 |
| Last confirmed live | 19 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 19 October 2026 |
| On Telegram | t.me/bipian |
Marketing & affiliate — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 Oct 2026, 02:20 | 3,115 | +226 |
| 15 Oct 2026, 22:36 | 2,889 | +229 |
| 12 Oct 2026, 16:50 | 2,660 | +492 |
| 6 Oct 2026, 08:41 | 2,168 | +432 |
| 29 Sept 2026, 08:57 | 1,736 | +915 |
| 16 Sept 2026, 06:38 | 821 | -3 |
| 9 Sept 2026, 12:20 | 824 | -22 |
| 31 Aug 2026, 12:35 | 846 | -60 |
| 25 Aug 2026, 13:13 | 906 | -9 |
| 24 Aug 2026, 14:45 | 915 | first reading |
3 posts held, back to 10 February 2024 — 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 3 posts for this entry, the most recent from 3 October 2025. An engagement rate over an empty window would be a number about nothing.
【万利会出海⚡资源社群】 官方工作人员公示： ⚡官方频道： ⚡万利会出海 ： @WlHCH ⚡万利会公群 ： @WlHGQ ⚡万利会供需 ： @WlHGX ⚡骗子曝光： @bipian（避骗） ⚡官方人员： ⚡万利会管事 ： @WL222 ⚡万利会客服 ： @WlHKF ⚡会员客服专员 ： @vipWlH ⚡万利会供需客服： @WlHSS ⚡万利会微微： @WlHWW ⚡万利会妞妞： @WlHNN ⚡万利会皮皮： @WlHPP ⚡万利会福福： @WlHFF ⚡万利会如如： @WlHRR ⚡万利会崽崽： @WlHZZ ⚡万利会优优： @WlHUU ⚡万利会建群号： @WlHQQ ⚡双向客服： @WlHCHbot ⚡全网供需发布 @WlHGXbot 工作时间：早上9点-凌晨2点（特殊情况咨询24小时客服） 携手上万利会出海 共享全球万亿红利！
避骗
Channel created
Showing the 3 most recent of 3 posts we hold for @bipian. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“海外新闻社·东南亚大事件曝光” (@bipian), 3,115 subscribers as measured 19 October 2026. Telegram Register, tgregister.com/channel/bipian.
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.