Channel
TENNIS KING 👑
@tennis_football_jackpot_match
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,123subscribers
-1,854 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001528615213 |
|---|---|
| Type | Channel |
| Username | @tennis_football_jackpot_match |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/tennis_football_jackpot_match |
Topic
Sports — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 00:01 | 5,123 | -368 |
| 18 Sept 2026, 02:58 | 5,491 | -246 |
| 13 Sept 2026, 12:39 | 5,737 | -187 |
| 9 Sept 2026, 19:16 | 5,924 | -322 |
| 4 Sept 2026, 22:17 | 6,246 | -253 |
| 1 Sept 2026, 03:58 | 6,499 | -204 |
| 29 Aug 2026, 05:04 | 6,703 | -243 |
| 27 Aug 2026, 18:17 | 6,946 | no change |
| 25 Aug 2026, 21:16 | 6,946 | -16 |
| 22 Aug 2026, 20:26 | 6,962 | -15 |
| 19 Aug 2026, 09:45 | 6,977 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
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.
@jmdpredictions · 53,008
Telegram ranks this channel #11 of 34 here — alongside 33 others — read 23 August 2026
@tennis_tips_free_football_tip · 82,922
Telegram ranks this channel #13 of 46 here — alongside 45 others — read 19 August 2026
@tenis_teniss_tipss · 85,160
Telegram ranks this channel #28 of 48 here — alongside 47 others — read 19 August 2026
@Raghav_Bhai_Official · 46,029
Telegram ranks this channel #43 of 53 here — alongside 52 others — read 26 August 2026
@hittler_dada_toss_hitlar_hitlerl · 55,534
Telegram ranks this channel #57 of 63 here — alongside 62 others — read 25 August 2026
This channel appears in 5 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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“TENNIS KING 👑” (@tennis_football_jackpot_match), 5,123 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/tennis_football_jackpot_match.
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.