Telegram RegisterThe public register of Telegram

Channel

it52.info

@it52info

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

4,905subscribers

-7 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001064683014
TypeChannel
Username@it52info
Created21 June 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/it52info

Growth

4,9044,9124,9085 August 2026 — 4,912 subscribers6 August 2026 — 4,912 subscribers9 August 2026 — 4,904 subscribers12 August 2026 — 4,905 subscribers4,9055 August 202612 August 2026
4 measurements spanning 6 days, net -7. 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 4,903–4,913 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 06:024,905+1
9 Aug 2026, 15:334,904-8
6 Aug 2026, 03:494,912no change
5 Aug 2026, 23:044,912first reading

Engagement

21 posts held, back to 10 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
43.5%
avg views ÷ 4,905 subscribers
Avg views / post
2,130
6 posts measured
Reaction rate
0.391%
reactions ÷ views · ER floor
Posts in window
6
of 21 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 6 August 2026
Posts held21 (10 June 20266 August 2026)
Views total12,790
Reactions total50
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:08 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

264 reactions across 20 posts, in 17 distinct kinds. The most used accounts for 28.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7628.8%
🤡4416.7%
🔥4015.2%
👍3714.0%
👎217.95%
💩166.06%
🥴62.27%
🤮51.89%
🤝41.52%
❤‍🔥31.14%
🙈31.14%
👌20.758%
👏20.758%
🤗20.758%
10.379%
🙏10.379%
🤣10.379%

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

Measured over the 21 most recent posts we hold, published 10 June 2026 to 6 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.

Recent posts

6 Aug 2026, 11:34 UTC≈1,600 views1 reactionsread 12 August 2026

📅 Мероприятия на неделю (06.08.2026 — 13.08.2026) 🏛 [Вебинар] Welcome Day к кейслабу по Информационной безопасности четверг, 06 августа 2026 15:00, Онлайн Телеграм: https://t.me/greenlab_greenatom Зарегистрироваться

1

4 Aug 2026, 01:29 UTC≈1,660 views8 reactionsread 12 August 2026

📅 Мероприятия на неделю (04.08.2026 — 11.08.2026) 🏛 [Встреча] Вечер невероятных ИТ-сторий среда, 05 августа 2026 18:30, г Нижний Новгород, ул Рождественская, д 44 Телеграм: https://t.me/gorky_drinkup Стоимость: 1000 ₽ Участников: до 50 Зарегистрироваться

3🤝3👍2

29 Jul 2026, 06:11 UTC≈2,270 views16 reactionsread 12 August 2026

[Видео]Дмитрий Петров: от жестких ИИ-сценариев к автономным агентам В третьем выпуске подкаста «УсталИИ?» генеральный директор группы IT-компаний Lad Дмитрий Петров рассказал о том, почему индустрия отказывается от жестких пайплайнов в пользу автономных мультиагентных систем и какие архитектурные и экономические риски несет такой подход. Подкаст «УсталИИ?» — проект группы IT-компаний Lad, посвященный практике приме

🔥7👍4🤡32

27 Jul 2026, 13:00 UTC≈2,030 views5 reactionsread 12 August 2026

[Встреча] DevRel-ужин №18 в Нижнем Новгороде: DevRel глазами тимлидов в эпоху ИИ Четверг, 30 июля 2026 19:30, г Нижний Новгород, Верхне-Волжская наб, д 9/1 ресторан "Три апельсина" Тема этой встречи — DevRel глазами тимлидов в эпоху ИИ 👉 Поразмышляем, что роднит деврела и тимлида, а где их интересы расходятся. 👉 Обсудим, как ИИ-инструменты меняют функции деврелов и тимлидов. 👉 Пофантазируем, как две этих профессии

3🤝1🙏1

22 Jul 2026, 10:40 UTC≈2,550 views11 reactionsread 12 August 2026

YADRO: Когерентность. Автоматизация в RTL и верификации Из подкаста вы узнаете: 📍в чем основная головная боль при построении чекеров кеша, 📍чем false sharing отличается от true sharing в верификации, 📍почему в верификации сложно разделить само тестирование и его автоматизацию, 📍как верификаторы в крупных компаниях оказываются «меж трех огней», 📍в чем заключается «проклятие воспроизводимости», 📍чего не хватает соврем

5👍3👎2👌1

15 Jul 2026, 16:23 UTC≈2,680 views9 reactionsread 12 August 2026

[Встреча] От идеи до производства: как генеративный ИИ меняет промышленность и бизнес Четверг, 16 июля 2026 18:00, г Нижний Новгород, ул Тургенева, д 30 Школа 21 Приглашаем на митап по генеративному ИИ в промышленности! Эта встреча открыта для всех, кому интересна тема искусственного интеллекта и то, как он применяется в разных организациях. Для жителей Нижнего Новгорода есть уникальная возможность посетить митап о

3👍3🙈3

12 Jul 2026, 16:14 UTC≈2,400 views5 reactionsread 12 August 2026

📅 Мероприятия на неделю (12.07.2026 — 19.07.2026) 🏛 [Встреча] T-Meetup: System Analysis среда, 15 июля 2026 19:00, г Нижний Новгород, ул Большая Покровская, д 18 Участников: до 150 Зарегистрироваться 🏛 [Встреча] Go Go Hopping Meetup четверг, 16 июля 2026 18:00, г Нижний Новгород, ул Большая Покровская, д 18 Участников: до 150 Зарегистрироваться 🏛 [Интерактивное мероприятие] Финальное демо проектов IT-академии Lad

2👌1👍1🔥1

10 Jul 2026, 05:12 UTC≈2,610 views13 reactionsread 12 August 2026

🍻 Мы в 2ГИС придумали легальный повод пройтись по барам в четверг вечером! 16 июля встречаемся на Go Go Hopping Meetup. План простой: 🍺 сначала — доклады от инженеров 2ГИС, Cloud.ru и MWS; 🍺 потом — бархоппинг по вечернему Нижнему; 🍺 бесплатное пиво для первых 30 участников на каждой точке; 🍺 а в финале — факап-разгоны без записи, слайдов и формальностей и тоже с пивом. И, кстати, ищем людей на разгоны. Мы хотим в

🔥13

7 Jul 2026, 06:10 UTC≈2,620 views12 reactionsread 12 August 2026

[Встреча] T-Meetup: System Analysis Среда, 15 июля 2026 19:00, г Нижний Новгород, ул Большая Покровская, д 18 DKRT Документация, которую покупают, Александр Пашин Системный аналитик, Т-Банк почему документация во внешних B2B-интеграциях напрямую влияет на скорость пресейла, качество оценки и доверие партнера; как на кейсе из финтеха правильная упаковка интеграции вдвое сократила время оценки разработки партнером и сд

6👍4❤‍🔥1🔥1

5 Jul 2026, 16:07 UTC≈2,220 views7 reactionsread 12 August 2026

📅 Мероприятия на неделю (06.07.2026 — 12.07.2026) 🏛 [Обучение] Летняя IT-школа группы компаний «ТЕКОМ» понедельник, 06 июля 2026 10:00, г Нижний Новгород, ул Карла Маркса, д 44Б Участников: до 40 Зарегистрироваться 🏛 [Встреча] PythoNN 10! 🎉: митап питонистов 10.07 пятница, 10 июля 2026 18:00, г Нижний Новгород, ул Алексеевская, д 6/16 Телеграм: https://t.me/pytho_nn Зарегистрироваться

4👍2🔥1

1 Jul 2026, 05:14 UTC≈3,240 views12 reactionsread 12 August 2026

[Встреча] PythoNN 10! 🎉: митап питонистов 10.07 Пятница, 10 июля 2026 18:00, г Нижний Новгород, ул Алексеевская, д 6/16 ИТ Лекторий «Горький Тех» Привет, лучшее сообщество Нижнего! Наши ежеквартальные митапы – снова раз в квартал. Можете поздравить нас и вас — всех — с юбилейным десятым номерным митапом. PythoNN 10! 🎉 В программе 4 крутейших юбилейных доклада от гостей города и (даже!) нижегородца: 🧙‍♂️"Как сообщ

5🔥4👍3

30 Jun 2026, 12:42 UTC≈2,480 views12 reactionsread 12 August 2026

[Встреча] Go Go Hopping Meetup Четверг, 16 июля 2026 18:00, г Нижний Новгород, ул Большая Покровская, д 18, Культурное пространство ДКРТ Go-разработчики, идём по барам с 2ГИС! Везём классных инженеров из 2ГИС, Cloud.ru и MWS, чтобы поговорить про OpenAPI, кодогенерацию, архитектурные паттерны и практику разработки на Go! Программа мероприятия: 📍Репозитория здорового человека, Даня Руденко, 2ГИС, Руководитель групп

6❤‍🔥2👍2💩1🔥1

Showing the 12 most recent of 21 posts we hold for @it52info. 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 — 283,505 of 1,169,250entries 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.

“it52.info” (@it52info), 4,905 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/it52info.

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.