Posted without readable text

Channel
CHELSEA MEDIA 🎥
@ChelseaFC_Media
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Telegram's recommendations · Cite this entry
22,509subscribers
+135 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001973912977 |
|---|---|
| Type | Channel |
| Username | @ChelseaFC_Media |
| Description | WORLD CHAMPIONS!!! CHELSEA: • Goals • Match Highlights • Interview videos • Funny videos ❌ No copyright intended. Credit to the owners Buy ads: https://telega.io/c/ChelseaFC_Media https://adsly.me/@ChelseaFC_Media 👨💻: @Kleenz_Mahn, @Kleenz_Mahn2 |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/ChelseaFC_Media |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 08:08 | 22,509 | +74 |
| 20 Aug 2026, 23:46 | 22,435 | -13 |
| 20 Aug 2026, 00:32 | 22,448 | -42 |
| 19 Aug 2026, 01:53 | 22,490 | -8 |
| 18 Aug 2026, 00:02 | 22,498 | -36 |
| 16 Aug 2026, 20:57 | 22,534 | +193 |
| 15 Aug 2026, 11:36 | 22,341 | -45 |
| 13 Aug 2026, 23:58 | 22,386 | -4 |
| 12 Aug 2026, 19:32 | 22,390 | +68 |
| 11 Aug 2026, 20:52 | 22,322 | -14 |
| 10 Aug 2026, 18:11 | 22,336 | -16 |
| 9 Aug 2026, 17:23 | 22,352 | -1 |
| 8 Aug 2026, 19:05 | 22,353 | -15 |
| 7 Aug 2026, 19:27 | 22,368 | -6 |
| 7 Aug 2026, 19:16 | 22,374 | no change |
| 7 Aug 2026, 19:05 | 22,374 | first reading |
Engagement
55 posts held, back to 27 July 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 36 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 17.0%
- avg views ÷ 22,509 subscribers
- Avg views / post
- 3,820
- 55 posts measured
- Reaction rate
- 0.751%
- reactions ÷ views · ER floor
- Posts in window
- 55
- of 55 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 50 of 55 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 55 (27 July 2026 – 22 August 2026) |
| Views total | 209,842 |
| Reactions total | 1,464 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 08:38 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈396
- Videos
- ≈2,880
- Links
- ≈187
Lifetime counters from Telegram’s own channel header, read 22 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 19m 41s
- Average length
- 1m 14s
Measured directly from 16 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
1,464 reactions across 50 posts, in 12 distinct kinds. The most used accounts for 91.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,342 | 91.7% | |
| 🔥 | 60 | 4.10% | |
| 👍 | 31 | 2.12% | |
| 🥰 | 7 | 0.478% | |
| 🤔 | 6 | 0.41% | |
| 👌 | 5 | 0.342% | |
| 🙏 | 4 | 0.273% | |
| 👎 | 3 | 0.205% | |
| 🎉 | 2 | 0.137% | |
| 💯 | 2 | 0.137% | |
| 💔 | 1 | 0.068% | |
| 😭 | 1 | 0.068% |
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 50 of the 55 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 1,464reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 55 most recent posts we hold, published 27 July 2026 to 22 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
Joao Pedro ✂️😮💨
❤55
Scenes! ⏮️ 📱 @ChelseaFC_Media
❤26🔥4🥰2
Posted without readable text
Previous opening day victories: Wigan 0-2 Chelsea 😤⏮️ 📱 @ChelseaFC_Media
👍22❤10
Posted without readable text
❤3
Chelsea FC: Brand New Season 📱 @ChelseaFC_Media
❤38🔥6
Posted without readable text
❤2
🇧🇷💫
❤69🔥2💯1
Posted without readable text
❤3
Ready for the 26/27 season. 💪
❤48
JOAO AGAIN! 🔵 3-1 🔴
❤30
Showing the 12 most recent of 55 posts we hold for @ChelseaFC_Media. 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.
Posts edited after publishing
@ChelseaFC_Media edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 9 August 2026
- Most recent edit
- 9 August 2026
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.
@ChelseaFcWorldWide_001 · 120,627
Telegram ranks this channel #14 of 89 here — alongside 88 others — read 14 August 2026
@Chelsea_fc_worldwide · 94,918
Telegram ranks this channel #29 of 95 here — alongside 94 others — read 16 August 2026
@CFC_ChelseaFC · 137,053
Telegram ranks this channel #30 of 94 here — alongside 93 others — read 13 August 2026
@boombet301 · 67,527
Telegram ranks this channel #88 of 90 here — alongside 89 others — read 20 August 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“CHELSEA MEDIA 🎥” (@ChelseaFC_Media), 22,509 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/ChelseaFC_Media.
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.