一手专注海外社交软件: OKC 巴豆 丘比特全系列 曼巴 大黄蜂 match AM kIS BOO juamo ins fb TN WS KaKao 全球实卡接码邮寄复接 等社交软件 东南亚交友定制软件可做上云机上号 欢迎定制海外各种app企业蓝标号 欢迎各大小盘口公司来洽谈 @XingChen680
❤1

Channel
@box160
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
268subscribers
-134 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003805786829 |
|---|---|
| Type | Channel |
| Username | @box160 |
| Description | 7x24H在线客服: @XingChen680 |
| Created | Between 1 February 2026 and 14 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 October 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 8 |
| On Telegram | t.me/box160 |
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 7 October 2026 and assigned it the closest of 31 fixed categories, at 57% 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 |
|---|---|---|
| 7 Oct 2026, 19:24 | 268 | no change |
| 1 Oct 2026, 06:16 | 268 | -10 |
| 16 Sept 2026, 14:21 | 278 | -27 |
| 7 Sept 2026, 23:36 | 305 | -96 |
| 30 Aug 2026, 16:55 | 401 | -18 |
| 23 Aug 2026, 15:47 | 419 | +14 |
| 16 Aug 2026, 20:54 | 405 | +3 |
| 8 Aug 2026, 06:30 | 402 | first reading |
13 posts held, back to 14 May 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 16 September 2026 |
|---|---|
| Posts held | 13 (14 May 2026 – 16 September 2026) |
| Views total | 220 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Oct 2026, 19:24 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 7 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 4 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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 2 of the 13 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 14 May 2026 to 16 September 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.
一手专注海外社交软件: OKC 巴豆 丘比特全系列 曼巴 大黄蜂 match AM kIS BOO juamo ins fb TN WS KaKao 全球实卡接码邮寄复接 等社交软件 东南亚交友定制软件可做上云机上号 欢迎定制海外各种app企业蓝标号 欢迎各大小盘口公司来洽谈 @XingChen680
❤1
🌟专属个人工作室|海外社交一站式服务 专业承接各类海外交友、社交软件业务,深耕行业多年,渠道稳定、成功率高,支持全地区无视限制,男号、女号均可定制,全程高效保密! 📌主营全系业务 ✅ 丘比特 全系列全套服务 ✅ 大黄蜂 专属定制、功能开通 ✅ Kismia 欧美顶级交友软件|全自定义定制,无地区壁垒,男女号全覆盖 ✅ 巴豆 全系账号、会员业务 ✅ OKC 社交账号搭建、 ✅ 领英 职业社交账号定制优化 ✅ match 专业男号定制 🌐全网社交软件全覆盖 支持 INS、FB 等主流海外交友软件,各类会员代开、账号定制、功能解锁,所有小众/主流品类均可咨询! 💪优势保障 ▪️ 渠道稳定,通过率高 ▪️ 无视地区限制,男女号均可做 ▪️ 极速接单,快速交付 ▪️ 长期售后,靠谱稳定 有需求直接滴滴,全天在线接单!🔥
❤1
百亿大盘 大户首选 澳门新葡京https://www.7333662.com/#/?c=1816GAEC bet365 https://www.g5115g.com/#/?c=4890SDWC 注册充值300送彩金88 充值1000送彩金388 优惠多多 反水高 回馈多 20-100W 提款秒到账 梦想大舞台,有梦你就来 烟中经典,盘中王者 加入我们,翻身从这一刻开始
📱📱📱📱📱📱📱📱 大量出纯私人微信🐟号 月 半年 年 全类型号 企业微信三合一均有 可扫码可带设备一起出货 欢迎各大小盘口中介来洽谈
频道的全部都有货 需要直接发消息拉群对接
市场没有统一价格,你总能遇到比我便宜的,也能遇到比我贵的,在信息透明的时代,认准一个稳定靠谱的办事人最重要‼️
星辰海外全能号商出货通知 pinned Deleted message
📱【kakao系列】📱 📱1.韩掴kakao普卡 📱2.韩掴kakao黑卡 📱3.韩掴kakao实名老号 📱4.韩掴kakao超级号 📱5.韩掴kakao企业号 韩国kakao大量到货 kakao实名大量有货
日本line 脱绑➕带绑 台湾line脱绑号 泰国line 韩国line 台湾带绑号码line 日台泰官方LINE 大量到货
OKC Boo 巴豆 穆斯林 丘比特 曼巴 AM GV KIS CMB 和谐 各种app软件可开会员 欢迎询价
https://www.internationalcupid.com 国际丘比特 https://www.latinamericancupid.com 拉丁美洲丘比特 https://www.asiandating.com 亚洲丘比特 https://www.interracialcupid.com 跨种族丘比特 https://www.afrointroductions.com 非洲丘比特 https://www.koreancupid.com 韩国丘比特 https://www.malaysiancupid.com 马来西亚丘比特 https://www.japancupid.com 日本丘比特 https://www.filipinocupid.com 菲律宾丘比特 http…
https://www.thaicupid.com/ 泰国丘比特 https://www.afrointroductions.com/ 非洲丘比特 https://www.colombiancupid.com/es 哥伦比亚丘比特 https://www.filipinocupid.com/ 菲律宾丘比特 https://www.muslima.com/ 全球穆斯林丘比特 https://www.internationalcupid.com/ 全球国际丘比特 https://www.koreancupid.com/ 韩国丘比特 https://www.japancupid.com/ 日本丘比特 https://www.eurocupid.com/ 欧洲丘比特 https://www.asiandating.com亚洲丘比特 带白金会员,需要的老板请…
Showing the 12 most recent of 13 posts we hold for @box160. 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“星辰海外全能号商出货通知” (@box160), 268 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/box160.
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.