Channel
B1-B2-C1 Prüfung Goethe telc
@alex_deutschb1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
7,292subscribers
+399 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001705816021 |
|---|---|
| Type | Channel |
| Username | @alex_deutschb1 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/alex_deutschb1 |
Topic
Education — 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 27 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 12:59 | 7,292 | +9 |
| 30 Oct 2026, 17:16 | 7,283 | +21 |
| 27 Oct 2026, 22:17 | 7,262 | +13 |
| 24 Oct 2026, 20:18 | 7,249 | +15 |
| 21 Oct 2026, 17:40 | 7,234 | +38 |
| 18 Oct 2026, 05:30 | 7,196 | +18 |
| 14 Oct 2026, 21:29 | 7,178 | +26 |
| 11 Oct 2026, 19:01 | 7,152 | +59 |
| 5 Oct 2026, 04:39 | 7,093 | +78 |
| 26 Sept 2026, 23:37 | 7,015 | +72 |
| 17 Sept 2026, 19:59 | 6,943 | +41 |
| 13 Sept 2026, 09:21 | 6,902 | +9 |
| 11 Sept 2026, 23:49 | 6,893 | 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.
@telchochschule_c1 · 26,143
Telegram ranks this channel #7 of 79 here — alongside 78 others — read 15 September 2026
@allemand237 · 20,809
Telegram ranks this channel #14 of 78 here — alongside 77 others — read 28 September 2026
@DTBB2C1 · 23,759
Telegram ranks this channel #14 of 80 here — alongside 79 others — read 19 September 2026
@almancaogreniyorum · 34,810
Telegram ranks this channel #47 of 58 here — alongside 57 others — read 29 September 2026
@jobecuspersonalservice · 20,083
Telegram ranks this channel #47 of 61 here — alongside 60 others — read 29 September 2026
@ecehocaydsyokdilyksdil · 32,947
Telegram ranks this channel #53 of 66 here — alongside 65 others — read 11 September 2026
This channel appears in 6 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“B1-B2-C1 Prüfung Goethe telc” (@alex_deutschb1), 7,292 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/alex_deutschb1.
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.