Channel
ࢪوَٖٖٓ͜آٰٖٖيـــ҈ـــآٰٖٖټي🔓💔
@roayaty19
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,002subscribers
+156 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002125752281 |
|---|---|
| Type | Channel |
| Username | @roayaty19 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/roayaty19 |
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 15 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 05:41 | 3,002 | -1 |
| 12 Sept 2026, 22:39 | 3,003 | +26 |
| 11 Sept 2026, 21:27 | 2,977 | no change |
| 8 Sept 2026, 19:35 | 2,977 | +21 |
| 3 Sept 2026, 11:38 | 2,956 | +1 |
| 31 Aug 2026, 03:59 | 2,955 | +12 |
| 28 Aug 2026, 03:25 | 2,943 | +29 |
| 25 Aug 2026, 03:34 | 2,914 | +41 |
| 21 Aug 2026, 13:44 | 2,873 | +16 |
| 18 Aug 2026, 21:08 | 2,857 | +5 |
| 16 Aug 2026, 03:29 | 2,852 | +6 |
| 15 Aug 2026, 08:21 | 2,846 | 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.
@bookdescription1 · 48,649
Telegram ranks this channel #2 of 66 here — alongside 65 others — read 27 August 2026
@lenaqra3 · 26,429
Telegram ranks this channel #8 of 74 here — alongside 73 others — read 12 September 2026
@roayati · 90,707
Telegram ranks this channel #9 of 81 here — alongside 80 others — read 17 August 2026
@L_alnader14 · 39,300
Telegram ranks this channel #11 of 85 here — alongside 84 others — read 31 August 2026
@basatinalkutib · 26,208
Telegram ranks this channel #21 of 72 here — alongside 71 others — read 13 September 2026
@books_nour · 104,014
Telegram ranks this channel #35 of 73 here — alongside 72 others — read 15 August 2026
This channel appears in 6 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“ࢪوَٖٖٓ͜آٰٖٖيـــ҈ـــآٰٖٖټي🔓💔” (@roayaty19), 3,002 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/roayaty19.
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.