Channel
Persian Audio Books
@PersianAudioBooks1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,742subscribers
+294 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001433628005 |
|---|---|
| Type | Channel |
| Username | @PersianAudioBooks1 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 2 times, most recently 30 October 2026 |
| On Telegram | t.me/PersianAudioBooks1 |
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 12 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Oct 2026, 16:46 | 6,742 | +31 |
| 24 Oct 2026, 15:37 | 6,711 | +10 |
| 21 Oct 2026, 08:17 | 6,701 | +35 |
| 18 Oct 2026, 16:46 | 6,666 | +3 |
| 15 Oct 2026, 22:28 | 6,663 | +7 |
| 12 Oct 2026, 17:38 | 6,656 | +29 |
| 5 Oct 2026, 23:15 | 6,627 | +23 |
| 29 Sept 2026, 01:22 | 6,604 | +55 |
| 16 Sept 2026, 06:56 | 6,549 | +8 |
| 12 Sept 2026, 06:00 | 6,541 | +9 |
| 8 Sept 2026, 10:41 | 6,532 | +20 |
| 2 Sept 2026, 23:58 | 6,512 | +10 |
| 30 Aug 2026, 12:55 | 6,502 | -15 |
| 28 Aug 2026, 12:02 | 6,517 | no change |
| 27 Aug 2026, 09:24 | 6,517 | +12 |
| 24 Aug 2026, 16:12 | 6,505 | +19 |
| 21 Aug 2026, 06:23 | 6,486 | +20 |
| 18 Aug 2026, 01:07 | 6,466 | +10 |
| 14 Aug 2026, 16:48 | 6,456 | +9 |
| 10 Aug 2026, 23:17 | 6,447 | 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.
@soutidastan · 95,182
Telegram ranks this channel #7 of 80 here — alongside 79 others — read 16 August 2026
@book44_book44 · 33,046
Telegram ranks this channel #8 of 63 here — alongside 62 others — read 4 September 2026
@farsi_pod · 20,846
Telegram ranks this channel #50 of 73 here — alongside 72 others — read 26 September 2026
@sh_n_halloo · 25,682
Telegram ranks this channel #67 of 91 here — alongside 90 others — read 13 September 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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“Persian Audio Books” (@PersianAudioBooks1), 6,742 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/PersianAudioBooks1.
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.