Supergroup
海外支付资源交流群！@viptt
@viptt
On this record: Growth · Engagement · Cite this entry
6,436members
+388 since we began measuring on 7 August 2026
342 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002183203688 |
|---|---|
| Type | Supergroup |
| Usernames | @kalichuhai @viptt |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/viptt |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 30 Aug 2026, 10:24 | 6,436 | +20 |
| 29 Aug 2026, 11:55 | 6,416 | +55 |
| 28 Aug 2026, 21:28 | 6,361 | no change |
| 27 Aug 2026, 02:12 | 6,361 | +54 |
| 24 Aug 2026, 04:04 | 6,307 | +63 |
| 20 Aug 2026, 09:44 | 6,244 | +47 |
| 17 Aug 2026, 10:53 | 6,197 | +53 |
| 14 Aug 2026, 07:34 | 6,144 | +58 |
| 11 Aug 2026, 05:31 | 6,086 | +20 |
| 7 Aug 2026, 21:38 | 6,066 | +18 |
| 7 Aug 2026, 14:45 | 6,048 | 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.
“海外支付资源交流群！@viptt” (@viptt), 6,436 members as measured 30 August 2026. Telegram Register, tgregister.com/channel/viptt.
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.