Зун 50₽ Текст на проверку @SABOTKLOP
Signed Свай

Channel
@MIRROX_channel
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
792subscribers
-25 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001553260622 |
|---|---|
| Type | Channel |
| Username | @MIRROX_channel |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/MIRROX_channel |
Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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 |
|---|---|---|
| 16 Sept 2026, 06:19 | 792 | -6 |
| 7 Sept 2026, 19:56 | 798 | -6 |
| 29 Aug 2026, 18:04 | 804 | -7 |
| 23 Aug 2026, 05:14 | 811 | -2 |
| 16 Aug 2026, 15:46 | 813 | -4 |
| 8 Aug 2026, 01:32 | 817 | no change |
| 7 Aug 2026, 11:35 | 817 | first reading |
20 posts held, back to 18 March 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 17 May 2026. An engagement rate over an empty window would be a number about nothing.
Зун 50₽ Текст на проверку @SABOTKLOP
Signed Свай
🖥Платформа - 2gis 💰Оплата - 25 📃Описание - Все быстро, расскажу 👤Выдаст задание - @EgW0rk
Signed Егор | Гис оплачу во Вторник
Авито 500₽ Надо аккаунты 2023 года кто не писал отзыв минимум 1 месяц @SABOTKLOP
Signed Свай
🖥Платформа - 2gis 💰Оплата - 25 📃Описание - Все быстро, расскажу 👤Выдаст задание - @EgW0rk
Signed Егор | Гис оплачу во Вторник
Яндекс Карта,Авито 150₽,300₽ Ищу менеджера по як С оплатой договоримся 5 ссылок есть Авито надо 2023 год аккаунт. @SABOTKLOP
Signed Свай/глушат инет
В наличии (с готовым текстом, есть новые ссылки): 🪆2гис по 10₽ 🪆 Zoon по 30₽ 🪆 Яндекс карты по 110₽ Писать @matryoshkawork
Signed MATRYOSHKA
Яндекс карта авито 150₽,300₽ Яндекс карта у кого 2 уровень @SABOTKLOP
Signed Свай
🖥Платформа - 2gis/яндекс карты 💰Оплата - 40/150 📃Описание - Все быстро, расскажу 👤Выдаст задание - @EgW0rk
Signed Егор
Янлекс карта,Авито 150₽,300₽ Пишите у кого проходит отзывы Писать: @SABOTKLOP
Signed Свай/инет глушат
💻 Платформа - Платформа: Яндекс карты /Яндекс браузер /Гугл карты 💸 Получите оплату - 150₽ /100₽ /100₽, после публикации отзыва 👤 Нужно людей - много 📃 Описание - Пришли скрин последних отзывов и Имя аккаунта с выбранной площадки, инструкцию дам 👥 Выдаст задание - @igorotzv
Signed Игорь
───── ⋆⋅☆⋅⋆ ───── ✧ Новое задание ✧ ፠Платформа: Яндекс карта ፠Цена: 150₽ ፠Описание: ,любые аккаунты ፠Задания взять у: @SABOTKLOP ───── ⋆⋅☆⋅⋆ ─────
Signed Свай
💻 Платформа - Платформа: Яндекс карты /Яндекс браузер /Гугл карты 💸 Получите оплату - 150₽ /100₽ /100₽, после публикации отзыва 👤 Нужно людей - много 📃 Описание - Пришли скрин последних отзывов и Имя аккаунта с выбранной площадки, инструкцию дам 👥 Выдаст задание - @igorotzv
Signed Игорь
Showing the 12 most recent of 20 posts we hold for @MIRROX_channel. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
@MIRROX_channel named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“𝕄𝕀ℝℝ𝕆𝕏 | 𝕔𝕙𝕒𝕟𝕟𝕖𝕝” (@MIRROX_channel), 792 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/MIRROX_channel.
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.