Channel
Gilan Ava - گیلان آوا
@gilan_ava
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,825subscribers
+46 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001128681324 |
|---|---|
| Type | Channel |
| Username | @gilan_ava |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 23 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/gilan_ava |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 |
|---|---|---|
| 23 Sept 2026, 01:41 | 1,825 | no change |
| 16 Sept 2026, 09:01 | 1,825 | +11 |
| 12 Sept 2026, 04:40 | 1,814 | +4 |
| 8 Sept 2026, 08:20 | 1,810 | +6 |
| 2 Sept 2026, 22:06 | 1,804 | +3 |
| 31 Aug 2026, 04:37 | 1,801 | +2 |
| 25 Aug 2026, 04:23 | 1,799 | +2 |
| 22 Aug 2026, 08:27 | 1,797 | +6 |
| 18 Aug 2026, 19:56 | 1,791 | -1 |
| 15 Aug 2026, 20:23 | 1,792 | +3 |
| 12 Aug 2026, 16:44 | 1,789 | +7 |
| 9 Aug 2026, 16:02 | 1,782 | +4 |
| 6 Aug 2026, 19:47 | 1,778 | -1 |
| 6 Aug 2026, 02:00 | 1,779 | 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.
@kordberoz · 21,896
Telegram ranks this channel #6 of 81 here — alongside 80 others — read 22 September 2026
@dj_myou · 45,269
Telegram ranks this channel #6 of 61 here — alongside 60 others — read 9 September 2026
@Rahmatazary · 31,029
Telegram ranks this channel #22 of 77 here — alongside 76 others — read 7 September 2026
@farhadjahangiriorg · 60,839
Telegram ranks this channel #35 of 95 here — alongside 94 others — read 23 August 2026
@delsouzkhaledii · 28,403
Telegram ranks this channel #48 of 65 here — alongside 64 others — read 9 September 2026
@ravizh14 · 54,224
Telegram ranks this channel #73 of 75 here — alongside 74 others — read 24 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 23 September 2026 — this entry's latest reading, not the date you are reading this.
“Gilan Ava - گیلان آوا” (@gilan_ava), 1,825 subscribers as measured 23 September 2026. Telegram Register, tgregister.com/channel/gilan_ava.
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.