Channel
کتابخانه ممنوعه های واتیکان
@persianfaile
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,465subscribers
+363 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 | -1001904341745 |
|---|---|
| Type | Channel |
| Username | @persianfaile |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/persianfaile |
Topic
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Oct 2026, 09:19 | 3,465 | +20 |
| 22 Oct 2026, 17:06 | 3,445 | +17 |
| 19 Oct 2026, 08:55 | 3,428 | +13 |
| 15 Oct 2026, 22:36 | 3,415 | +13 |
| 12 Oct 2026, 16:49 | 3,402 | +22 |
| 6 Oct 2026, 12:36 | 3,380 | +45 |
| 29 Sept 2026, 17:37 | 3,335 | +60 |
| 16 Sept 2026, 09:21 | 3,275 | +17 |
| 12 Sept 2026, 20:17 | 3,258 | +12 |
| 9 Sept 2026, 23:16 | 3,246 | no change |
| 9 Sept 2026, 05:38 | 3,246 | +11 |
| 3 Sept 2026, 22:36 | 3,235 | +14 |
| 31 Aug 2026, 05:04 | 3,221 | +10 |
| 28 Aug 2026, 06:27 | 3,211 | +11 |
| 25 Aug 2026, 15:53 | 3,200 | +21 |
| 22 Aug 2026, 05:46 | 3,179 | +19 |
| 18 Aug 2026, 19:03 | 3,160 | +7 |
| 15 Aug 2026, 08:27 | 3,153 | +32 |
| 11 Aug 2026, 21:07 | 3,121 | +15 |
| 8 Aug 2026, 18:00 | 3,106 | 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.
@mohadesemohamadnezhad1 · 93,682
Telegram ranks this channel #59 of 61 here — alongside 60 others — read 17 August 2026
@ketab_mamnue · 30,564
Telegram ranks this channel #64 of 69 here — alongside 68 others — read 9 September 2026
@toseyefardiket · 60,285
Telegram ranks this channel #72 of 76 here — alongside 75 others — read 22 August 2026
@yortchi_bosjin · 26,406
Telegram ranks this channel #81 of 82 here — alongside 81 others — read 14 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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“کتابخانه ممنوعه های واتیکان” (@persianfaile), 3,465 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/persianfaile.
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.