Channel
@freetgproxy
On this record: Topic · Growth · Engagement · Posts · Cite this entry
98subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001312799717 |
|---|---|
| Type | Channel |
| Username | @freetgproxy |
| Created | 25 July 2021 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/freetgproxy |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 |
|---|---|---|
| 3 Oct 2026, 17:38 | 98 | -2 |
| 3 Sept 2026, 16:21 | 100 | -1 |
| 20 Aug 2026, 10:25 | 101 | -1 |
| 9 Aug 2026, 10:01 | 102 | no change |
| 7 Aug 2026, 00:58 | 102 | first reading |
4 posts held, back to 25 July 2021 — 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 2 January 2022. An engagement rate over an empty window would be a number about nothing.
vmess://eyJhZGQiOiJneS55ZWVtLmNjIiwiYWlkIjoiMCIsImhvc3QiOiIiLCJpZCI6IjhjYjY3YTRhLTlhNTQtNDYwMS1mYThhLTI2YjIyY2M0YmVmOCIsIm5ldCI6IndzIiwicGF0aCI6Ii8iLCJwb3J0IjoiMjM0NTYiLCJwcyI6IuOAkE5BVC/lub/np7vjgJHwn4e68J+HuOa0m+adieeftiB8IOadpeiHqkBzZW5sdTAiLCJzY3kiOiJhdXRvIiwic25pIjoiIiwidGxzIjoiIiwidHlwZSI6IiIsInYiOiIyIn0=
Signed 森鹭|出一台1c1gVPS 初三随时失联
ss://[email protected]:9101#+%7c10.84Mb ss://Y2hhY2hhMjAtaWV0Zi1wb2x5MTMwNTpyNE1QNUR6RE5tQXFiQkh6YlNYdw@217.138.221.42:8389#Relay_+%7c+8.72Mb ss://[email protected]:6379#+%7c+1.48Mb ss://[email protected]:8000#+%7c21.05Mb
Signed 森鹭|出一台1c1gVPS 初三随时失联
https://t.me/proxy?server=shcm-a01.344944.xyz&port=34916&secret=ee68ede4ef8a407e4e1101d6b2e85f6715617a7572652e6d6963726f736f66742e636f6d 流量：500G
Signed 跨越长城 机场主-东哥
Channel created
Showing the 4 most recent of 4 posts we hold for @freetgproxy. 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“电报代理与节点|跨越长城” (@freetgproxy), 98 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/freetgproxy.
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.