Channel
إشراق للستيب | STEP
@eshraq5
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,795subscribers
-255 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002054706860 |
|---|---|
| Type | Channel |
| Username | @eshraq5 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/eshraq5 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 06:38 | 6,795 | -16 |
| 20 Oct 2026, 03:49 | 6,811 | -9 |
| 17 Oct 2026, 12:41 | 6,820 | -10 |
| 14 Oct 2026, 10:51 | 6,830 | -14 |
| 11 Oct 2026, 00:39 | 6,844 | -27 |
| 4 Oct 2026, 23:41 | 6,871 | -44 |
| 25 Sept 2026, 18:38 | 6,915 | -23 |
| 17 Sept 2026, 00:18 | 6,938 | -10 |
| 12 Sept 2026, 17:01 | 6,948 | -9 |
| 8 Sept 2026, 19:20 | 6,957 | -23 |
| 3 Sept 2026, 19:59 | 6,980 | -12 |
| 31 Aug 2026, 21:49 | 6,992 | -6 |
| 28 Aug 2026, 15:53 | 6,998 | -6 |
| 27 Aug 2026, 11:53 | 7,004 | no change |
| 25 Aug 2026, 23:23 | 7,004 | -15 |
| 22 Aug 2026, 23:17 | 7,019 | -13 |
| 19 Aug 2026, 15:17 | 7,032 | -9 |
| 16 Aug 2026, 22:24 | 7,041 | -9 |
| 13 Aug 2026, 18:02 | 7,050 | 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.
@saudiHD · 66,187
Telegram ranks this channel #17 of 67 here — alongside 66 others — read 20 August 2026
@SPLFHD · 33,865
Telegram ranks this channel #25 of 46 here — alongside 45 others — read 2 September 2026
@Itti10 · 31,738
Telegram ranks this channel #32 of 45 here — alongside 44 others — read 5 September 2026
@Xz_fn · 129,438
Telegram ranks this channel #32 of 56 here — alongside 55 others — read 13 August 2026
@ittihq · 49,295
Telegram ranks this channel #39 of 55 here — alongside 54 others — read 25 August 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total, of which the 5 where it ranks highest are shown above. 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“إشراق للستيب | STEP” (@eshraq5), 6,795 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/eshraq5.
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.