Channel
Dbook
@Dbook5
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,539subscribers
+74 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002166033232 |
|---|---|
| Type | Channel |
| Username | @Dbook5 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Dbook5 |
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 100% 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, 09:37 | 3,539 | +19 |
| 13 Sept 2026, 19:39 | 3,520 | +24 |
| 9 Sept 2026, 18:37 | 3,496 | +18 |
| 8 Sept 2026, 13:26 | 3,478 | no change |
| 4 Sept 2026, 11:36 | 3,478 | +11 |
| 31 Aug 2026, 20:24 | 3,467 | +2 |
| 29 Aug 2026, 05:04 | 3,465 | -1 |
| 26 Aug 2026, 10:46 | 3,466 | +1 |
| 25 Aug 2026, 19:45 | 3,465 | 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.
@phfatima_5 · 34,107
Telegram ranks this channel #25 of 88 here — alongside 87 others — read 3 September 2026
@pharmacistG · 27,210
Telegram ranks this channel #32 of 76 here — alongside 75 others — read 11 September 2026
@saadm1999 · 25,968
Telegram ranks this channel #34 of 88 here — alongside 87 others — read 13 September 2026
@Farma1kon · 42,333
Telegram ranks this channel #40 of 90 here — alongside 89 others — read 29 August 2026
@Caseblu · 23,219
Telegram ranks this channel #43 of 87 here — alongside 86 others — read 19 September 2026
@Scientificpharmacists · 25,167
Telegram ranks this channel #45 of 88 here — alongside 87 others — read 14 September 2026
@hakim2398 · 49,884
Telegram ranks this channel #67 of 85 here — alongside 84 others — read 25 August 2026
@pharmaceion · 29,282
Telegram ranks this channel #78 of 84 here — alongside 83 others — read 8 September 2026
This channel appears in 8 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.
“Dbook” (@Dbook5), 3,539 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Dbook5.
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.