
Channel
STEFAN KARL ๐๐ช๐งโโ๏ธ
@STEFANKARLL
On this record: Topic ยท Growth ยท Engagement ยท Telegram's recommendations ยท Cite this entry
1,150subscribers
-21 since we began measuring on 18 August 2026
Risers and fallers across the register ยท movement among entries of 1,000โ3,162.
Register entry
| Telegram ID | -1001842914337 |
|---|---|
| Type | Channel |
| Username | @STEFANKARLL |
| Created | Between 1 October 2022 and 30 September 2023 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 5 October 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 2 times, most recently 19 November 2026 |
| On Telegram | t.me/STEFANKARLL |
Topic
Gambling & betting โ 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 5 October 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 11:59 | 1,150 | -1 |
| 9 Nov 2026, 21:49 | 1,151 | -3 |
| 3 Nov 2026, 08:06 | 1,154 | -3 |
| 31 Oct 2026, 07:47 | 1,157 | -8 |
| 27 Oct 2026, 22:28 | 1,165 | +2 |
| 24 Oct 2026, 17:05 | 1,163 | -1 |
| 21 Oct 2026, 09:26 | 1,164 | +5 |
| 18 Oct 2026, 06:34 | 1,159 | -5 |
| 15 Oct 2026, 05:57 | 1,164 | -6 |
| 12 Oct 2026, 07:39 | 1,170 | +4 |
| 5 Oct 2026, 14:18 | 1,166 | +5 |
| 5 Oct 2026, 04:28 | 1,161 | no change |
| 28 Sept 2026, 03:20 | 1,161 | -6 |
| 18 Sept 2026, 11:40 | 1,167 | +6 |
| 14 Sept 2026, 03:16 | 1,161 | -3 |
| 10 Sept 2026, 03:02 | 1,164 | +1 |
| 4 Sept 2026, 21:22 | 1,163 | +5 |
| 1 Sept 2026, 00:43 | 1,158 | -4 |
| 29 Aug 2026, 07:44 | 1,162 | -2 |
| 22 Aug 2026, 20:28 | 1,164 | 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.
@Fixed_Ticket_Odds ยท 35,043
Telegram ranks this channel #12 of 54 here โ alongside 53 others โ read 16 September 2026
@CorrectScore_FixedMatches_UkOdds ยท 37,439
Telegram ranks this channel #46 of 65 here โ alongside 64 others โ read 25 September 2026
@kingsolomonbets001 ยท 128,365
Telegram ranks this channel #46 of 70 here โ alongside 69 others โ read 18 August 2026
@futbol24_ng ยท 22,030
Telegram ranks this channel #52 of 57 here โ alongside 56 others โ read 5 October 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 14 November 2026 โ this entry's latest reading, not the date you are reading this.
โSTEFAN KARL ๐๐ช๐งโโ๏ธโ (@STEFANKARLL), 1,150 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/STEFANKARLL.
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.