Telegram RegisterThe public register of Telegram
Telegram profile photo for Forecast FPV

Channel

Forecast FPV

@forecast_fpv

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

24subscribers

+3 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002223025661
TypeChannel
Username@forecast_fpv
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live10 October 2026
Measurements held5
Confirmed unchanged2 times, most recently 10 October 2026
On Telegramt.me/forecast_fpv

Topic

Gaming — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 87% 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

212422.510 August 2026 — 21 subscribers11 August 2026 — 21 subscribers25 August 2026 — 22 subscribers10 September 2026 — 23 subscribers1 October 2026 — 24 subscribers10 August 20261 October 2026
5 measurements spanning 51 days, net +3. 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 21–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 05:1824+1
10 Sept 2026, 02:5623+1
25 Aug 2026, 04:4522+1
11 Aug 2026, 13:4621no change
10 Aug 2026, 22:4721first reading

Engagement

18 posts held, back to 10 May 2025 — 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 18 posts for this entry, the most recent from 7 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
5m 00s
Average length
30s

Measured directly from 10 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.

Reaction mix

65 reactions across 16 posts, in 14 distinct kinds. The most used accounts for 15.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52354654819928097201015.4%
custom 52354781220815605351015.4%
❤1015.4%
🔥1015.4%
👍69.23%
custom 522425894594992702746.15%
⚡46.15%
😱46.15%
😁23.08%
🍾11.54%
👾11.54%
🤝11.54%
🤣11.54%
🤩11.54%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 17 of the 18 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 65 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 10 May 2025 to 7 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Dec 2025, 17:34 UTC125 views3 reactionsread 11 August 2026

⏱ #Racegow5 Track 6 Трек интересный, но летал я его очень мало, потому что большую часть времени чинил вуп 🤓 📌Помимо этого успел потестить новую засечку — StarForge Вышла очень компактной и удобной: подключается по вайфай и сразу готова к использованию без долгой сборки и настройки Думаю, это самый удачный вариант для соло тренировок, который я продолжу использовать

custom 52242589459499270272custom 52354654819928097201

23 Nov 2025, 18:06 UTC351 views5 reactionsread 11 August 2026
Video

25.44 — Track 3 🏁 #racegow5

custom 52354654819928097202custom 52354781220815605352custom 52242589459499270271

10 Nov 2025, 05:26 UTC413 views8 reactionsread 11 August 2026
Video

13.92 ⏱ #racegow5

custom 52354654819928097205custom 52354781220815605352custom 52242589459499270271

26 Oct 2025, 16:38 UTC351 views6 reactionsread 11 August 2026
Video

11.15 ⏱ ForecastFPV

custom 52354781220815605355👍1

25 Oct 2025, 08:33 UTC314 views2 reactionsread 11 August 2026
Video

11.5 ForecastFPV

custom 52354654819928097202

25 Oct 2025, 08:32 UTC102 views4 reactionsread 11 August 2026

🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆 Вчера пролетел первую трассу RG на реальном дроне Несмотря на то, что трек компактный и техничный, лететь на 75 было удобно. ➡️Текущий результат - 11.5 и 9.3 в симе Остаётся пару дней до нового трека, но на выходных буду улучшать время и пробовать на лёгкой 65 ⏱ Считаю такие ивенты как и вдт хорошей тренировкой, отражающей позицию в актуальном лидерборде #racegow5

🔥2👍1custom 52354781220815605351

9 Jun 2025, 05:49 UTC156 views5 reactionsread 11 August 2026
Photo

Собрал HertzHunter на своей печатной плате, получилось довольно компактно

👍2👾1🔥1😁1

8 Jun 2025, 05:12 UTC122 views1 reactionsread 11 August 2026
Video

Лучшие 3 круга подряд с WhoopMANIA S1 Track 2

🔥1

4 Jun 2025, 17:43 UTC122 views6 reactionsread 11 August 2026
Photo

Легчайшие леды Coming Soon

🔥4😁1😱1

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

“Forecast FPV” (@forecast_fpv), 24 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/forecast_fpv.

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.