Channel
روُح عّليَ .
@BKKDB
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,043subscribers
-275 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002060912056 |
|---|---|
| Type | Channel |
| Username | @BKKDB |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/BKKDB |
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 13 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 |
|---|---|---|
| 9 Nov 2026, 02:21 | 4,043 | -9 |
| 5 Nov 2026, 12:21 | 4,052 | -12 |
| 2 Nov 2026, 15:08 | 4,064 | -9 |
| 30 Oct 2026, 09:09 | 4,073 | -2 |
| 27 Oct 2026, 00:40 | 4,075 | -8 |
| 24 Oct 2026, 09:26 | 4,083 | -3 |
| 21 Oct 2026, 03:30 | 4,086 | -8 |
| 18 Oct 2026, 12:04 | 4,094 | -8 |
| 15 Oct 2026, 01:19 | 4,102 | -10 |
| 12 Oct 2026, 04:02 | 4,112 | -27 |
| 5 Oct 2026, 21:42 | 4,139 | -35 |
| 28 Sept 2026, 04:55 | 4,174 | -43 |
| 18 Sept 2026, 08:37 | 4,217 | -17 |
| 14 Sept 2026, 03:39 | 4,234 | -15 |
| 10 Sept 2026, 11:21 | 4,249 | -13 |
| 4 Sept 2026, 22:41 | 4,262 | -6 |
| 4 Sept 2026, 12:55 | 4,268 | no change |
| 1 Sept 2026, 12:34 | 4,268 | -11 |
| 29 Aug 2026, 22:39 | 4,279 | -7 |
| 27 Aug 2026, 05:32 | 4,286 | 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.
@The1Holy1Quran1 · 77,754
Telegram ranks this channel #24 of 74 here — alongside 73 others — read 18 August 2026
@I2i0l · 100,331
Telegram ranks this channel #30 of 77 here — alongside 76 others — read 17 August 2026
@alruer · 63,759
Telegram ranks this channel #47 of 78 here — alongside 77 others — read 20 August 2026
@zz_zzml · 82,542
Telegram ranks this channel #47 of 77 here — alongside 76 others — read 17 August 2026
@bk_B4 · 89,498
Telegram ranks this channel #70 of 82 here — alongside 81 others — read 17 August 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“روُح عّليَ .” (@BKKDB), 4,043 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/BKKDB.
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.