Block found on SOLO # 3168070 Network Difficulty: 294.5 G Mined by: 89KqRSwi…FLH78WHg Pool Hashrate: 51.4 MH/s Miners total: 75

Channel
Solo XMR
@SoloXmr2Miners
On this record: Growth · Engagement · Posts · Cite this entry
55subscribers
-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 | -1001266684915 |
|---|---|
| Type | Channel |
| Username | @SoloXmr2Miners |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/SoloXmr2Miners |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 08:38 | 55 | -1 |
| 24 Aug 2026, 17:06 | 56 | -1 |
| 10 Aug 2026, 07:16 | 57 | no change |
| 7 Aug 2026, 23:36 | 57 | first reading |
Engagement
20 posts held, back to 2 June 2024 — 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 10 June 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Block found on SOLO # 3167632 Network Difficulty: 273.98 G Mined by: 882sWsAX…cH4fFUga Pool Hashrate: 75.65 MH/s Miners total: 77
Block found on SOLO # 3166735 Network Difficulty: 281.3 G Mined by: 882sWsAX…cH4fFUga Pool Hashrate: 22.38 MH/s Miners total: 82
Block found on SOLO # 3166391 Network Difficulty: 270.61 G Mined by: 882sWsAX…cH4fFUga Pool Hashrate: 68.07 MH/s Miners total: 82
Block found on SOLO # 3166123 Network Difficulty: 244.5 G Mined by: 48dWrJvZ…JEtCWQrY Pool Hashrate: 1.26 MH/s Miners total: 88
Block found on SOLO # 3165564 Network Difficulty: 242.64 G Mined by: 882sWsAX…cH4fFUga Pool Hashrate: 51.55 MH/s Miners total: 85
Block found on SOLO # 3165281 Network Difficulty: 236.61 G Mined by: 89KqRSwi…FLH78WHg Pool Hashrate: 47.91 MH/s Miners total: 83
Block found on SOLO # 3164223 Network Difficulty: 260.45 G Mined by: 882sWsAX…cH4fFUga Pool Hashrate: 93.53 MH/s Miners total: 92
Block found on SOLO # 3163823 Network Difficulty: 239.17 G Mined by: 866uwJ2u…kV1xgtUr Pool Hashrate: 34.18 MH/s Miners total: 95
Block found on SOLO # 3163791 Network Difficulty: 236.17 G Mined by: 866uwJ2u…kV1xgtUr Pool Hashrate: 20.89 MH/s Miners total: 95
Block found on SOLO # 3163537 Network Difficulty: 226.32 G Mined by: 866uwJ2u…kV1xgtUr Pool Hashrate: 39.05 MH/s Miners total: 93
Block found on SOLO # 3163341 Network Difficulty: 227.62 G Mined by: 866uwJ2u…kV1xgtUr Pool Hashrate: 23.81 MH/s Miners total: 101
Showing the 12 most recent of 20 posts we hold for @SoloXmr2Miners. 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Solo XMR” (@SoloXmr2Miners), 55 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/SoloXmr2Miners.
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.