Channel
Speeeedy Premium
@speeeedypremium
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,044subscribers
+91 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001457875143 |
|---|---|
| Type | Channel |
| Username | @speeeedypremium |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 3 times, most recently 4 November 2026 |
| On Telegram | t.me/speeeedypremium |
Topic
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 11:28 | 3,044 | +5 |
| 22 Oct 2026, 15:41 | 3,039 | +8 |
| 19 Oct 2026, 17:36 | 3,031 | +3 |
| 16 Oct 2026, 08:36 | 3,028 | +12 |
| 13 Oct 2026, 00:10 | 3,016 | +9 |
| 6 Oct 2026, 23:15 | 3,007 | +17 |
| 29 Sept 2026, 15:40 | 2,990 | +14 |
| 19 Sept 2026, 10:40 | 2,976 | -2 |
| 15 Sept 2026, 04:56 | 2,978 | +9 |
| 11 Sept 2026, 21:42 | 2,969 | no change |
| 11 Sept 2026, 05:41 | 2,969 | +10 |
| 6 Sept 2026, 18:01 | 2,959 | +10 |
| 2 Sept 2026, 12:45 | 2,949 | -2 |
| 30 Aug 2026, 13:23 | 2,951 | -4 |
| 25 Aug 2026, 03:12 | 2,955 | +3 |
| 15 Aug 2026, 16:24 | 2,952 | +2 |
| 9 Aug 2026, 19:32 | 2,950 | -2 |
| 7 Aug 2026, 00:53 | 2,952 | -1 |
| 6 Aug 2026, 14:54 | 2,953 | 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.
@fresh_electronic_music · 23,101
Telegram ranks this channel #5 of 60 here — alongside 59 others — read 19 September 2026
@record_playlists · 28,769
Telegram ranks this channel #75 of 90 here — alongside 89 others — read 10 September 2026
This channel appears in 2 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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“Speeeedy Premium” (@speeeedypremium), 3,044 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/speeeedypremium.
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.