hi,国庆快来, BOSS 公益代理,2024/10/04 公益代理无任何质量保证,随缘使用! tg://proxy?server=223.72.20.133&port=22202&secret=eef48fb31f6f63e08891e87e1edf67cb6d636d2e6b7578756579756e2e636f6d
👍7

Channel
@bossproxy
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
373subscribers
-29 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001768705832 |
|---|---|
| Type | Channel |
| Username | @bossproxy |
| Created | Between 1 December 2021 and 17 July 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/bossproxy |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 9 Oct 2026, 21:56 | 373 | -5 |
| 30 Sept 2026, 12:15 | 378 | -5 |
| 15 Sept 2026, 17:54 | 383 | -2 |
| 8 Sept 2026, 07:16 | 385 | -6 |
| 29 Aug 2026, 14:26 | 391 | -2 |
| 22 Aug 2026, 15:14 | 393 | -8 |
| 14 Aug 2026, 19:24 | 401 | -1 |
| 7 Aug 2026, 00:03 | 402 | no change |
| 6 Aug 2026, 23:58 | 402 | first reading |
20 posts held, back to 17 July 2022 — 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 20 posts for this entry, the most recent from 4 October 2024. An engagement rate over an empty window would be a number about nothing.
53 reactions across 15 posts, in 3 distinct kinds. The most used accounts for 86.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 46 | 86.8% | |
| 🔥 | 4 | 7.55% | |
| ❤ | 3 | 5.66% |
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 18 of the 20 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 53 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 17 July 2022 to 4 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
hi,国庆快来, BOSS 公益代理,2024/10/04 公益代理无任何质量保证,随缘使用! tg://proxy?server=223.72.20.133&port=22202&secret=eef48fb31f6f63e08891e87e1edf67cb6d636d2e6b7578756579756e2e636f6d
👍7
hi,好久不见, BOSS 公益代理,2024/1/6 公益代理无任何质量保证,随缘使用! 《点击连接代理》 《点击连接代理》
👍14
hi,好久不见, BOSS 公益代理,2023/4/26 公益代理无任何质量保证,随缘使用! https://t.me/proxy?server=tg代理www.电报.com&port=23566&secret=ee8e71ceefaa37ae519422d18cd8ce75646177732e636f6d
🔥3
BOSS 公益代理,2022/3/13 公益代理无任何质量保证,随缘使用! 高速代理 《点我连接代理》 您的分享,才是我的动力!
👍1
当前可用,确定链接后需要等待5秒
👍2
BOSS 公益代理,2022/3/13 公益代理无任何质量保证,随缘使用! https://t.me/proxy?server=3.36.114.50&port=3306&secret=ee9be00f807bda754be2b52db594bb8e4f6177732e636f6d 确定连接后等待5秒,超过5秒未能成功连接请放弃
TG BOSS公益代理 2022/2/26 该代理需要连接需要等待5秒,超过5秒建议放弃使用! tg://proxy?server=13.208.168.200&port=3306&secret=ee962c5bd26c19370870351220f2d22674636c6f7564666c6172652e636f6d
收费代理已升级,季节以上,可联系客服进行迁移。@TGTGSOCKS5
🔥1
2023春节到了,新年快乐,千祥云集庆有余,百福骈臻贺新年!青山依旧在,祝福年年有!朋友,新的一年锦上添花!
TG BOSS公益代理 2022/1/15 该代理需要连接需要等待5秒,超过5秒建议放弃使用! tg://proxy?server=54.199.97.41&port=3306&secret=eec965f5a85ada8af905fefa62734ed0106177732e636f6d
👍3
回来了,明天继续更新公益代理,一切事物明天处理
TG代理,临时 https://t.me/socks?server=3.1.20.193&port=8888&user=123&pass=123
Showing the 12 most recent of 20 posts we hold for @bossproxy. 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.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“TG代理 | 飞机代理” (@bossproxy), 373 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/bossproxy.
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.