Channel
Books on Philosophy
@booksonphilosophy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
8,453subscribers
+339 since we began measuring on 6 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001090005023 |
|---|---|
| Type | Channel |
| Username | @booksonphilosophy |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/booksonphilosophy |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 30 Oct 2026, 11:48 | 8,453 | +17 |
| 27 Oct 2026, 01:59 | 8,436 | +5 |
| 24 Oct 2026, 11:46 | 8,431 | +18 |
| 21 Oct 2026, 11:49 | 8,413 | +1 |
| 18 Oct 2026, 05:41 | 8,412 | +17 |
| 14 Oct 2026, 23:56 | 8,395 | +8 |
| 11 Oct 2026, 12:56 | 8,387 | +37 |
| 5 Oct 2026, 00:41 | 8,350 | +85 |
| 25 Sept 2026, 22:42 | 8,265 | +74 |
| 17 Sept 2026, 09:37 | 8,191 | +35 |
| 13 Sept 2026, 10:37 | 8,156 | +25 |
| 9 Sept 2026, 09:19 | 8,131 | +17 |
| 6 Sept 2026, 12:41 | 8,114 | no change |
| 6 Sept 2026, 09:47 | 8,114 | 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.
@philosophybooks · 19,553
Telegram ranks this channel #7 of 64 here — alongside 63 others — read 1 October 2026
@Sanjeev_thakur_sir_pdf_notes · 21,919
Telegram ranks this channel #57 of 58 here — alongside 57 others — read 22 September 2026
@bookspsychology101 · 32,025
Telegram ranks this channel #58 of 59 here — alongside 58 others — read 6 September 2026
@LawPrepJudiciary · 23,877
Telegram ranks this channel #72 of 82 here — alongside 81 others — read 17 September 2026
@ilmnafsi · 31,600
Telegram ranks this channel #88 of 93 here — alongside 92 others — read 6 September 2026
This channel appears in 5 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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“Books on Philosophy” (@booksonphilosophy), 8,453 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/booksonphilosophy.
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.