Telegram RegisterThe public register of Telegram
Telegram profile photo for تلاوات الشيخ د. بندر بليلة

Channel

تلاوات الشيخ د. بندر بليلة

@bandarbalilah

On this record: Topic · Previous handles · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

16,390subscribers

+78 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001086417225
TypeChannel
Username@bandarbalilah
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live17 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/bandarbalilah

Topic

Religion — 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 10 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.

Previous handles

Recorded in 2019 as “تلاوات د. بندر بليلة — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.

Growth

16,31216,39016,3517 August 2026 — 16,312 subscribers7 August 2026 — 16,319 subscribers8 August 2026 — 16,314 subscribers9 August 2026 — 16,319 subscribers10 August 2026 — 16,318 subscribers11 August 2026 — 16,322 subscribers12 August 2026 — 16,329 subscribers14 August 2026 — 16,324 subscribers15 August 2026 — 16,331 subscribers16 August 2026 — 16,329 subscribers17 August 2026 — 16,330 subscribers18 August 2026 — 16,330 subscribers19 August 2026 — 16,337 subscribers19 August 2026 — 16,332 subscribers20 August 2026 — 16,333 subscribers22 August 2026 — 16,339 subscribers23 August 2026 — 16,338 subscribers25 August 2026 — 16,334 subscribers25 August 2026 — 16,338 subscribers26 August 2026 — 16,342 subscribers27 August 2026 — 16,351 subscribers28 August 2026 — 16,356 subscribers29 August 2026 — 16,360 subscribers30 August 2026 — 16,357 subscribers31 August 2026 — 16,359 subscribers1 September 2026 — 16,358 subscribers2 September 2026 — 16,359 subscribers6 September 2026 — 16,349 subscribers9 September 2026 — 16,367 subscribers12 September 2026 — 16,374 subscribers13 September 2026 — 16,377 subscribers17 September 2026 — 16,390 subscribers7 August 202617 September 2026
32 measurements spanning 41 days, net +78. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 16,300–16,402 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
17 Sept 2026, 10:3816,390+13
13 Sept 2026, 16:5816,377+3
12 Sept 2026, 00:2016,374+7
9 Sept 2026, 16:4016,367+18
6 Sept 2026, 05:5816,349-10
2 Sept 2026, 14:1316,359+1
1 Sept 2026, 15:1316,358-1
31 Aug 2026, 18:4816,359+2
30 Aug 2026, 19:2516,357-3
29 Aug 2026, 20:1416,360+4
28 Aug 2026, 18:1816,356+5
27 Aug 2026, 17:2716,351+9
26 Aug 2026, 19:4316,342+4
25 Aug 2026, 20:5216,338+4
25 Aug 2026, 00:0316,334-4
23 Aug 2026, 13:4716,338-1
22 Aug 2026, 02:3916,339+6
20 Aug 2026, 22:5716,333+1
19 Aug 2026, 22:0716,332-5
19 Aug 2026, 01:1516,337first reading

Engagement

No public post preview. We read this entry on 18 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

تلاوات الشيخ د. ماهر المعيقلي
@almuaiqly · 44,348
Telegram ranks this channel #2 of 99 here — alongside 98 others — read 28 August 2026
تلاوات الشيخ ياسر الدوسري
@yaseeraldosry · 25,830
Telegram ranks this channel #3 of 99 here — alongside 98 others — read 13 September 2026
تلاوات الشيخ د. ياسر الدوسري
@yasseraldosry · 62,971
Telegram ranks this channel #4 of 97 here — alongside 96 others — read 28 August 2026
شؤون الأئمة والمؤذنين
@moathemam · 44,958
Telegram ranks this channel #10 of 98 here — alongside 97 others — read 28 August 2026
قناة الشيخ ناصر القطامي
@nasseralqtami · 27,535
Telegram ranks this channel #16 of 96 here — alongside 95 others — read 10 September 2026
Alafasy - مشاري راشد العفاسي
@AlafasyM · 38,515
Telegram ranks this channel #20 of 77 here — alongside 76 others — read 12 September 2026
رعد الكردي
@raadalkurdy · 26,403
Telegram ranks this channel #61 of 82 here — alongside 81 others — read 12 September 2026

This channel appears in 7 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.

“تلاوات الشيخ د. بندر بليلة” (@bandarbalilah), 16,390 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/bandarbalilah.

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.