Telegram RegisterThe public register of Telegram

Channel

IT Events RU

@iteventsru

On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry

2,960subscribers

+2 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-1001276513255
TypeChannel
Username@iteventsru
Created28 December 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/iteventsru

Growth

2,9582,9602,9596 August 2026 — 2,958 subscribers6 August 2026 — 2,958 subscribers12 August 2026 — 2,960 subscribers6 August 202612 August 2026
3 measurements spanning 7 days, net +2. 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 2,958–2,960 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:182,960+2
6 Aug 2026, 06:012,958no change
6 Aug 2026, 05:582,958first reading

Engagement

15 posts held, back to 26 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.9%
avg views ÷ 2,960 subscribers
Avg views / post
323
7 posts measured
Reaction rate
1.02%
reactions ÷ views · ER floor
Posts in window
7
of 15 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 2 of 7 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 held15 (26 December 20255 August 2026)
Views total2,258
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:15 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.

What this channel posts

Video runtime
28s
Average length
28s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

18 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥633.3%
👍527.8%
422.2%
🤬211.1%
🤔15.56%

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 7 of the 15 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 18reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 26 December 2025 to 5 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.

Advertising

Ad load
26.7%
4 of 15 posts carry an ad marker
Regulatory tokens
4
posts carrying an erid · 4 distinct tokens
Median views · ads
176
over 4 measured posts
Median views · rest
545
over 11 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFG3gNLh15 August 20265 August 2026
2W5zFGnVuhK116 June 202616 June 2026
2W5zFHNbdBF118 June 202618 June 2026
2W5zFHaPrxh15 August 20265 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 15 most recent posts we hold, published 26 December 2025 to 5 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

5 Aug 2026, 10:30 UTC≈154 viewsread 6 August 2026
Advertisementerid 2W5zFHaPrxhPhoto

🔥 Уже 12 августа стартует Школа разработки AI-агентов на Vibe Coding За 4 онлайн-занятия в Zoom вы: 🔸 освоите основы vibe coding 🔸 научитесь создавать современных AI-агентов 🔸 соберёте свои первые AI-проекты шаг за шагом Во время обучения вас ждут: ✔️ домашние задания с проверкой ✔️ поддержка кураторов ✔️ розыгрыши призов 🎓 По итогам школы вы получите сертификат о прохождении и создадите 9 AI-агентов для своего по

5 Aug 2026, 06:30 UTC≈176 viewsread 6 August 2026
Advertisementerid 2W5zFG3gNLhPhoto

🤷 Права доступа в Битрикс24 часто настраивают по ходу дела: одному сотруднику дали лишнее, другому закрыли нужное, а руководитель видит не те данные. В итоге страдают безопасность, процессы и контроль над коммерческой информацией. 🔗 10 августа в 19:00 МСК приглашаем вас на открытый урок, где разберём, как выстроить организационную структуру, группы пользователей и ролевую модель прав в CRM. На практическом примере

4 Aug 2026, 11:20 UTC239 viewsread 8 August 2026
Forwarded from @codeibnewsPhoto

🌄 Код ИБ ПРОФИ — выездной интенсив по кибербезопасности в формате «три дня учебы, два дня приключений». 🗓 9-13 сентября 2026 📍 Сочи, курорт «Роза Хутор» Что ждет участников? • Практические мастер-классы от CISO Сбербанка, Яндекса, VK, Билайна, Озон Банка, Райффайзенбанка и других ведущих компаний. Эксперты разберут реальные кейсы и подходы, которые редко обсуждаются публично. • Киберучения в штабе и на киберполиг

30 Jul 2026, 11:32 UTC380 views3 reactionsread 8 August 2026
Photo

🪄Рынок меняется, маржинальность снижается, привычные драйверы роста перестают работать, а скорость изменений делает запоздалую реакцию слишком дорогой. Сегодня выигрывают компании, которые умеют не просто собирать данные, а превращать их в своевременные управленческие решения. 🔝«Формула прибыли» — аналитический интенсив СберУниверситета для руководителей, которые хотят использовать аналитику как инструмент управлени

1🔥1🤔1

29 Jul 2026, 08:57 UTC380 viewsread 8 August 2026
Photo

Шахматный вечер в Сбер.Среде ♟ 31 июля собираемся провести вечер среди тех, кто любит доску и хорошую партию. Программа — просто топ! ✔️ Турнир по швейцарской системе. Играют все туры, без вылетов, независимо от результата. Трое счастливчиков получат мерч Сбера. ✔️ Сеанс одновременной игры с гроссмейстерами Андреем и Сергеем Дрыгаловыми: сразись с легендами шахматной индустрии. ✔️ Фриплей для тех, кто хочет просто

27 Jul 2026, 10:23 UTC430 viewsread 8 August 2026
Forwarded from @NikolskyPhoto

🏆 Запускаем школу спикеров Именно здесь будет проходить обучение и подготовка выступающих для Неконфы (спойлер: к процессу подключатся театралы. Научат не душнить, не падать в обморок перед выходом на сцену - и не падать в глазах зрителей на ней). 🔵 Завтра - первое событие в пилотном формате. Для самых быстрых - 5 бесплатных билетов по промокоду NIKOLSKY Взамен с вас - лайк, репост, обратная связь и советы по улу

23 Jul 2026, 10:01 UTC499 views6 reactionsread 8 August 2026
Photo

Открытый разговор про искусственный интеллект Факультет компьютерных наук НИУ ВШЭ собрал тех, кого редко можно увидеть в одном разговоре. Ведущие специалисты индустрии, известные исследователи и преподаватели ФКН ВШЭ встретятся, чтобы обсудить будущее искусственного интеллекта. Среди спикеров — эксперты, которые создают ИИ-продукты, руководят исследованиями и определяют развитие отрасли. Что обсудим? ⚪️ какие техн

2👍2🔥2

3 Jul 2026, 10:34 UTC671 viewsread 8 August 2026
Photo

Приглашаем на Infrastructure & Reliability Meetup от Спортса” 📍 10 июля - приходите на митап в Москве или подключайтесь онлайн. В программе четыре доклада для DevOps- и SRE-инженеров: • Как защитить GitLab Runner и не оставить лишних точек для атаки; • Как устроена CDN, что учитывать при миграции инфраструктуры и где обычно возникают проблемы; • Как внедрять ArgoCD и GitOps-подход в команде; • Как запускать GPU-за

18 Jun 2026, 07:30 UTC713 viewsread 8 August 2026
Advertisementerid 2W5zFHNbdBF

🛠 AI Weekends: Два дня практики, которые заменят месяцы самообучения Два дня очной практики о внедрении AI, где вы работаете руками под руководством экспертов. 4–5 июля в Москве мы соберемся, чтобы за одни выходные внедрить AI в ваши рабочие процессы. В чем уникальность? Вы выбираете один из трех параллельных воркшопов и погружаетесь в него на два полных дня. Никакого онлайна и записей — только живая работа. Выбер

16 Jun 2026, 10:23 UTC656 views0 reactionsread 8 August 2026
Advertisementerid 2W5zFGnVuhK

🕵️‍♂️ Кем мы будем работать через 3 года? Исследуем на Agentic Dev Conf Индустрия меняется быстрее, чем мы успеваем обновлять зависимости. AI-агенты уже не просто пишут сниппеты, они начинают брать на себя целые этапы SDLC. Что это значит для нас? Мы перестанем быть «писателями кода» и станем «дирижерами агентов»? 3 июля в Москве пройдет Аgentic Dev Conf - конференция, целиком посвященная агентной архитектуре и буд

15 Jun 2026, 06:02 UTC545 views3 reactionsread 8 August 2026
Photo

Приглашаем на открытый онлайн Devhands AI Meetup #2! 📅 Когда: 18 июня, начало в 18:30 (Мск) 🔗 Где: Zoom (ссылку опубликуем в день митапа в чате @devhandsai) Формат: блиц по 7 минут, только личный опыт и кейсы, без воды. ~45 минут выступления подряд без вопросов, ~45 минут — обсуждение и вопросы. Программа на 18 июня: • «ACP как база для агентской автоматизации» Алексей Самойлов, Techlead в Fasronome • «Системный

👍3

10 Jun 2026, 10:05 UTC690 views3 reactionsread 8 August 2026
Photo

Приходи на C# Speed Dating — 2 часа на полезные знакомства 23 июня пройдет вечер коротких онлайн-знакомств для C#-разработчиков. Как все пройдет Участники будут рандомно делиться по парам и общаться в Zoom. Будет 6 раундов по 10 минут. Зачем приходить — обсудишь темы, которые вызывают споры: AI, карьера, архитектурные паттерны и метрики. — заберешь идеи и практики, которые работают у других, и поделишься своим опы

🔥3

Showing the 12 most recent of 15 posts we hold for @iteventsru. 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,254,237 of 1,350,102entries 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

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.

“IT Events RU” (@iteventsru), 2,960 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/iteventsru.

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.