Channel
@e0lann
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
48,295subscribers
-1,257 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002119862543 |
|---|---|
| Type | Channel |
| Username | @e0lann |
| Description | كاتبة أنا بلـ فَنانة و مَا المِجدُ الا للِفَنانين {ومِن شَّرِ حَاسِدًا إذَا حَّسِد} "مُجرد ذكرى" |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 55 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/e0lann |
Personal blog — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 08:16 | 48,295 | -15 |
| 2 Nov 2026, 06:49 | 48,310 | +6 |
| 1 Nov 2026, 04:51 | 48,304 | -14 |
| 31 Oct 2026, 03:36 | 48,318 | -24 |
| 30 Oct 2026, 00:57 | 48,342 | -17 |
| 29 Oct 2026, 03:51 | 48,359 | +5 |
| 28 Oct 2026, 02:49 | 48,354 | -4 |
| 27 Oct 2026, 05:38 | 48,358 | +498 |
| 26 Oct 2026, 03:16 | 47,860 | -19 |
| 25 Oct 2026, 01:08 | 47,879 | -14 |
| 23 Oct 2026, 22:36 | 47,893 | -15 |
| 22 Oct 2026, 22:06 | 47,908 | -20 |
| 21 Oct 2026, 19:26 | 47,928 | -24 |
| 20 Oct 2026, 14:11 | 47,952 | -4 |
| 19 Oct 2026, 10:56 | 47,956 | -34 |
| 17 Oct 2026, 12:36 | 47,990 | -19 |
| 16 Oct 2026, 16:06 | 48,009 | +15 |
| 15 Oct 2026, 13:37 | 47,994 | -15 |
| 14 Oct 2026, 12:10 | 48,009 | -19 |
| 13 Oct 2026, 00:19 | 48,028 | first reading |
60 posts held, back to 5 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 177 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 1 November 2026 |
|---|---|
| Posts held | 60 (5 July 2026 – 1 November 2026) |
| Views total | 231,390 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 14:11 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 3 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
دخلنا شهر ميلادكِ يا فتنةَ الجمال ويا أجمل ما أهدتني الحياة شهرٌ تتزيّن أيامه لأنّ فيها وُلدتِ أنتِ وكأنّ نوفمبر لم يُخلق إلا ليحمل ذكرى ميلاد قطعةٍ من الحُسن لا تتكرر يا قمراً لا يُشبهه قمر كلّ عامٍ وأنتِ أجمل من العمر وأحلى من أعوامه أقبل شهر ميلادكِ فأقبل معه الجمالُ بأبهى صوره وكيف لا يكون شهرًا استثنائيًا وفيه وُلدت مَن لو اجتمع الحُسن في امرأةٍ لكان بعضًا من ملامحها؟
شايف الـ غصة مِن يگول: إنتهى الحُب الـ جمعنا والصور ما الها معنى؟ بالضبط حُسام تشلع گلبي من تگولها إنتهى كُلشي وما يتصلح شي كُلشي نكسر وكُل ذكرياتنا حتبقى بداخلنا
File, posted without a caption
لا يُمكنُكَ أن تُحبَّني بِخوفٍ بدونِ اندفاعٍ وشغفٍ كبيرٍ لأَنَّني إن أحببتُ احبُّ بجراءةٍ لا يَستَهويني حُبُّ الجبانِ
أستحق أن أكون الأولى بقلبك أن تكون مهووسًا بي بتصرفاتي وبعفويتي بكلامي بجمالي أن تجعل تفكيرك يقتصر بي أنا لا أحد غيري أنا بداخلك أو العدم
جمعة مُباركة كُل جمعة وأحنه سوا🤍
هل جرب أحدكُم مُتعة أن ترى مَن تُحب أمامك وتراه لدقائقٍ معدودة أنا كُنت هكذا أرى مَن أُحب لدقائق أُسافر عبر عصور الحُب بـ أكملها عندما نكون معًا حتى وصلت معه الى عصورِ مابعد الحُب …
كان مِن المُمكن إلا تنتهي هكذا بدموعٍ وخوف انتهت وكأنها لم تكُن يومًا
صباح معتم قليلًا وضحكات كثيرة وقلبٌ وجد في ابتسامتها سببًا جديدًا ليحبّ الحياة
بكُل مرة اشوف بيها نفسي أكون جدًا فخورة لأنها طموحة وشاطرة وعدها نجاح واهداف تحققت شُكرًا اليّ لأن داصبر على كُلشي
كنتُ سعيدًا بطريقة لا أستطيع وصفها سعادة بسيطة في ظاهرها، عظيمة في قلبي سعادة شخصٍ رأى من يحب فعاد إلى منزله وهو يحمل مشهدا واحدا في ذاكرته ويعيده مرارا ً وكأنّه يخشى أن تنتهي حلاوته
Photo, posted without a caption
Showing the 12 most recent of 60 posts we hold for @e0lann. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
@e0lann edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 2 posts on @e0lann as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 26 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 40 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“إيلان.” (@e0lann), 48,295 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/e0lann.
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.