Channel
Azərbaycan Dili (Suallar və Cavablar)
@AzerbaycanDiliA
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,270subscribers
-285 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001998022545 |
|---|---|
| Type | Channel |
| Username | @AzerbaycanDiliA |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 21 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 21 October 2026 |
| On Telegram | t.me/AzerbaycanDiliA |
Topic
Education — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 21 Oct 2026, 14:58 | 6,270 | +1 |
| 18 Oct 2026, 09:46 | 6,269 | -22 |
| 15 Oct 2026, 09:56 | 6,291 | -12 |
| 12 Oct 2026, 04:21 | 6,303 | -32 |
| 5 Oct 2026, 11:01 | 6,335 | -32 |
| 27 Sept 2026, 02:21 | 6,367 | -79 |
| 17 Sept 2026, 15:00 | 6,446 | -26 |
| 13 Sept 2026, 21:57 | 6,472 | -30 |
| 10 Sept 2026, 09:59 | 6,502 | -19 |
| 5 Sept 2026, 13:37 | 6,521 | -35 |
| 1 Sept 2026, 04:36 | 6,556 | +1 |
| 31 Aug 2026, 21:21 | 6,555 | no change |
| 31 Aug 2026, 21:15 | 6,555 | 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.
@azerbaycandiligunelmemmedova · 29,904
Telegram ranks this channel #4 of 66 here — alongside 65 others — read 8 September 2026
@nergizhesenova · 18,905
Telegram ranks this channel #17 of 59 here — alongside 58 others — read 4 October 2026
@Mehtiyevatest · 31,360
Telegram ranks this channel #21 of 70 here — alongside 69 others — read 6 September 2026
@oxu_hazirliq_kurslari · 19,733
Telegram ranks this channel #32 of 65 here — alongside 64 others — read 30 September 2026
@Riyaziyyatindunyasi · 38,020
Telegram ranks this channel #49 of 55 here — alongside 54 others — read 31 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 21 October 2026 — this entry's latest reading, not the date you are reading this.
“Azərbaycan Dili (Suallar və Cavablar)” (@AzerbaycanDiliA), 6,270 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/AzerbaycanDiliA.
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.