Supergroup
URBEX подслушка
@urbex_chatik
On this record: Growth · Engagement · Cite this entry
534members
+14 since we began measuring on 7 August 2026
4 online right now
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001935509115 |
|---|---|
| Type | Supergroup |
| Username | @urbex_chatik |
| Description | Чат канала @urbex_kzn |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 October 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 10 |
| On Telegram | t.me/urbex_chatik |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 11 Oct 2026, 19:53 | 534 | no change |
| 9 Oct 2026, 03:15 | 534 | -6 |
| 29 Sept 2026, 02:42 | 540 | -3 |
| 12 Sept 2026, 09:14 | 543 | +6 |
| 3 Sept 2026, 07:47 | 537 | -1 |
| 27 Aug 2026, 22:25 | 538 | +3 |
| 21 Aug 2026, 12:29 | 535 | +7 |
| 14 Aug 2026, 07:48 | 528 | +7 |
| 7 Aug 2026, 20:52 | 521 | +1 |
| 7 Aug 2026, 14:41 | 520 | 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“URBEX подслушка” (@urbex_chatik), 534 members as measured 11 October 2026. Telegram Register, tgregister.com/channel/urbex_chatik.
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.