Block found on SOLO # 1847259 Network Difficulty: 58.98 T Mined by: 9hWuq4Ph…xvjLG7PL Pool Hashrate: 5.51 GH/s Miners total: 6

Channel
Solo ERG
@SoloErg2Miners
On this record: Growth · Engagement · Posts · Cite this entry
70subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001508520336 |
|---|---|
| Type | Channel |
| Username | @SoloErg2Miners |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 7 September 2026 |
| On Telegram | t.me/SoloErg2Miners |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 11:15 | 70 | -1 |
| 16 Aug 2026, 03:58 | 71 | -1 |
| 9 Aug 2026, 23:01 | 72 | no change |
| 7 Aug 2026, 23:36 | 72 | first reading |
Engagement
20 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Block found on SOLO # 1846975 Network Difficulty: 66.3 T Mined by: 9hVR2SG6…JV4ip1Tx Pool Hashrate: 4.33 GH/s Miners total: 5
Block found on SOLO # 1846930 Network Difficulty: 66.3 T Mined by: 9g2qZCoK…9EbVPKpp Pool Hashrate: 4.16 GH/s Miners total: 5
Block found on SOLO # 1846699 Network Difficulty: 64.03 T Mined by: 9ghQ2XCG…g6j3SDKv Pool Hashrate: 5.6 GH/s Miners total: 6
Block found on SOLO # 1846590 Network Difficulty: 64.99 T Mined by: 9g2qZCoK…9EbVPKpp Pool Hashrate: 5.76 GH/s Miners total: 7
Block found on SOLO # 1846503 Network Difficulty: 60.06 T Mined by: 9g2qZCoK…9EbVPKpp Pool Hashrate: 4.7 GH/s Miners total: 7
Block found on SOLO # 1846486 Network Difficulty: 60.06 T Mined by: 9hVR2SG6…JV4ip1Tx Pool Hashrate: 3.77 GH/s Miners total: 6
Block found on SOLO # 1846389 Network Difficulty: 59.83 T Mined by: 9hVR2SG6…JV4ip1Tx Pool Hashrate: 4.23 GH/s Miners total: 7
Block found on SOLO # 1846068 Network Difficulty: 66.13 T Mined by: 9hxHrGvC…5S42Jwhy Pool Hashrate: 3.98 GH/s Miners total: 7
Block found on SOLO # 1846026 Network Difficulty: 66.13 T Mined by: 9gUXZXvN…X21t5yYV Pool Hashrate: 4.28 GH/s Miners total: 7
Block found on SOLO # 1845743 Network Difficulty: 58.2 T Mined by: 9hYcqywE…Z4QnzNmB Pool Hashrate: 4.53 GH/s Miners total: 8
Block found on SOLO # 1845706 Network Difficulty: 58.2 T Mined by: 9hVR2SG6…JV4ip1Tx Pool Hashrate: 4.52 GH/s Miners total: 9
Showing the 12 most recent of 20 posts we hold for @SoloErg2Miners. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Solo ERG” (@SoloErg2Miners), 70 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/SoloErg2Miners.
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.