Supergroup
CryptoHover | کریپتوهاور
@Crypto_Hover
On this record: Growth · Engagement · Cite this entry
5,403members
-95 since we began measuring on 13 August 2026
41 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002566419291 |
|---|---|
| Type | Supergroup |
| Username | @Crypto_Hover |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/Crypto_Hover |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 7 Sept 2026, 01:59 | 5,403 | -7 |
| 2 Sept 2026, 05:13 | 5,410 | -8 |
| 31 Aug 2026, 12:03 | 5,418 | no change |
| 30 Aug 2026, 15:07 | 5,418 | -21 |
| 27 Aug 2026, 10:08 | 5,439 | -11 |
| 24 Aug 2026, 14:54 | 5,450 | -9 |
| 20 Aug 2026, 13:12 | 5,459 | -17 |
| 17 Aug 2026, 12:48 | 5,476 | -20 |
| 13 Aug 2026, 18:25 | 5,496 | -2 |
| 13 Aug 2026, 11:03 | 5,498 | 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“CryptoHover | کریپتوهاور” (@Crypto_Hover), 5,403 members as measured 7 September 2026. Telegram Register, tgregister.com/channel/Crypto_Hover.
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.