Channel
᷂القران هُدى .
@lV4Tl
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,070subscribers
-202 since we began measuring on 2 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001985633938 |
|---|---|
| Type | Channel |
| Username | @lV4Tl |
| Created | Between 1 April 2023 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/lV4Tl |
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 27 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 21:49 | 3,070 | -12 |
| 8 Nov 2026, 00:37 | 3,082 | -9 |
| 5 Nov 2026, 06:50 | 3,091 | -13 |
| 1 Nov 2026, 23:01 | 3,104 | -6 |
| 29 Oct 2026, 23:15 | 3,110 | -12 |
| 27 Oct 2026, 00:38 | 3,122 | -6 |
| 23 Oct 2026, 21:36 | 3,128 | -6 |
| 21 Oct 2026, 06:47 | 3,134 | -6 |
| 18 Oct 2026, 13:28 | 3,140 | -9 |
| 15 Oct 2026, 09:07 | 3,149 | -9 |
| 11 Oct 2026, 23:59 | 3,158 | -22 |
| 5 Oct 2026, 07:39 | 3,180 | -26 |
| 27 Sept 2026, 00:59 | 3,206 | -26 |
| 15 Sept 2026, 22:41 | 3,232 | -16 |
| 11 Sept 2026, 23:36 | 3,248 | -16 |
| 9 Sept 2026, 21:21 | 3,264 | no change |
| 7 Sept 2026, 04:40 | 3,264 | -8 |
| 2 Sept 2026, 19:02 | 3,272 | 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.
@PilBB · 33,302
Telegram ranks this channel #3 of 62 here — alongside 61 others — read 2 September 2026
@ltv8l · 28,447
Telegram ranks this channel #5 of 70 here — alongside 69 others — read 8 September 2026
@aleppo1993 · 21,944
Telegram ranks this channel #6 of 69 here — alongside 68 others — read 19 September 2026
@IV1TII · 27,643
Telegram ranks this channel #15 of 60 here — alongside 59 others — read 8 September 2026
@J3llIj · 19,637
Telegram ranks this channel #46 of 67 here — alongside 66 others — read 26 September 2026
@Syria_a9 · 23,826
Telegram ranks this channel #53 of 63 here — alongside 62 others — read 15 September 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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“᷂القران هُدى .” (@lV4Tl), 3,070 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/lV4Tl.
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.