
Channel
AAMIN ⚽️ SPORTS
@Wadani_sports1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,316subscribers
+36 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001816500035 |
|---|---|
| Type | Channel |
| Username | @Wadani_sports1 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Wadani_sports1 |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 18 Sept 2026, 15:42 | 2,316 | +16 |
| 17 Sept 2026, 15:28 | 2,300 | no change |
| 14 Sept 2026, 00:57 | 2,300 | +8 |
| 10 Sept 2026, 17:14 | 2,292 | +10 |
| 5 Sept 2026, 16:59 | 2,282 | -1 |
| 2 Sept 2026, 01:24 | 2,283 | +4 |
| 27 Aug 2026, 15:52 | 2,279 | +1 |
| 24 Aug 2026, 22:06 | 2,278 | -2 |
| 23 Aug 2026, 17:30 | 2,280 | 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.
@Hubaalsportts · 51,308
Telegram ranks this channel #11 of 63 here — alongside 62 others — read 24 August 2026
@midnimo18 · 31,879
Telegram ranks this channel #18 of 66 here — alongside 65 others — read 4 September 2026
@shuqaalesports · 49,489
Telegram ranks this channel #19 of 68 here — alongside 67 others — read 2 September 2026
@somtipps · 59,810
Telegram ranks this channel #19 of 64 here — alongside 63 others — read 23 August 2026
@shaxdasomalia · 5
Telegram ranks this channel #21 of 66 here — alongside 65 others — read 24 August 2026
@Shaxdomuqdisho · 37,101
Telegram ranks this channel #22 of 59 here — alongside 58 others — read 31 August 2026
@bakshiomar1 · 21,270
Telegram ranks this channel #23 of 67 here — alongside 66 others — read 24 September 2026
This channel appears in 7 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“AAMIN ⚽️ SPORTS” (@Wadani_sports1), 2,316 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Wadani_sports1.
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.