Telegram RegisterThe public register of Telegram

Channel

MTik.pro новости

@mtikpro

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,182subscribers

+5 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001094779711
TypeChannel
Username@mtikpro
Created20 January 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/mtikpro

Growth

1,1771,1821,179.56 August 2026 — 1,177 subscribers6 August 2026 — 1,177 subscribers6 August 2026 — 1,178 subscribers9 August 2026 — 1,179 subscribers12 August 2026 — 1,182 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net +5. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,176–1,183 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:551,182+3
9 Aug 2026, 20:531,179+1
6 Aug 2026, 20:561,178+1
6 Aug 2026, 08:501,177no change
6 Aug 2026, 01:091,177first reading

Engagement

20 posts held, back to 13 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
46.4%
avg views ÷ 1,182 subscribers
Avg views / post
548
3 posts measured
Reaction rate
1.41%
reactions ÷ views · ER floor
Posts in window
3
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 3 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (13 January 20265 August 2026)
Views total1,645
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 08:50 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

5 Aug 2026, 14:34 UTC≈283 views4 reactionsread 6 August 2026
Forwarded from @sysodmins

🚨 Один пакет до рута. В OpenWrt нашли критическую дыру в DHCPv6-сервере (CVSS 9.8) В любимой прошивке раскопали шикарную RCE. Вся магия происходит в демоне odhcpd, который отвечает за выдачу IPv6-адресов. И да, по дефолту этот демон крутится с правами root 😬 Разрабы допустили классическое переполнение фиксированного 512-байтового стекового буфера (pdbuf). Чтобы взломать роутер, атакующему не нужна авторизация. Дост

16 Jul 2026, 10:33 UTC≈723 viewsread 6 August 2026

Кто в теме про ИИ, почему ИИ-шки не умеют в обычные арифметические операции?

16 Jul 2026, 09:42 UTC≈639 viewsread 6 August 2026

открыл для себя новую запись ASN. RFC5396 : Формат ASdot или ASdot+ (они немного разные). asplain - простая десятичная запись ASN в виде одного числа. asdot — формат, разбивающий 32‑битный ASN на две 16‑битные части: «старшую» и «младшую», разделённые точкой. То есть каждые 16 бит интерпретируем как отдельное число. Оказалось, что пользоваться 32-битными ASN бывает комфортнее в ASdot. 😎 Вот пример для таблицы с ди

10 Jul 2026, 10:04 UTC≈917 views8 reactionsread 6 August 2026

Вышли новые версии MikroTik #RouterOS RouterOS 7 Stable: 7.23.2 RouterOS 7 Long-term: 7.21.5 RouterOS 6 Long-term: 6.49.20 У всех в changelog'е: !) fixed a service security issue, home user with default config not affected, but we recommend the upgrade for all users regardless; то есть исправили что-то связанное с безопасностью. Домашних пользователей не должно заафектить, но рекомендуют обновиться. Следуем реком

29 May 2026, 12:54 UTC≈1,240 views10 reactionsread 6 August 2026
Photo

Про IPv8 посмеялись и ладно... За последнее время произошло важное событие. По данным публичной статистики Google процент пользователей, которым сервисы google доступны по #IPv6 достиг уровня 50%. Интернет уже работает поверх IPv6, оборудование уже поддерживает этот протокол. От внешних сил требовать нечего, ждать нечего... Пора использовать IPv6! О том какие есть отличия IPv6 от текущего IPv4, как запустить I

13 May 2026, 12:39 UTC≈1,230 views16 reactionsread 6 August 2026
Photo

Могу сознаться, что я тоже симулировал (основную) 💼 работу во время конференции GetNet /25

13 May 2026, 09:37 UTC≈1,190 views9 reactionsread 6 August 2026
Photo

В прошлом году на GetNet /25 была неформальная зона для тех, кто пришёл на конференцию, но не смог полноценно высвободить свой рабочий график. Ну, всегда же так.... 😭

13 May 2026, 06:17 UTC≈1,020 views9 reactionsread 6 August 2026
Photo

Уже скоро - в эту пятницу 15 мая в Москве пройдёт конференция GetNet /26 Ещё есть возможность зарегистрироваться и прийти очно, чтобы послушать доклады вживую и позадавать каверZные (или не очень) вопросы. Если вы не в Москве и не готовы всё бросить и приехать — регистрируйтесь на онлайн трансляцию - будет Интересно!

17 Apr 2026, 09:03 UTC≈1,370 views9 reactionsread 6 August 2026

коллеги предупреждают, что использовать FTP это опасно .. ХА... Приводится в качестве аргумента, что ваши логины и пароли можно посмотреть при использовании открытого WiFI, так как в FTP пароли не шифруются (передаются plain text'ом). Вообще, это всё пол беды. На операторах связи давно стоят DPI операторов и штука, ТСПУ и некая система для мероприятий . Все эти три коробки не только способны детектировать FTP, но

17 Apr 2026, 06:50 UTC≈1,200 views9 reactionsread 6 August 2026

Что-то пошло не так и в этом году 1-апрельский RFC вышел поздно. Везде и со всех сторон пишут про публикацию нового черновика RFC про IPv8, который скорее IPv4+v4 Не первая попытка придумать новый стандарт, который победит какие-то проблемы IPv4. Лично я рассматриваю это исключительно как шутку, которая почему-то опубликована 14 апреля, а не 1 апреля.

9 Apr 2026, 08:22 UTC≈1,410 views0 reactionsread 6 August 2026
Photo

Чуть интерактива... Что изображено на фото и какой цвет вам нравится больше? 😂 Предлагаю писать в комменты что это ПОД СПОЙЛЕРАМИ и кто с чем сталкивался, что у вас в работе.

31 Mar 2026, 06:32 UTC≈1,450 views5 reactionsread 6 August 2026

Сохраняйтесь. Сегодня день, когда нужно подумать о своих резервных копиях. Не только в этот день, но в этот день - как "посидеть на дорожку", вспомнить если про что-то забыли.

Showing the 12 most recent of 20 posts we hold for @mtikpro. 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.

Citation-graph rank

Citation-graph rank — 1,126,333 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“MTik.pro новости” (@mtikpro), 1,182 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/mtikpro.

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.