Supergroup
PROXYHUB SHOP
@PR0XYHUB_SH0P
On this record: Growth · Engagement · Cite this entry
5,840members
-115 since we began measuring on 7 August 2026
1,130 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002518469076 |
|---|---|
| Type | Supergroup |
| Username | @PR0XYHUB_SH0P |
| Description | Mobile and residential proxies, all information in the @pr0xyhub_team channel |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 10 |
| On Telegram | t.me/PR0XYHUB_SH0P |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 29 Aug 2026, 22:37 | 5,840 | no change |
| 29 Aug 2026, 15:28 | 5,840 | -11 |
| 26 Aug 2026, 23:27 | 5,851 | -14 |
| 24 Aug 2026, 09:15 | 5,865 | -19 |
| 20 Aug 2026, 15:24 | 5,884 | -11 |
| 17 Aug 2026, 10:27 | 5,895 | -21 |
| 14 Aug 2026, 04:06 | 5,916 | -14 |
| 11 Aug 2026, 05:22 | 5,930 | -24 |
| 7 Aug 2026, 23:46 | 5,954 | -1 |
| 7 Aug 2026, 16:02 | 5,955 | 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“PROXYHUB SHOP” (@PR0XYHUB_SH0P), 5,840 members as measured 29 August 2026. Telegram Register, tgregister.com/channel/PR0XYHUB_SH0P.
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.