Telegram RegisterThe public register of Telegram
Telegram profile photo for Kasr Alainy Data (197)

Channel

Kasr Alainy Data (197)

@elkasrdata

On this record: Growth · Engagement · Telegram's recommendations · Cite this entry

13,268subscribers

+29 since we began measuring on 26 August 2026

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

Register entry

Telegram ID-1001900701041
TypeChannel
Username@elkasrdata
CreatedBetween 1 March 2023 and 30 November 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live5 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/elkasrdata

Growth

13,23913,26813,253.526 August 2026 — 13,239 subscribers26 August 2026 — 13,239 subscribers26 August 2026 — 13,240 subscribers27 August 2026 — 13,250 subscribers29 August 2026 — 13,252 subscribers30 August 2026 — 13,250 subscribers1 September 2026 — 13,242 subscribers2 September 2026 — 13,250 subscribers3 September 2026 — 13,256 subscribers5 September 2026 — 13,268 subscribers26 August 20265 September 2026
10 measurements spanning 10 days, net +29. 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 13,235–13,272 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 05:0113,268+12
3 Sept 2026, 09:5213,256+6
2 Sept 2026, 04:0213,250+8
1 Sept 2026, 00:3813,242-8
30 Aug 2026, 22:4713,250-2
29 Aug 2026, 23:2513,252+2
27 Aug 2026, 19:2413,250+10
26 Aug 2026, 18:5313,240+1
26 Aug 2026, 10:4413,239no change
26 Aug 2026, 02:4513,239first reading

Engagement

No public post preview. We read this entry on 26 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.

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.

FUTURE DOCTORS 196🩺
@FUTUREDOCTORS_196 · 35,159
Telegram ranks this channel #2 of 77 here — alongside 76 others — read 2 September 2026
FUTURE DOCTORS CHANNEL🩺
@FUTUREDOCTORS_194 · 41,447
Telegram ranks this channel #7 of 89 here — alongside 88 others — read 29 August 2026
Easy Medicine (Osama Ramadan)
@Medical_Data_Channel · 49,130
Telegram ranks this channel #21 of 82 here — alongside 81 others — read 26 August 2026
Dr.YoussefMohsen
@dryoussefmohsen · 32,395
Telegram ranks this channel #36 of 86 here — alongside 85 others — read 5 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“Kasr Alainy Data (197)” (@elkasrdata), 13,268 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/elkasrdata.

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.