需要能吃大量的车队 不罚站!
❤1

Channel
@boxiaocai8886
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
843subscribers
-87 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003893160997 |
|---|---|
| Type | Channel |
| Username | @boxiaocai8886 |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/boxiaocai8886 |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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 |
|---|---|---|
| 10 Sept 2026, 10:00 | 843 | -36 |
| 1 Sept 2026, 03:56 | 879 | -29 |
| 24 Aug 2026, 13:36 | 908 | -4 |
| 16 Aug 2026, 15:37 | 912 | -16 |
| 8 Aug 2026, 04:24 | 928 | -2 |
| 8 Aug 2026, 00:51 | 930 | no change |
| 7 Aug 2026, 18:53 | 930 | first reading |
11 posts held, back to 31 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 11 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
31 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 48.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 15 | 48.4% | |
| ❤ | 10 | 32.3% | |
| 😁 | 3 | 9.68% | |
| 👏 | 2 | 6.45% | |
| 🥰 | 1 | 3.23% |
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 7 of the 11 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 31 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 31 July 2026 to 7 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.
需要能吃大量的车队 不罚站!
❤1
有两 卡户开工!
🚦🚦🚦重申:开工前要把卡都备好了 盘口要 随时给 !!不要因为卡的原因,耽误挣钱!!! 🖲🕹🖲🕹🖲🕹
持续有量 保司法保料性保量 切客上下分 投注记录随时提供 能吃量联系我 罚站赔U
👍5❤4😁1
Photo, posted without a caption
👍8😁2🥰1
车队每天持续开工 有卡的可以联系我了
❤2
🎰✅✅😃😃😃😃😃 😃😃😃😃 😀😃😀😃😀😃😀😃😄😃😀 😃一道卡⚡️车队 1️⃣1️⃣1️⃣1️⃣ 😃一道码⚡️车队 1️⃣1️⃣1️⃣1️⃣ 😃二道卡⚡️车队 1️⃣1️⃣1️⃣1️⃣ ⚡️欢迎实力车队 大车 小车通通都是好车 欢迎迷茫想干事的兄弟 我提供平台 你展示能力 抓住机会共同致富! 料区别以及车队模式科普: 🏬 一道充值卡 🏬 二道归集料 🏬 卡U车队 🏬 人头卡 🏬 外贸卡 🏬 贷款卡 🥰🥰🥰中介奖励政策 😃😀😃😀 😃😀😃😀 🥰负责人:旺盛🥰
❤1
🎰✅✅😃😃😃😃😃 😃😃😃😃 😀😃😀😃😀😃😀😃😄😃😀 😃一道卡⚡️车队 1️⃣1️⃣1️⃣1️⃣ 😃一道码⚡️车队 1️⃣1️⃣1️⃣1️⃣ 😃二道卡⚡️车队 1️⃣1️⃣1️⃣1️⃣ ⚡️欢迎实力车队 大车 小车通通都是好车 欢迎迷茫想干事的兄弟 我提供平台 你展示能力 抓住机会共同致富! 料区别以及车队模式科普: 🏬 一道充值卡 🏬 二道归集料 🏬 卡U车队 🏬 人头卡 🏬 外贸卡 🏬 贷款卡 🥰🥰🥰中介奖励政策 😃😀😃😀 😃😀😃😀 🥰负责人:旺盛🥰
🕍🕍🕍老板们,约量要提前一天约 当天没办法约量
🕋🕋🕋上车秒射 量大 切客记录 充值记录 随时抽查!!!
👏2👍1
Photo, posted without a caption
❤2👍1
Showing the 11 most recent of 11 posts we hold for @boxiaocai8886. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“旺盛—【直盘直招】” (@boxiaocai8886), 843 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/boxiaocai8886.
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.