Telegram RegisterThe public register of Telegram
Telegram profile photo for - JS -

Channel

- JS -

@xAlattabi

2 usernames

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

25,075subscribers

-3,000 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003978098349
TypeChannel
Usernames@ALOMDARAP @xAlattabi
CreatedBetween 1 April 2026 and 14 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live15 September 2026
Measurements held39
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/xAlattabi

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 10 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 why it has no browse page of its own yet.

Growth

128,07514,0386 August 2026 — 28,075 subscribers7 August 2026 — 28,018 subscribers8 August 2026 — 27,898 subscribers9 August 2026 — 27,806 subscribers10 August 2026 — 27,682 subscribers11 August 2026 — 27,559 subscribers12 August 2026 — 27,450 subscribers14 August 2026 — 27,339 subscribers14 August 2026 — 27,339 subscribers15 August 2026 — 27,211 subscribers16 August 2026 — 27,115 subscribers17 August 2026 — 27,051 subscribers18 August 2026 — 26,959 subscribers18 August 2026 — 26,881 subscribers19 August 2026 — 26,881 subscribers19 August 2026 — 1 subscribers19 August 2026 — 26,802 subscribers21 August 2026 — 26,708 subscribers22 August 2026 — 26,563 subscribers24 August 2026 — 26,485 subscribers25 August 2026 — 26,363 subscribers26 August 2026 — 26,287 subscribers26 August 2026 — 5 subscribers27 August 2026 — 26,179 subscribers28 August 2026 — 26,081 subscribers29 August 2026 — 26,018 subscribers29 August 2026 — 25,967 subscribers30 August 2026 — 25,923 subscribers31 August 2026 — 25,854 subscribers1 September 2026 — 25,799 subscribers1 September 2026 — 8 subscribers2 September 2026 — 25,756 subscribers4 September 2026 — 25,661 subscribers6 September 2026 — 25,539 subscribers9 September 2026 — 25,361 subscribers10 September 2026 — 11 subscribers12 September 2026 — 25,224 subscribers13 September 2026 — 25,171 subscribers15 September 2026 — 25,075 subscribers25,0756 August 202615 September 2026
39 measurements spanning 40 days, net -3,000. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 39
Measured (UTC)SubscribersChange
15 Sept 2026, 12:5725,075-96
13 Sept 2026, 20:3625,171-53
12 Sept 2026, 05:2025,224+25,213
10 Sept 2026, 04:4011-25,350
9 Sept 2026, 19:4025,361-178
6 Sept 2026, 10:4225,539-122
4 Sept 2026, 02:0125,661-95
2 Sept 2026, 14:2725,756+25,748
1 Sept 2026, 21:058-25,791
1 Sept 2026, 17:3325,799-55
31 Aug 2026, 19:1425,854-69
30 Aug 2026, 22:1525,923-44
29 Aug 2026, 22:4625,967-51
29 Aug 2026, 01:5526,018-63
28 Aug 2026, 01:3826,081-98
27 Aug 2026, 03:2226,179+26,174
26 Aug 2026, 13:035-26,282
26 Aug 2026, 06:4826,287-76
25 Aug 2026, 04:1826,363-122
24 Aug 2026, 02:0726,485first reading

Engagement

No public post preview. We read this entry on 19 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Forward network

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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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

“- JS -” (@xAlattabi), 25,075 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/xAlattabi.

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.