Telegram RegisterThe public register of Telegram
Telegram profile photo for مذكِّرات قارِئ

Channel

مذكِّرات قارِئ

@diaryreader

On this record: Topic · Growth · Engagement · Citations · Cite this entry

2,293subscribers

-25 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-1001386819438
TypeChannel
Username@diaryreader
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 September 2026
Last confirmed live8 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/diaryreader

Topic

Literature — 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 99% 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

2,2932,3182,305.56 August 2026 — 2,318 subscribers9 August 2026 — 2,317 subscribers13 August 2026 — 2,318 subscribers16 August 2026 — 2,316 subscribers19 August 2026 — 2,314 subscribers22 August 2026 — 2,317 subscribers25 August 2026 — 2,318 subscribers28 August 2026 — 2,317 subscribers30 August 2026 — 2,315 subscribers3 September 2026 — 2,312 subscribers8 September 2026 — 2,310 subscribers12 September 2026 — 2,308 subscribers16 September 2026 — 2,307 subscribers17 September 2026 — 2,307 subscribers2 October 2026 — 2,295 subscribers8 October 2026 — 2,293 subscribers6 August 20268 October 2026
16 measurements spanning 63 days, net -25. 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 2,289–2,322 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 20:372,293-2
2 Oct 2026, 03:162,295-12
17 Sept 2026, 15:142,307no change
16 Sept 2026, 07:412,307-1
12 Sept 2026, 07:582,308-2
8 Sept 2026, 04:212,310-2
3 Sept 2026, 09:082,312-3
30 Aug 2026, 23:032,315-2
28 Aug 2026, 05:032,317-1
25 Aug 2026, 13:122,318+1
22 Aug 2026, 12:582,317+3
19 Aug 2026, 03:062,314-2
16 Aug 2026, 08:422,316-2
13 Aug 2026, 01:432,318+1
9 Aug 2026, 21:312,317-1
6 Aug 2026, 09:092,318first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“مذكِّرات قارِئ” (@diaryreader), 2,293 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/diaryreader.

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.