Telegram RegisterThe public register of Telegram
Telegram profile photo for Formula Data Analysis

Channel

Formula Data Analysis

@FDataAn

On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Telegram's recommendations · Cite this entry

3,997subscribers

+59 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001933363693
TypeChannel
Username@FDataAn
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/FDataAn

Growth

3,9383,9973,967.57 August 2026 — 3,938 subscribers7 August 2026 — 3,938 subscribers8 August 2026 — 3,940 subscribers11 August 2026 — 3,950 subscribers14 August 2026 — 3,948 subscribers17 August 2026 — 3,950 subscribers21 August 2026 — 3,962 subscribers24 August 2026 — 3,975 subscribers28 August 2026 — 3,973 subscribers31 August 2026 — 3,987 subscribers3 September 2026 — 3,990 subscribers8 September 2026 — 3,997 subscribers7 August 20268 September 2026
12 measurements spanning 32 days, net +59. 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 3,929–4,006 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 09:383,997+7
3 Sept 2026, 07:553,990+3
31 Aug 2026, 01:483,987+14
28 Aug 2026, 02:453,973-2
24 Aug 2026, 20:583,975+13
21 Aug 2026, 02:583,962+12
17 Aug 2026, 17:083,950+2
14 Aug 2026, 07:563,948-2
11 Aug 2026, 10:543,950+10
8 Aug 2026, 06:223,940+2
7 Aug 2026, 12:333,938no change
7 Aug 2026, 12:203,938first reading

Engagement

17 posts held, back to 20 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages 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 17 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

166 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 54.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
9154.8%
👍3923.5%
😭1710.2%
🔥159.04%
🤔31.81%
🥰10.602%

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

Measured over the 17 most recent posts we hold, published 20 July 2026 to 7 August 2026, 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 Aug 2026, 09:20 UTC434 views3 reactionsread 8 August 2026
Photo

Which F1 Team Will Excel and Which One Will Disappoint After the Summer Break? Comment! 👇

🔥3

7 Aug 2026, 09:18 UTC456 views6 reactionsread 8 August 2026
Photo

⚙️ Engine Development Under the Previous and New Regulations 3 years of F1 development under engine freeze are still worth 2.280 s/lap: that's the average 2022→2025 improvement! Best development: Williams (-3.315s). Worst: Ferrari (-1.464s), best car at the start of '22, only 4th best by '25. Williams was 5.635s quicker in Australia 2025 than in 2022! Ferrari was SLOWER (+0.099s) in Baku 2025 compared to 2022...

5🥰1

29 Jul 2026, 14:10 UTC≈1,150 views17 reactionsread 8 August 2026
Photo

📊 Hungarian GP - Race | Race Pace Analysis 🟧 NOR remains quickest even after correcting for his additional tyre set, yet 🟦 VER was just 1 tenth behind, 🟩 ANT 0.15s behind! 🟥 Ferrari was just 4th best on the track they should have dominated (also due to traffic). 🟩 Aston's updates really worked: 8th fastest team in the race, in front of Haas, Williams, and unreliable Cadillac!

9🔥6👍2

26 Jul 2026, 19:25 UTC≈1,690 views16 reactionsread 8 August 2026
Photo

Acceleration Times: No advantage starting on the soft!

16

26 Jul 2026, 19:25 UTC≈1,400 views8 reactionsread 8 August 2026
Photo

ANT vs RUS Race Start: Notice that RUS's speed remains flat once reached 20km/h!

6🤔2

26 Jul 2026, 19:24 UTC≈1,110 views12 reactionsread 8 August 2026
Photo

📊 Hungarian GP - Race | Race Start & Acceleration Times Russell really can't catch a break: the anti-stall cost him 1.3s over 0-100 km/h! 💥 This race was yet another confirmation that Ferrari's start advantage has disappeared: all teams are now getting quick, consistent starts. Time to consider dropping the pre-start procedure? McLaren and Haas excelled, while Alpine and Audi struggled.

👍84

26 Jul 2026, 19:23 UTC853 views8 reactionsread 8 August 2026
Photo

📊 Hungarian GP - Practice 2 | Long Runs 🟩 ANT quickest, on Softs. 🟦 VER was next best, fast on Softs and still pretty quick on Mediums. 🟥 Ferrari didn't produce any stint which was either fast or long and consistent (hard to gauge). Audi looks best-of-the-rest, but Racing Bulls might keep that crown. Haas > Williams (which, however, kept very constant pace even on 25 laps tyres)! Judging by PER's consistency, C

5👍3

25 Jul 2026, 06:09 UTC964 views16 reactionsread 8 August 2026

Following FP2 and considering each car's strengths and weaknesses and the track characteristics, here are my Power Rankings: 1) 🟥 Ferrari! If Mercedes solves their issues: 2) 🟧 McL / ⬛️ Mercedes; 3) 🟦 RBR. Otherwise: 2 )🟧 McL; 3) 🟦 RBR / ⬛️ Mercedes. What's YOUR prediction? 👀

12👍4

25 Jul 2026, 06:08 UTC869 views8 reactionsread 8 August 2026
Photo

TOP SPEED: Ferrari's top speed was very good, too! And they didn't seem to be in a more powerful engine mode. Instead, RBR ran a very conservative power mode. MINISECTORS: HAM/NOR/VER minisector battle: HAM was quickest for over half the lap (53.7%); NOR for just 19% of it (but he gained significantly whenever he was quickest, losing little when he wasn't).

6👍2

25 Jul 2026, 06:07 UTC782 views8 reactionsread 8 August 2026
Photo

📊 Hungarian GP - Practice 2 | Session Overview BEST SECTOR GAPS: 🟥 Ferrari was quickest in FP2 and is the weekend's favourite thanks to these track characteristics! - 4 Straight-mode zones: Less drag → less impact of engine power, less energy to be deployed. - No energy shortage: 9MJ available in quali over a short track. - Many medium-speed corners, especially in sector 2, make SF-26's great downforce shine! Upda

6🔥2

24 Jul 2026, 05:26 UTC802 views1 reactionsread 8 August 2026

Link to know more about JMP, the software I used to perform this analysis! 👇 https://www.jmp.com/en/offers/partners?utm_source=x&utm_medium=referral&utm_campaign=fdataanalysis_en_post&utm_audience=f1race-interest&utm_content=trial

🤔1

24 Jul 2026, 05:24 UTC≈1,110 views15 reactionsread 8 August 2026
Photo

⚙️ First Aston Martin Upgrade in 2026 Aston Martin is bringing their first update this weekend; it MUST work, or they won't be admitted to races starting from around Singapore! 🚫 Their quali performance went from bad to worse: 0.220% farther from pole EACH EVENT with a robust trend (R²: 0.6). The regression predicts them going above the 107% laptime threshold 6 quali sessions from now: at that point, they won't be

11🔥4

Showing the 12 most recent of 17 posts we hold for @FDataAn. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

F1 Stream 🏁
@Formula1es · 59,739
Telegram ranks this channel #8 of 47 here — alongside 46 others — read 8 September 2026
Formula 1 News | RacePress
@formula1newses0 · 35,151
Telegram ranks this channel #13 of 74 here — alongside 73 others — read 8 September 2026
Formula1
@formula1 · 46,882
Telegram ranks this channel #14 of 70 here — alongside 69 others — read 8 September 2026
Fórmula 1 Gratis 2026 🏁 RACEFANS 🏆
@formula1gratis2026 · 71,379
Telegram ranks this channel #21 of 52 here — alongside 51 others — read 8 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“Formula Data Analysis” (@FDataAn), 3,997 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/FDataAn.

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.