Channel
کتابخانه هما
@HOMA_PDF
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,775subscribers
+182 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002132105206 |
|---|---|
| Type | Channel |
| Username | @HOMA_PDF |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/HOMA_PDF |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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 |
|---|---|---|
| 17 Sept 2026, 21:21 | 2,775 | +16 |
| 14 Sept 2026, 00:18 | 2,759 | +25 |
| 13 Sept 2026, 14:54 | 2,734 | no change |
| 9 Sept 2026, 23:38 | 2,734 | +21 |
| 4 Sept 2026, 11:56 | 2,713 | +12 |
| 31 Aug 2026, 23:48 | 2,701 | +15 |
| 29 Aug 2026, 03:03 | 2,686 | +19 |
| 26 Aug 2026, 03:28 | 2,667 | +14 |
| 23 Aug 2026, 04:48 | 2,653 | +17 |
| 19 Aug 2026, 13:34 | 2,636 | +14 |
| 16 Aug 2026, 20:17 | 2,622 | +11 |
| 13 Aug 2026, 14:05 | 2,611 | +12 |
| 10 Aug 2026, 21:15 | 2,599 | +8 |
| 7 Aug 2026, 17:02 | 2,591 | -2 |
| 7 Aug 2026, 13:35 | 2,593 | 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.
@ketabtarikhim · 45,545
Telegram ranks this channel #7 of 88 here — alongside 87 others — read 27 August 2026
@pdf_tarikhema · 45,874
Telegram ranks this channel #11 of 79 here — alongside 78 others — read 27 August 2026
@naghde_eslamm · 37,159
Telegram ranks this channel #13 of 81 here — alongside 80 others — read 1 September 2026
@feqdanedel · 28,281
Telegram ranks this channel #37 of 80 here — alongside 79 others — read 10 September 2026
@IranAncient · 72,964
Telegram ranks this channel #55 of 82 here — alongside 81 others — read 19 August 2026
@World5History · 252
Telegram ranks this channel #75 of 82 here — alongside 81 others — read 17 August 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“کتابخانه هما” (@HOMA_PDF), 2,775 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/HOMA_PDF.
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.