Telegram RegisterThe public register of Telegram
Telegram profile photo for ITibekin | Просто о цифровом

Channel

ITibekin | Просто о цифровом

@ITibekin_fm

On this record: Growth · Engagement · Reactions · Stars · Posts · Polls · Citations · Cite this entry

277subscribers

+1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002404467042
TypeChannel
Username@ITibekin_fm
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/ITibekin_fm

Growth

276277276.56 August 2026 — 276 subscribers6 August 2026 — 276 subscribers15 August 2026 — 277 subscribers6 August 202615 August 2026
3 measurements spanning 9 days, net +1. 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 276–277 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 13:28277+1
6 Aug 2026, 23:31276no change
6 Aug 2026, 21:16276first reading

Engagement

20 posts held, back to 12 March 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
220.2%
avg views ÷ 277 subscribers
Avg views / post
610
3 posts measured
Reaction rate
7.32%
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held20 (12 March 20264 August 2026)
Views total1,830
Reactions total134
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 23:31 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.

Reaction mix

609 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 36.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥22236.5%
👍17729.1%
🤝8313.6%
6911.3%
396.40%
👏91.48%
😱30.493%
👌20.328%
😁20.328%
😢10.164%
🤔10.164%
🤯10.164%

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 609reactions 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 12 March 2026 to 4 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.

Telegram Stars

Stars received
30
across the posts below
Posts paid on
18
of 20 we hold a reading for · 90%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ITibekin_fm. 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 12 March 2026 to 4 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.

Recent posts

4 Aug 2026, 12:03 UTC312 views42 reactions1 Starread 6 August 2026

Цифровизация Шанхая: транспортная инфраструктура. Сравнение с Россией В прошлом посте я делился общими впечатлениями от Шанхая - про беспилотное метро, умные светофоры и экосистемы. Сегодня - глубже. Сравниваю транспортную инфраструктуру двух стран. Не в формате: у них лучше, у нас хуже, а как инженер - по фактам, цифрам и подходам. Компаниям, кто занимается развитием данных систем, стоит задуматься, посмотрев на э

👍17🔥17🤝8

28 Jul 2026, 12:05 UTC794 views42 reactions1 Starread 6 August 2026
Photo

Цифровизация Шанхая глазами ИТ-инженера из Сибири В начале июля я улетел в Шанхай. Не в командировку, а в отпуск. Но, как любой технический руководитель, я всё равно обратил внимание на то, как устроены городские цифровые сервисы и ИТ-инфраструктура. До поездки ожидал увидеть просто большой мегаполис. Но Шанхай оказался городом, где цифровые технологии стали частью повседневной жизни. Уровень внедрения, к которому

🔥18👍13🤝11

21 Jul 2026, 12:05 UTC724 views50 reactions1 Starread 6 August 2026
Photo

Материалы DevOps Lab: ML Edition уже доступны В конце июня мы провели первый 🤩DevOps Lab: ML Edition в Новосибирске. Собрали инженеров, техлидов и всех, кому интересно, как ML-сервисы живут в реальной производственной среде. Не устану благодарить всех, кто слушал доклады вживую. Ваши вопросы, споры и живое обсуждение превратили встречу из очередного митапа во встречу настоящего профессионального сообщества. Мы это

🔥21👍15🤝131

30 Jun 2026, 12:05 UTC763 views47 reactions2 Starsread 6 August 2026

Как прошел DevOps Lab: ML in Production В прошлую пятницу прошел первый митап из серии 🤩DevOps Lab. На нём мы разобрали, как ML-сервисы ведут себя в производственной среде. Выше записал вам небольшой тизер программы, а сегодня поделюсь своими наблюдениями в качестве организатора. ➡️Но сначала – важное. Спасибо каждому, кто пришёл, задавал вопросы, спорил, делился своим опытом и не расходился сразу после докладов. Т

🔥19👍15🤝13

30 Jun 2026, 12:00 UTC813 views42 reactions2 Starsread 6 August 2026
Video message

Video message, posted without a caption

👍16🔥14🤝9👏3

18 Jun 2026, 12:05 UTC835 views37 reactions2 Starsread 6 August 2026

LLM в проде на Kubernetes: как не сжечь бюджет на GPU Всем привет! Продолжаем серию постов про DevOps Lab: ML Edition, который состоится уже на следующей неделе, 26 июня. На повестке сегодня – второй анонс доклада. Актуальная тема для каждого, кто пробует запускать свои LLM. На митапе инженер Никсис Пётр Рукин разберет, как выстроить быстрый, надежный и безопасный инференс в Kubernetes. Приватные LLM – must-have д

🔥15👍12🤝91

11 Jun 2026, 12:09 UTC903 views23 reactionsread 6 August 2026
Poll

➡️Кстати, а какая у вас роль?

  1. Предприниматель0%
  2. Бизнесмен в ИТ4%
  3. Должность C-level13%
  4. Инженер17%
  5. Разработчик8%
  6. Бизнес-аналитик0%
  7. Менеджер проектов8%
  8. Маркетолог13%
  9. Другое38%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

👍9🔥6🤝61🤔1

11 Jun 2026, 12:05 UTC823 views22 reactions2 Starsread 6 August 2026

Как AI-агенты заменяют второго DevOps в компании из 50 человек Перед тем как уйти на заслуженные выходные, поделюсь с вами кейсом от Collabo. Продолжаю серию постов про DevOps Lab: ML Edition, который состоится 26 июня. Сегодня – анонс первого доклада. Тема близка многим руководителям и инженерам: как выживать, когда ты один DevOps на 50 разработчиков. ➡️Представьте, вы – DevOps-инженер. На вас 50 разработчиков, б

👍9🔥8🤝41

4 Jun 2026, 12:05 UTC513 views27 reactions2 Starsread 6 August 2026

Приглашаю на DevOps Lab: ML in Production Коллеги, всех с первыми летними рабочими днями! :) Сегодня не будет разговоров о болях или чек-листов с выводами. Хочу обсудить с вами кое-что поинтереснее – камерное событие. 26 июня мы в 🤩 Никсис проводим DevOps Lab: ML Edition. ➡️Но вернемся в начало. Почему мы вообще решили пробовать делать DevOps Lab, зачем тратить на это время и ресурсы, и почему в этом году тема -

👍7🔥753👌2🤝2😱1

28 May 2026, 12:05 UTC431 views22 reactions2 Starsread 6 August 2026

7 маркеров, что ваш аутстаффинг работает не на вас Сначала – важное. Коллеги, поздравляю вас с прошедшим Днём предпринимателя! Желаю, чтобы несмотря на любые изменения рынка, у нас оставались стабильные процессы, надёжные партнёры и пространство для роста. ➡️Итак, вы наняли инженера вне штата, оплачиваете его услуги по ставке опытного специалиста, а получаете проблемы, как от стажёра. Знакомо? Мы в Никсис сами явл

👍7🔥76🤝2

21 May 2026, 12:01 UTC462 views26 reactions2 Starsread 6 August 2026

Как мы превратили хаос в систему: выводы после 100+ проектов с поддержкой 24/7 В прошлом посте я делился особенностями круглосуточной технической поддержки. В нём затронул проблемы клиентов и подрядчика, но не раскрыл практических выводов и рекомендаций. Сегодня расскажу, как мы в Никсис перестроили процессы так, чтобы проблем становилось меньше, а порядка – больше. В прошлый раз я описал две стороны медали: ✳️клие

👍11🔥74🤝4

14 May 2026, 12:05 UTC447 views11 reactions2 Starsread 6 August 2026

Особенности техподдержки 24/7: проблемы клиентов и взгляд изнутри В этом месяце хочу поделиться болями внешних подрядчиков (аутсорса). Но не всех сразу, а только тех, кто обеспечивает заказчиков поддержкой 24/7. Мы в Никсис как раз специализируемся на этом уже более 15 лет. ✔️За 2025 и первую половину 2026 года через нашу поддержку прошло более 100 заказчиков. Запросы разнообразны, от «помогите развернуть проект» д

🔥54🤝2

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Jun 2026, 12:09 UTCAnonymous Poll24 voters

➡️Кстати, а какая у вас роль?

  1. Предприниматель0%
  2. Бизнесмен в ИТ4%
  3. Должность C-level13%
  4. Инженер17%
  5. Разработчик8%
  6. Бизнес-аналитик0%
  7. Менеджер проектов8%
  8. Маркетолог13%
  9. Другое38%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

31 Mar 2026, 12:05 UTCAnonymous Poll51 voters

Какой мессенджер предпочитаете вы, даже с учётом блокировки Telegram?❌

  1. Telegram82%
  2. Max6%
  3. Vkontakte2%
  4. Битрикс240%
  5. Signal0%
  6. Яндекс.Мессенджер0%
  7. Mattermost2%
  8. Свой вариант в комментариях8%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 12 March 2026 to 4 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 355,765 of 1,481,306entries 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.

Mentions

Named by 2 registered channels — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“ITibekin | Просто о цифровом” (@ITibekin_fm), 277 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/ITibekin_fm.

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.