Telegram RegisterThe public register of Telegram
Telegram profile photo for 熱帶氣旋調侃

Channel

熱帶氣旋調侃

@taifuu

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

114subscribers

-1 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-1001339423240
TypeChannel
Username@taifuu
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/taifuu

Topic

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

113116114.57 August 2026 — 115 subscribers9 August 2026 — 115 subscribers7 September 2026 — 116 subscribers15 September 2026 — 115 subscribers29 September 2026 — 113 subscribers9 October 2026 — 114 subscribers1147 August 20269 October 2026
6 measurements spanning 62 days, net -1. 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 113–116 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 10:17114+1
29 Sept 2026, 08:39113-2
15 Sept 2026, 09:56115-1
7 Sept 2026, 07:20116+1
9 Aug 2026, 05:47115no change
7 Aug 2026, 23:45115first reading

Engagement

15 posts held, back to 1 June 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 15 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Aug 2026, 14:57 UTC28 viewsread 9 August 2026

现在看, 12W 将会在明天 +9 区的中午前后在南大东岛的北方 100km 附近通过, 现时 JMA 对大东岛地方发布了大浪警报

11 Jul 2026, 01:20 UTC87 viewsread 9 August 2026
Photo

石垣島的雷达活了下来, 机场的自动气象台录得最低最低气压是 956

6 Jul 2026, 07:26 UTC77 viewsread 9 August 2026

關島的雷達已經停止更新了一段時間了, 不知道是不是被吹壞了

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

“熱帶氣旋調侃” (@taifuu), 114 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/taifuu.

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.