Posted without readable text
👍10🔥2

Channel
@mikrotik_rus
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
3,032subscribers
+37 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001055499138 |
|---|---|
| Type | Channel |
| Username | @mikrotik_rus |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/mikrotik_rus |
Technology — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 17 Sept 2026, 18:17 | 3,032 | +5 |
| 13 Sept 2026, 06:15 | 3,027 | +5 |
| 9 Sept 2026, 15:21 | 3,022 | +7 |
| 4 Sept 2026, 11:00 | 3,015 | +12 |
| 31 Aug 2026, 20:45 | 3,003 | +4 |
| 29 Aug 2026, 00:34 | 2,999 | +2 |
| 26 Aug 2026, 09:17 | 2,997 | +1 |
| 23 Aug 2026, 04:48 | 2,996 | +8 |
| 19 Aug 2026, 13:24 | 2,988 | +1 |
| 16 Aug 2026, 14:13 | 2,987 | -6 |
| 9 Aug 2026, 19:31 | 2,993 | -3 |
| 7 Aug 2026, 00:41 | 2,996 | +1 |
| 6 Aug 2026, 05:02 | 2,995 | no change |
| 5 Aug 2026, 23:28 | 2,995 | first reading |
20 posts held, back to 8 January 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 3 pages 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 3 August 2026. An engagement rate over an empty window would be a number about nothing.
305 reactions across 20 posts, in 16 distinct kinds. The most used accounts for 33.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 101 | 33.1% | |
| 🔥 | 72 | 23.6% | |
| 🤣 | 47 | 15.4% | |
| 😢 | 26 | 8.52% | |
| 😁 | 20 | 6.56% | |
| 🎉 | 9 | 2.95% | |
| ❤ | 8 | 2.62% | |
| 👏 | 7 | 2.30% | |
| 👎 | 4 | 1.31% | |
| ❤🔥 | 2 | 0.656% | |
| 🤔 | 2 | 0.656% | |
| 🤮 | 2 | 0.656% | |
| 🥰 | 2 | 0.656% | |
| 💩 | 1 | 0.328% | |
| 😍 | 1 | 0.328% | |
| 🤯 | 1 | 0.328% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 305 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 January 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mikrotik_rus. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 8 January 2026 to 3 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Posted without readable text
👍10🔥2
Вышли сразу две версии: • RouterOS 7.21.5 [long-term] • RouterOS 7.23.2 [stable] В обеих исправлена CVE-2026-59108. Рекомендуем запланировать обновление. UPD: вендор изменил в ченджлогах формулировку про CVE: !) fixed a service security issue, home user with default config not affected, but we recommend the upgrade for all users regardless; (Если зажмуриться — то её как будто нет) Остальные изменения найдёте в че…
😁2👍1
Стабилизируемся: RouterOS 7.23.1 [stable] What's new in 7.23.1 (2026-Jun-02 12:25): *) app - fixed bogus configuration export; *) app - fixed making empty directories when running configuration export; *) bgp - fixed memory leak; *) bridge - fixed stability issue when using DHCPv4 snooping; *) disk - avoid reading SCSI stats all the time to allow disks to go to sleep; *) disk - improved error message when a swap fil…
👍6🔥2
Привет! Вышла версия 7.23. Те, кому прод не жалко, можете обновиться и потестировать, остальным рекомендую подождать следующих fix-апдейтов ) Ченджлог внушительный Нейроаналитику уберу под спойлер для любителей такого 😜 ✅ Безопасность по умолчанию – обновления теперь тянутся через HTTPS, а не HTTP. Можно отдельно настроить режимы подключения к серверам MikroTik. 📦 App/Container – прорыв! Добавлено 18 новых приложений…
👍11🔥1
Пятничный-предпраздничный релиз. Маленький ченджлог — это не стыдно, просто вода была холодная. RouterOS 7.22.3 [stable] What's new in 7.22.3 (2026-May-07 12:19): *) console - fixed unresponsiveness when entering safe-mode through the Windows 11 terminal; *) ethernet - fixed stability issue after switch reset on devices with IPQ-40xx, IPQ-60xx CPUs (introduced in v7.22); *) vrrp - fixed stability issue when using VR…
😁12❤2🔥1
Кучно пошло: RouterOS 7.22.2 [stable] What's new in 7.22.2 (2026-Apr-22 11:03): *) app - fixed uptime-kuma and jupyter-notebook; *) bgp - fixed stability issue when non-existent output select-chain was specified; *) bridge - fixed missing dynamic "switch-cpu" VLAN entry in WiFi setup; *) bridge - synchronize only local bridge MAC addresses for MLAG (introduced in v7.22); *) console - rename "cpu-used-per-cpu" to "cp…
👍10🔥1
Вчера обновился лонг-терм, причём, на следующую версию. Встречаем: RouterOS 7.21.4 [long-term] What's new in 7.21.4 (2026-Apr-21 09:49): *) bgp - fixed stability issue when non-existent output select-chain was specified; *) bgp-vpn - allow modifying scopes with routing filters; *) bgp-vpn - fixed non-working import filter after reboot; *) bgp-vpn - use target scope for imported route; *) bridge - fixed missing dynam…
👍13🔥1
Вчера вышла RouterOS 7.22.1 [stable] На удивление не так много фиксов: What's new in 7.22.1 (2026-Mar-23 16:35): *) bgp-vpn - fixed non-working import filter after reboot; *) certificate - added option to configure built-in trust store for all services (CLI only); *) certificate - use "default" for built-in trust store default value; *) chr - improved virtio_net stability; *) console - removed the "reset" command fr…
👍6🔥1
https://mikrotik.com/download/winbox Winbox3 🔤🔤🔤 🫡
😢26🎉9🔥4❤🔥2💩1🤮1
RouterOS 7.22 — главное за релиз (нейросетевой анализ — прим. кожаного) 🚀 Новые возможности MLAG теперь в bridge (конфигурация перенесена автоматически, но откат потеряет настройки). BGP: unnumbered, add-path, multipath (ECMP). Reverse-proxy в меню IP. ACME: поддержка нескольких сертификатов (сервисы с истёкшим сертификатом потребуют перенастройки). Приложения: пользовательские apps, jupyter-notebook, livebook,…
❤4👍4
Тем временем Winbox 4 вышел из беты: What's new in 4.0.1 (2026-Feb-13 09:36): *) table: fixed a visual issue in tables with tree structure where last element is collapsed; What's new in WinBox 4: *) WinBox is now cross-platform and available on Windows, Linux, and macOS; *) completely redesigned the login panel, tables, forms, buttons, and overall UI layout; *) added custom font selection and font weight/spacing c…
👍17🤣10👎4🔥2🤯1
RouterOS 7.21.3 [stable] What's new in 7.21.3 (2026-Feb-12 15:10): *) bridge - fixed dhcp-snooping incorrectly disabling HW offloading on QCA8337, Atheros8327 switch chips (introduced in v7.20); *) certificate - fixed initial certificate creation using SCEP (introduced in v7.21); *) console - improved service stability when processing files over CLI; *) dhcpv4-server - append "s" after lease-time value in setup comm…
👍3🔥2🥰1
Showing the 12 most recent of 20 posts we hold for @mikrotik_rus. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Mikrotik по-русски” (@mikrotik_rus), 3,032 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/mikrotik_rus.
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.