
Channel
ayubghaleh-ایوب قلعه
@ayubghaleh
On this record: Growth · Engagement · Cite this entry
6,798subscribers
-47 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001009017370 |
|---|---|
| Type | Channel |
| Username | @ayubghaleh |
| Created | Between 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/ayubghaleh |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 01:08 | 6,798 | -1 |
| 27 Aug 2026, 21:15 | 6,799 | no change |
| 26 Aug 2026, 03:32 | 6,799 | -5 |
| 23 Aug 2026, 04:48 | 6,804 | -7 |
| 19 Aug 2026, 11:13 | 6,811 | -9 |
| 16 Aug 2026, 06:56 | 6,820 | -12 |
| 12 Aug 2026, 17:53 | 6,832 | -12 |
| 9 Aug 2026, 23:45 | 6,844 | -1 |
| 6 Aug 2026, 16:33 | 6,845 | 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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“ayubghaleh-ایوب قلعه” (@ayubghaleh), 6,798 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/ayubghaleh.
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.