Supergroup
Вписки Казань
@vpiski_kzn
On this record: Growth · Engagement · Cite this entry
6,657members
+667 since we began measuring on 7 August 2026
8 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001170593635 |
|---|---|
| Type | Supergroup |
| Username | @vpiski_kzn |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/vpiski_kzn |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 6 Sept 2026, 07:57 | 6,657 | +129 |
| 1 Sept 2026, 16:05 | 6,528 | +29 |
| 30 Aug 2026, 02:39 | 6,499 | +41 |
| 28 Aug 2026, 19:27 | 6,458 | no change |
| 26 Aug 2026, 23:13 | 6,458 | +101 |
| 24 Aug 2026, 03:42 | 6,357 | +73 |
| 20 Aug 2026, 02:48 | 6,284 | +68 |
| 16 Aug 2026, 21:39 | 6,216 | +61 |
| 13 Aug 2026, 11:49 | 6,155 | +101 |
| 10 Aug 2026, 22:08 | 6,054 | +64 |
| 7 Aug 2026, 18:23 | 5,990 | 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Вписки Казань” (@vpiski_kzn), 6,657 members as measured 6 September 2026. Telegram Register, tgregister.com/channel/vpiski_kzn.
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.