Channel
@miningmoscowshop
On this record: Topic · Growth · Engagement · Posts · Cite this entry
889subscribers
-43 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001826662011 |
|---|---|
| Type | Channel |
| Username | @miningmoscowshop |
| Created | 1 March 2023 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/miningmoscowshop |
Ecommerce storefront — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 68% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 22:19 | 889 | +3 |
| 29 Sept 2026, 08:59 | 886 | -6 |
| 16 Sept 2026, 06:57 | 892 | -6 |
| 8 Sept 2026, 07:56 | 898 | -6 |
| 29 Aug 2026, 21:33 | 904 | -10 |
| 23 Aug 2026, 06:37 | 914 | -14 |
| 16 Aug 2026, 17:04 | 928 | -3 |
| 8 Aug 2026, 09:04 | 931 | -1 |
| 7 Aug 2026, 09:33 | 932 | no change |
| 7 Aug 2026, 09:24 | 932 | first reading |
4 posts held, back to 1 March 2023 — 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 4 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
#наличие #бу Тестолит S19kpro 120th 115usdt Есть 7шт✅ T21 190th без ремонтов🔥 От 1шт - 545$ От 5шт - 540$ От 10шт - 520$ От 30шт - 510$ От 100шт - 495$ Бу в отличном состоянии, домашние✅ Z15pro 860k 6900usdt Всего 9шт Из них 2шт почти новые в работе месяц 7000usdt. Z15j 320k выдаёт 350k 2300usdt 1шт S21pro 220т - 1250$ eeprom до 245Т S21pro 234т - 1340$ S21pro 245т - 1430$ Есть количество лотом M50s в отличном …
#продам Т21 190th 500usdt От 10шт‼️ ❤@Artem_Kesyan 💬89181074209
Mining Moscow майнинговое оборудование в Москве, оптом и в розницу.: #Иркутск От 50шт М50S 128t 185u М50S 130t 195u М50S 132t 205u М50S 134t 220u М50S+ 128t 250u М50S +130t 260u М50S +132t 270u М50S +134t 280u М50S +136t 290u М50S +138t 300u М50S +140t 310u М50S +142t 320u М50S +144t 330u М50S +146-148t 350u ❤@Artem_Kesyan 💬89181074209
Channel created
Showing the 4 most recent of 4 posts we hold for @miningmoscowshop. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“Mining Moscow майнинговое оборудование в Москве, оптом и в розницу.” (@miningmoscowshop), 889 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/miningmoscowshop.
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.