Telegram RegisterThe public register of Telegram
Telegram profile photo for 米国主频道

Channel

米国主频道

@miguopro

On this record: Topic · Growth · Engagement · Posts · Cite this entry

244subscribers

-12 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-1001692161876
TypeChannel
Username@miguopro
CreatedBetween 1 December 2021 and 7 October 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/miguopro

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 44% 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

2442562507 August 2026 — 256 subscribers7 August 2026 — 256 subscribers14 August 2026 — 254 subscribers20 August 2026 — 255 subscribers27 August 2026 — 251 subscribers2 September 2026 — 249 subscribers11 September 2026 — 247 subscribers2 October 2026 — 244 subscribers7 August 20262 October 2026
8 measurements spanning 57 days, net -12. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 242–258 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 23:36244-3
11 Sept 2026, 10:38247-2
2 Sept 2026, 16:43249-2
27 Aug 2026, 11:24251-4
20 Aug 2026, 22:53255+1
14 Aug 2026, 20:36254-2
7 Aug 2026, 08:01256no change
7 Aug 2026, 07:55256first reading

Engagement

15 posts held, back to 7 October 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 15 posts for this entry, the most recent from 16 April 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Apr 2023, 04:02 UTC≈1,710 viewsread 7 August 2026
Photo

内核 仅支持ROOT 王者 300/月 明透会高风险 电报找 @SYC233 备注手机型号 q 196333077 不用刷boot的老方式,直接开即用

Signed 诗与车

7 Nov 2022, 02:24 UTC≈3,140 viewsread 7 August 2026
Photo

Photo, posted without a caption

Signed 诗与车

Showing the 12 most recent of 15 posts we hold for @miguopro. 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 2 October 2026 — this entry's latest reading, not the date you are reading this.

“米国主频道” (@miguopro), 244 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/miguopro.

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.