Channel
KURD BOX 3
@kurdbox3
On this record: Growth · Engagement · Cite this entry
7,307subscribers
+66 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002375488103 |
|---|---|
| Type | Channel |
| Username | @kurdbox3 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/kurdbox3 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 13:58 | 7,307 | +9 |
| 2 Sept 2026, 00:29 | 7,298 | +9 |
| 30 Aug 2026, 10:07 | 7,289 | +8 |
| 27 Aug 2026, 07:12 | 7,281 | +11 |
| 26 Aug 2026, 21:30 | 7,270 | no change |
| 24 Aug 2026, 02:13 | 7,270 | +8 |
| 20 Aug 2026, 18:52 | 7,262 | -6 |
| 17 Aug 2026, 09:45 | 7,268 | +14 |
| 14 Aug 2026, 03:06 | 7,254 | +2 |
| 10 Aug 2026, 22:05 | 7,252 | +9 |
| 7 Aug 2026, 14:47 | 7,243 | +2 |
| 7 Aug 2026, 12:59 | 7,241 | 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“KURD BOX 3” (@kurdbox3), 7,307 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/kurdbox3.
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.