Telegram RegisterThe public register of Telegram
Telegram profile photo for سَلمــىٰ

Channel

سَلمــىٰ

@ssalmaezzeldin

On this record: Topic · Growth · Engagement · Citations · Cite this entry

1,374subscribers

+39 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003637843414
TypeChannel
Username@ssalmaezzeldin
Description﴿ قَالَ رَبِّ بِمَا أَنْعَمْتَ عَلَيَّ فَلَنْ أَكُونَ ظَهِيرًا لِّلْمُجْرِمِينَ﴾ [القصص: 17] https://tellonym.me/archive.s.alma
First recorded30 September 2026
Last confirmed live30 September 2026
Measurements held15
On Telegramt.me/ssalmaezzeldin

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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

1,3351,3801,357.57 August 2026 — 1,335 subscribers10 August 2026 — 1,367 subscribers14 August 2026 — 1,366 subscribers17 August 2026 — 1,369 subscribers20 August 2026 — 1,365 subscribers23 August 2026 — 1,368 subscribers27 August 2026 — 1,375 subscribers29 August 2026 — 1,377 subscribers2 September 2026 — 1,379 subscribers6 September 2026 — 1,380 subscribers11 September 2026 — 1,377 subscribers14 September 2026 — 1,379 subscribers19 September 2026 — 1,378 subscribers28 September 2026 — 1,374 subscribers30 September 2026 — 1,374 subscribers1,3747 August 202630 September 2026
15 measurements spanning 54 days, net +39. 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 1,328–1,387 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 16:581,374no change
28 Sept 2026, 07:181,374-4
19 Sept 2026, 03:381,378-1
14 Sept 2026, 17:151,379+2
11 Sept 2026, 05:391,377-3
6 Sept 2026, 11:591,380+1
2 Sept 2026, 05:421,379+2
29 Aug 2026, 20:331,377+2
27 Aug 2026, 05:271,375+7
23 Aug 2026, 22:331,368+3
20 Aug 2026, 09:561,365-4
17 Aug 2026, 17:281,369+3
14 Aug 2026, 04:151,366-1
10 Aug 2026, 19:161,367+32
7 Aug 2026, 07:471,335first 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.

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.

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 30 September 2026 — this entry's latest reading, not the date you are reading this.

“سَلمــىٰ” (@ssalmaezzeldin), 1,374 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/ssalmaezzeldin.

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.