Supergroup
公群593 全网独家白料手机口 谢哥集团 押金1294u
@jbpipip1013
On this record: Growth · Engagement · Cite this entry
5,836members
-157 since we began measuring on 10 August 2026
2 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002132558753 |
|---|---|
| Type | Supergroup |
| Username | @jbpipip1013 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/jbpipip1013 |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 31 Aug 2026, 19:18 | 5,836 | -67 |
| 29 Aug 2026, 22:02 | 5,903 | no change |
| 28 Aug 2026, 16:34 | 5,903 | -38 |
| 25 Aug 2026, 17:23 | 5,941 | -8 |
| 23 Aug 2026, 00:48 | 5,949 | -32 |
| 19 Aug 2026, 15:05 | 5,981 | +5 |
| 16 Aug 2026, 19:37 | 5,976 | -9 |
| 13 Aug 2026, 14:36 | 5,985 | +12 |
| 10 Aug 2026, 20:01 | 5,973 | -20 |
| 10 Aug 2026, 05:45 | 5,993 | 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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“公群593 全网独家白料手机口 谢哥集团 押金1294u” (@jbpipip1013), 5,836 members as measured 31 August 2026. Telegram Register, tgregister.com/channel/jbpipip1013.
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.