Channel
ملفات سقيا
@suqya_pdf
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,799subscribers
-131 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002027625051 |
|---|---|
| Type | Channel |
| Username | @suqya_pdf |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 2 times, most recently 7 November 2026 |
| On Telegram | t.me/suqya_pdf |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 04:37 | 4,799 | -4 |
| 31 Oct 2026, 22:10 | 4,803 | -4 |
| 28 Oct 2026, 16:19 | 4,807 | -7 |
| 25 Oct 2026, 12:40 | 4,814 | -5 |
| 22 Oct 2026, 08:21 | 4,819 | -4 |
| 18 Oct 2026, 20:56 | 4,823 | -3 |
| 15 Oct 2026, 19:56 | 4,826 | -4 |
| 12 Oct 2026, 21:09 | 4,830 | -8 |
| 6 Oct 2026, 07:56 | 4,838 | -9 |
| 29 Sept 2026, 11:56 | 4,847 | -25 |
| 14 Sept 2026, 14:01 | 4,872 | -9 |
| 11 Sept 2026, 07:37 | 4,881 | -11 |
| 6 Sept 2026, 02:37 | 4,892 | -9 |
| 2 Sept 2026, 08:56 | 4,901 | -4 |
| 1 Sept 2026, 22:31 | 4,905 | no change |
| 30 Aug 2026, 06:34 | 4,905 | -3 |
| 27 Aug 2026, 01:04 | 4,908 | -3 |
| 24 Aug 2026, 08:42 | 4,911 | -10 |
| 20 Aug 2026, 06:11 | 4,921 | -9 |
| 16 Aug 2026, 20:45 | 4,930 | 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.
@swaadelaalwaai · 90,502
Telegram ranks this channel #14 of 93 here — alongside 92 others — read 16 August 2026
@modarasatswaad · 30,001
Telegram ranks this channel #36 of 84 here — alongside 83 others — read 6 September 2026
@as_maabdo · 19,052
Telegram ranks this channel #51 of 82 here — alongside 81 others — read 3 October 2026
@sheikh_Abdulrahman1 · 36,277
Telegram ranks this channel #58 of 86 here — alongside 85 others — read 5 September 2026
@eg_jobs · 30,054
Telegram ranks this channel #69 of 72 here — alongside 71 others — read 7 September 2026
This channel appears in 5 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“ملفات سقيا” (@suqya_pdf), 4,799 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/suqya_pdf.
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.