😃😃😃😃😃😃😃😃😃 🙋♀️🙋♀️🙋♀️🙋♀️🙋♀️ 1.大量招收 ☹️☹️☹️☹️☹️ 微信个人 ,微信经营,微信收款单 (量大,上压就射) 缺微信收款码!来就打钱!赚钱就完了,只要是微信收款码! 🤫🤫🤫🤫🤫🤫🤫🤫🤫🤫 大量要 😀微信微信经营,微信收款单 👍 急缺信经营,⚡️⚡️收款单 秒 急缺信经营,⚡️⚡️收款单 秒 急缺收款单,⚡️⚡️收款单 秒 全网最大的量!上押秒射! 码丝滑保量!!码丝滑保量!! 📱📱📱📱📱 2.大量招收😂😂 支付宝个人,支付宝经营口令 微信个人 微信经营 大量招收 聚合 扫街车队🚗 🤣😀😀😀😀😀😀😀😀 汇率顶置 盘口直招 料子柔 🇸🇰不罚站 汇率顶置 盘口直招 料子柔 🇸🇰不罚站 想挣💰💰💰 联系 @DJZF8868 射速快🇸🇰🇸🇰🇸🇰不罚站 🇸🇰🇸🇰🇸🇰 😀😀😀😀😀 😀😀😀😀:@DJZF8868
Channel
八方集团结算频道
@BFJSXZ1010
On this record: Topic · Growth · Engagement · Posts · Cite this entry
171subscribers
-61 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003845286511 |
|---|---|
| Type | Channel |
| Username | @BFJSXZ1010 |
| Created | Between 1 February 2026 and 11 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/BFJSXZ1010 |
Topic
Hacking & security — 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 24 September 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 13:51 | 171 | -3 |
| 2 Oct 2026, 08:17 | 174 | -2 |
| 16 Sept 2026, 15:01 | 176 | -3 |
| 9 Sept 2026, 03:59 | 179 | -10 |
| 31 Aug 2026, 12:23 | 189 | -3 |
| 24 Aug 2026, 05:47 | 192 | -22 |
| 17 Aug 2026, 09:28 | 214 | -18 |
| 8 Aug 2026, 10:04 | 232 | no change |
| 7 Aug 2026, 18:33 | 232 | first reading |
Engagement
4 posts held, back to 11 February 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 4 posts for this entry, the most recent from 13 February 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Photo, posted without a caption
Photo, posted without a caption
😃😃😃😃😃😃😃😃😃 🙋♀️🙋♀️🙋♀️🙋♀️🙋♀️ 1.大量招收 ☹️☹️☹️☹️☹️ 微信个人 ,微信经营,微信收款单 (量大,上压就射) 缺微信收款码!来就打钱!赚钱就完了,只要是微信收款码! 🤫🤫🤫🤫🤫🤫🤫🤫🤫🤫 大量要 😀微信微信经营,微信收款单 👍 急缺信经营,⚡️⚡️收款单 秒 急缺信经营,⚡️⚡️收款单 秒 急缺收款单,⚡️⚡️收款单 秒 全网最大的量!上押秒射! 码丝滑保量!!码丝滑保量!! 📱📱📱📱📱 2.大量招收😂😂 支付宝个人,支付宝经营口令 微信个人 微信经营 大量招收 聚合 扫街车队🚗 🤣😀😀😀😀😀😀😀😀 汇率顶置 盘口直招 料子柔 🇸🇰不罚站 汇率顶置 盘口直招 料子柔 🇸🇰不罚站 想挣💰💰💰 联系 @DJZF8868 射速快🇸🇰🇸🇰🇸🇰不罚站 🇸🇰🇸🇰🇸🇰 😀😀😀😀😀 😀😀😀😀:@DJZF8868
Showing the 4 most recent of 4 posts we hold for @BFJSXZ1010. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“八方集团结算频道” (@BFJSXZ1010), 171 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/BFJSXZ1010.
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.