Telegram RegisterThe public register of Telegram
Telegram profile photo for Lesestoff + Hörstoff

Channel

Lesestoff + Hörstoff

@lesestoff

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

1,153subscribers

+23 since we began measuring on 5 October 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001283340923
TypeChannel
Username@lesestoff
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 October 2026
Last confirmed live1 November 2026
Measurements held9
Confirmed unchanged2 times, most recently 1 November 2026
On Telegramt.me/lesestoff

Topic

Literature — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 19 October 2026 and assigned it the closest of 31 fixed categories, at 69% 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

1,1301,1531,141.55 October 2026 — 1,130 subscribers6 October 2026 — 1,130 subscribers9 October 2026 — 1,133 subscribers14 October 2026 — 1,136 subscribers16 October 2026 — 1,138 subscribers19 October 2026 — 1,149 subscribers22 October 2026 — 1,151 subscribers25 October 2026 — 1,152 subscribers29 October 2026 — 1,153 subscribers5 October 202629 October 2026
9 measurements spanning 24 days, net +23. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,127–1,156 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 00:471,153+1
25 Oct 2026, 21:291,152+1
22 Oct 2026, 18:471,151+2
19 Oct 2026, 22:091,149+11
16 Oct 2026, 15:151,138+2
14 Oct 2026, 01:471,136+3
9 Oct 2026, 06:191,133+3
6 Oct 2026, 04:021,130no change
5 Oct 2026, 03:171,130first 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.

Mr.Mostafa English
@Mr_Mostafa_q8_English · 19,610
Telegram ranks this channel #83 of 84 here — alongside 83 others — read 5 October 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“Lesestoff + Hörstoff” (@lesestoff), 1,153 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/lesestoff.

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.