Channel
حروف سكواد
@Squad_huruf
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,300subscribers
-283 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001902252910 |
|---|---|
| Type | Channel |
| Username | @Squad_huruf |
| Created | Between 1 March 2023 and 31 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/Squad_huruf |
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 16 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, 19:10 | 2,300 | -5 |
| 1 Nov 2026, 22:28 | 2,305 | +5 |
| 29 Oct 2026, 23:46 | 2,300 | -1 |
| 27 Oct 2026, 05:37 | 2,301 | +1 |
| 24 Oct 2026, 08:06 | 2,300 | -18 |
| 21 Oct 2026, 01:08 | 2,318 | +2 |
| 18 Oct 2026, 08:46 | 2,316 | -13 |
| 15 Oct 2026, 05:11 | 2,329 | -11 |
| 12 Oct 2026, 02:42 | 2,340 | -27 |
| 5 Oct 2026, 06:58 | 2,367 | -34 |
| 26 Sept 2026, 12:42 | 2,401 | -36 |
| 17 Sept 2026, 16:57 | 2,437 | -19 |
| 16 Sept 2026, 00:55 | 2,456 | no change |
| 14 Sept 2026, 00:57 | 2,456 | -50 |
| 10 Sept 2026, 07:38 | 2,506 | -19 |
| 5 Sept 2026, 12:20 | 2,525 | -13 |
| 1 Sept 2026, 20:54 | 2,538 | -13 |
| 29 Aug 2026, 15:12 | 2,551 | -6 |
| 26 Aug 2026, 09:12 | 2,557 | -6 |
| 23 Aug 2026, 12:47 | 2,563 | 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.
@njafeoo_n · 263,957
Telegram ranks this channel #19 of 79 here — alongside 78 others — read 10 August 2026
@njafeoon · 398,161
Telegram ranks this channel #23 of 73 here — alongside 72 others — read 10 August 2026
@alnajafci · 26,291
Telegram ranks this channel #42 of 72 here — alongside 71 others — read 12 September 2026
@NajafeoonH · 82,364
Telegram ranks this channel #56 of 90 here — alongside 89 others — read 18 August 2026
@cities_najaf · 174,828
Telegram ranks this channel #63 of 89 here — alongside 88 others — read 12 August 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.
“حروف سكواد” (@Squad_huruf), 2,300 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/Squad_huruf.
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.