
Supergroup
Московский чат
@vpisky_msx
On this record: Growth · Engagement · Cite this entry
5,799members
+610 since we began measuring on 7 August 2026
57 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001957421203 |
|---|---|
| Type | Supergroup |
| Username | @vpisky_msx |
| Description | Московский чат Ночной Тусовки, встречи, вечеринки, общение. |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 10 |
| On Telegram | t.me/vpisky_msx |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 30 Aug 2026, 11:26 | 5,799 | no change |
| 30 Aug 2026, 08:29 | 5,799 | +103 |
| 27 Aug 2026, 04:12 | 5,696 | +73 |
| 24 Aug 2026, 12:45 | 5,623 | +93 |
| 20 Aug 2026, 21:33 | 5,530 | +101 |
| 18 Aug 2026, 00:33 | 5,429 | +56 |
| 15 Aug 2026, 06:07 | 5,373 | +104 |
| 11 Aug 2026, 14:01 | 5,269 | +58 |
| 8 Aug 2026, 16:55 | 5,211 | +22 |
| 7 Aug 2026, 17:37 | 5,189 | 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Московский чат” (@vpisky_msx), 5,799 members as measured 30 August 2026. Telegram Register, tgregister.com/channel/vpisky_msx.
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.