Telegram RegisterThe public register of Telegram
Telegram profile photo for كُلشي يخُصني.

Channel

كُلشي يخُصني.

@a20s20aa

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

10subscribers

+0 since we began measuring on 19 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001905074851
TypeChannel
Username@a20s20aa
Created4 May 2023measured — dated from the channel’s first post
First recorded19 September 2026
Last confirmed live19 September 2026
Measurements held2
On Telegramt.me/a20s20aa

Growth

1019 Sept 2026, 02:47 — 10 subscribers19 Sept 2026, 03:22 — 10 subscribers19 Sept 2026, 02:4719 Sept 2026, 03:22
2 measurements taken within a single day. 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 9–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 03:2210no change
19 Sept 2026, 02:4710first reading

Engagement

4 posts held, back to 4 May 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 4 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 19 September 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.

Recent posts

4 Jun 2026, 19:14 UTC267 viewsread 19 September 2026

https://t.me/+rERdekkV_401YjUy قناتنا الخاصَّـة فقط للنِساء.

4 Jun 2026, 19:14 UTC215 viewsread 19 September 2026

قَناتنا الأَساسيَّة | @a20s20a قَناتي لمواهبي المُتواضِعة | @X_55To مُتجري للمَلابِس النِسائية وملابس الأَطفال وغَيرُها *للنِساء* لاأُحلل دخُول الرجال وغير مَبري الذمة لِمن يدخُل او يتصفّح المَنشورات |@Fashion_syn مُتجري اللُخ للمُنتجات النِسائية، نوعًا ما انشُر اشياء رجالية ، وَللإِكسسوارات وغَيرُها. | @tut_biuti

Showing the 4 most recent of 4 posts we hold for @a20s20aa. 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.

Mentions

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

“كُلشي يخُصني.” (@a20s20aa), 10 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/a20s20aa.

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.