Channel
قرآن | Quran
@E_EEN1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,207subscribers
-115 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002021008652 |
|---|---|
| Type | Channel |
| Username | @E_EEN1 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 October 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/E_EEN1 |
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 3 October 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 |
|---|---|---|
| 3 Nov 2026, 17:17 | 1,207 | -4 |
| 31 Oct 2026, 13:06 | 1,211 | -3 |
| 28 Oct 2026, 15:57 | 1,214 | -5 |
| 25 Oct 2026, 22:35 | 1,219 | -5 |
| 23 Oct 2026, 02:45 | 1,224 | -5 |
| 20 Oct 2026, 05:08 | 1,229 | -6 |
| 17 Oct 2026, 14:27 | 1,235 | -3 |
| 14 Oct 2026, 19:42 | 1,238 | -4 |
| 11 Oct 2026, 10:41 | 1,242 | -4 |
| 4 Oct 2026, 20:40 | 1,246 | -13 |
| 3 Oct 2026, 02:55 | 1,259 | no change |
| 25 Sept 2026, 18:57 | 1,259 | -15 |
| 15 Sept 2026, 08:38 | 1,274 | -9 |
| 11 Sept 2026, 14:21 | 1,283 | -10 |
| 7 Sept 2026, 07:57 | 1,293 | -5 |
| 2 Sept 2026, 17:57 | 1,298 | -6 |
| 30 Aug 2026, 18:27 | 1,304 | -3 |
| 27 Aug 2026, 11:02 | 1,307 | -1 |
| 24 Aug 2026, 14:37 | 1,308 | -8 |
| 20 Aug 2026, 22:44 | 1,316 | 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.
@ssc_tasea · 25,469
Telegram ranks this channel #10 of 84 here — alongside 83 others — read 12 September 2026
@English_Shihabi · 20,046
Telegram ranks this channel #29 of 71 here — alongside 70 others — read 1 October 2026
@Soezana · 82,757
Telegram ranks this channel #55 of 77 here — alongside 76 others — read 17 August 2026
@Syrian_universities23 · 23,918
Telegram ranks this channel #64 of 81 here — alongside 80 others — read 15 September 2026
This channel appears in 4 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“قرآن | Quran” (@E_EEN1), 1,207 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/E_EEN1.
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.