Telegram RegisterThe public register of Telegram
Telegram profile photo for IT мероприятия России / ITMeeting / IT events

Channel

IT мероприятия России / ITMeeting / IT events

@iteventsrus

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

17,036subscribers

+219 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001848072420
TypeChannel
Username@iteventsrus
DescriptionIT события России: форумы, конференции, митапы, вебинары, хакатоны и т.д. Обменивайся опытом и развивай свои навыки на лучших IT-событиях! По рекламе и всем вопросам: @romanroman_pr РКН: https://u.to/2JcOIg https://telega.in/?r=SQWEDnZ7
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/iteventsrus

Topic

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 10 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@iteventsrus/2245 · this entry24 Jul 2026, 15:15 UTC@freeitevent/154427 Jul 2026, 07:05 UTC1.003 days
@freeitevent/154931 Jul 2026, 07:31 UTC@iteventsrus/2258 · this entry3 Aug 2026, 08:15 UTC1.003 days
@freeitevent/156021 Aug 2026, 08:01 UTC@iteventsrus/2279 · this entry21 Aug 2026, 12:15 UTC1.004.2 hours
@iteventsrus/2280 · this entry24 Aug 2026, 09:14 UTC@freeitevent/156425 Aug 2026, 07:15 UTC1.0022 hours
@iteventsrus/2285 · this entry25 Aug 2026, 14:14 UTC@freeitevent/156627 Aug 2026, 07:01 UTC1.0041 hours
@freeitevent/157128 Aug 2026, 09:33 UTC@iteventsrus/2292 · this entry28 Aug 2026, 14:15 UTC1.004.7 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@freeitevent8 (8/8 hand-verifiable sample passed)1.0032 hourseven
@ITMeeting6 (6/6 hand-verifiable sample passed)1.0022 hours@ITMeeting (4–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 6 of the 8 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 90 comparable posts for this entry, running 24 July 2026 to 15 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_copy · clone_mutual, last confirmed 16 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

16,81617,03616,9267 August 202613 November 2026
61 measurements spanning 98 days, net +219. 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 16,783–17,069 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
13 Nov 2026, 18:0717,036+24
11 Nov 2026, 02:2017,012+62
8 Nov 2026, 02:5916,950-2
6 Nov 2026, 23:2716,952+5
5 Nov 2026, 20:2116,947+26
4 Nov 2026, 19:2816,921-3
3 Nov 2026, 19:5016,924+29
2 Nov 2026, 18:4516,895+36
1 Nov 2026, 15:3616,859+1
31 Oct 2026, 18:5616,858-7
30 Oct 2026, 18:4016,865-1
29 Oct 2026, 00:2916,866-5
27 Oct 2026, 20:5516,871-3
26 Oct 2026, 23:4616,874-1
25 Oct 2026, 22:0616,875-1
24 Oct 2026, 19:2916,876-4
23 Oct 2026, 18:3016,880-3
22 Oct 2026, 20:5616,883-1
21 Oct 2026, 19:2816,884-5
20 Oct 2026, 11:5516,889first reading

Engagement

91 posts held, back to 24 July 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 81 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.5%
avg views ÷ 17,036 subscribers
Avg views / post
1,970
37 posts measured
Reaction rate
0.559%
reactions ÷ views · ER floor
Posts in window
37
of 91 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 16 November 2026
Posts held91 (24 July 2026 – 16 November 2026)
Views total72,762
Reactions total407
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 06:33 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

Photos
≈1,460
Videos
≈40
Links
≈1,430

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 03s
Average length
21s

Measured directly from 3 videos 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

1,234 reactions across 90 posts, in 7 distinct kinds. The most used accounts for 38.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤47138.2%
🔥36329.4%
👍26321.3%
⚡705.67%
🆒292.35%
🦄221.78%
🥰161.30%

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

Measured over the 91 most recent posts we hold, published 24 July 2026 to 16 November 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
2
across the posts below
Posts paid on
2
of 91 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @iteventsrus. 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 91 most recent posts we hold for this entry, published 24 July 2026 to 16 November 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.

Advertising

Ad load
42.9%
39 of 91 posts carry an ad marker
Regulatory tokens
37
posts carrying an erid · 37 distinct tokens
Median views · ads
2,120
over 39 measured posts
Median views · rest
2,290
over 52 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2Vtzqv872FP128 October 202628 October 2026
2VtzqwXr6XV12 September 20262 September 2026
2VtzqwvRMwB121 October 202621 October 2026
2VtzqxC7uok111 November 202611 November 2026
2VtzqxiJa3u119 August 202619 August 2026
2W5zFG285z1122 October 202622 October 2026
2W5zFG6JYnV127 August 202627 August 2026
2W5zFGNKHQD125 August 202625 August 2026
2W5zFGWK89w129 July 202629 July 2026
2W5zFGfGRxM12 September 20262 September 2026
2W5zFGjHBTw128 July 202628 July 2026
2W5zFGrZQiD119 August 202619 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. 25 further tokens are held for this entry and not listed here.

Measured over the 91 most recent posts we hold, published 24 July 2026 to 16 November 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

Telegram’s own ‘edited’ marker: 0 of 37 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 06:15 UTC278 views2 reactionsread 16 November 2026
Photo

Lé.codes запускает 48-часовой онлайн-хакатон lé.codes48 🚀 Собери мобильное приложение или интерактивный проект с помощью AI и преврати идею в работающий продукт всего за 48 часов. 💫 Общий призовой фонд — 200 000 ₽ 💫 Приложения победителей опубликуют в App Store и Google Play 💫 Готовый проект можно добавить в портфолио, а права на него останутся за командой Два трека — выбирай свой: • Продукт: создай приложение, ко…

❤1🔥1

15 Nov 2026, 06:15 UTC984 views6 reactionsread 16 November 2026
Photo

🚀 Последний шанс присоединиться к «Коду города»! Регистрация до 15 ноября Хочешь поработать над реальными технологическими задачами, получить опыт и побороться за денежный приз? Успей подать заявку! «Код города» — студенческий кейс-чемпионат от МГТС, одного из крупнейших операторов фиксированной связи Москвы. Тебе предстоит предложить решение реальной задачи компании, которая развивает телеком-инфраструктуру столич…

👍4❤1🔥1

13 Nov 2026, 10:46 UTC≈1,260 views3 reactionsread 16 November 2026
Advertisementerid 2W5zFGurTh4Photo

🚀 PostCode Challenge 2.0 — хакатон по ИИ от Почтатеха и Университета Иннополис Разработайте сервис для Почты России и поборитесь за призовой фонд 1 800 000 ₽. Три задачи на выбор: • автоматизация обработки исходящей почты; • создание прототипа подписки «Почта Премиум»; • разработка веб-сервиса для повышения энергоэффективности почтовых отделений. Вас ждут: ✅ практика с ИИ, аналитикой и веб-разработкой на реальных…

❤2🔥1

13 Nov 2026, 06:15 UTC≈1,260 views3 reactionsread 16 November 2026
Advertisementerid 2W5zFJyXwjQPhoto

ИИ, процессы и решения руководителя: как управлять результатом. TeamLead Conf — 3 и 4 декабря, Москва, кампус Сколково. Очно (один или два дня) или онлайн. Перестроить разработку под ИИ, вовремя пересмотреть проект и понять, почему команда буксует. Какие решения помогут тимлиду в новой реальности? В программе TeamLead Conf 2026 — 50+ докладов и 6 треков: — Андрей Усенко. Как перестроили разработку в сторону AI-na…

❤3

12 Nov 2026, 09:15 UTC≈1,440 views5 reactionsread 16 November 2026
Photo

До Импульса Т1 — одна неделя ⚡️ 19 ноября в Москве состоится ИТ-конференция Импульс Т1. Если вы еще не зарегистрировались, сейчас самое время это сделать. В программе — 5 направлений, 70+ практических активностей и более 2 000 активных участников ИТ-сообщества. В этом году можно будет отрабатывать знания на практике сразу после докладов: 🔘на код-ретрите — практиковаться в парном программировании и TDD 🔘в ресурсны…

❤5

12 Nov 2026, 06:15 UTC≈1,440 views4 reactionsread 16 November 2026
Advertisementerid 2W5zFJrSpDQPhoto

ИИ, автоматизация и цифровые технологии: что действительно нужно бизнесу? Внедрение технологий само по себе не гарантирует результата. Важно понимать, какие процессы стоит автоматизировать, что можно доверить ИИ и как использовать цифровые инструменты, чтобы принимать обоснованные решения даже в условиях неопределённости На бизнес-завтраке «Точка опоры» вместе с экспертами обсудим, как меняется B2B-рынок, какие воз…

❤4

11 Nov 2026, 12:15 UTC≈1,640 views21 reactionsread 16 November 2026
Advertisementerid 2VtzqxC7uokPhoto

ИИ-агенты, которые понимают бизнес: контекст, регламенты и сквозные рабочие процессы Чтобы включить ИИ-агентов в бизнес-процессы, недостаточно просто поставить задачу. Нужно задать правила работы, обеспечить сохранение контекста и определить, когда агент действует самостоятельно, а когда подключает сотрудника. ⏰ 12 ноября в 11:00 на вебинаре эксперты VK Tech расскажут, как задавать правила работы автономным агентам…

🔥7❤6👍6⚡1🥰1

11 Nov 2026, 06:15 UTC≈1,660 views7 reactionsread 16 November 2026
Photo

МГТС запускает студенческий кейс-чемпионат «Код города» 🚀 Реши реальную бизнес-задачу, разработай технологическое решение при поддержке экспертов МГТС и поборись за призы! 💫 Общий призовой фонд — 600 000 ₽ 💫 Фаст-трек на стажировку в МГТС для команд, занявших 2-е и 3-е места. Три направления — выбирай своё: • Робототехника: разработай алгоритм для сервисного робота, который самостоятельно проходит маршрут и обходи…

❤5🔥2

10 Nov 2026, 17:50 UTC≈1,700 views3 reactionsread 16 November 2026
Photo

🚩 «Лига ЦТФ» — Всероссийская лига по кибербезопасности открывает первый сезон Командные CTF-соревнования для студентов вузов и ссузов со всей России: онлайн-раунды в течение всего сезона и суперфинал в Москве. 📅 Раунды: • 1 раунд — 21 ноября, онлайн • 2 раунд — 19 декабря, онлайн • 3–5 раунды — в 2027 году, даты будут объявлены позже 📊 За что играем • рейтинг команд — 10 лучших выходят в суперфинал • рейтинг вузов…

❤3

10 Nov 2026, 06:15 UTC≈2,520 views10 reactionsread 16 November 2026
Photo

🔥 КИБЕР 102 — всероссийский хакатон в Уфе и онлайн, 13–15 ноября Три дня и две ночи, чтобы превратить идею в работающий прототип. Настоящие задачи — от министерств и компаний Башкортостана с дальнейшими перспективами работы Что решают команды: — веб-платформы и мобильные приложения — VR/AR, симуляторы и тренажёры — ИИ-агенты, чат-боты, нейросети — игры и геймификация Как проходит: 13 ноября — открытие, постановка …

❤6🔥4

9 Nov 2026, 17:15 UTC≈1,850 views16 reactions1 Starread 16 November 2026
Forwarded from @roseltorg_tgPhoto

Нейросеть подключили, но быстрее не стало? Сократить подготовку сайта с получаса до минуты возможно, но вместе с инструментами придётся менять и подход к работе. 🎙 19 ноября на RLT.Conf Владимир Клюев, руководитель АРТИКМЕДИА и эксперт по разработке веб-платформ, поделится опытом перехода на вайбкодинг. Разберём, кто ставит задачи и отвечает за результат, а также что делать, если код нельзя передавать во внешнюю м…

❤10🔥6

9 Nov 2026, 13:15 UTC≈1,830 views6 reactionsread 16 November 2026
Photo

Собственный ЦОД, колокейшн, облако или МЦОД — универсально правильного варианта нет. Каждая модель по-разному отвечает на требования бизнеса к устойчивости, масштабированию, контролю и экономике. 12 ноября приглашаем на онлайн-дискуссию, где вместе с экспертами разберем, как выбрать и обосновать инфраструктурную стратегию перед бизнесом. Обсудим: ▪️ Критерии выбора. Какие требования бизнеса и ограничения ИТ-службы…

❤3🔥3

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

Posts recorded as deleted after publishing

We recorded 1 post on @iteventsrus as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
12 November 2026
Most recent seen missing
12 November 2026
Median time before seen missing
6 days
Seen missing in the last 30 days
1

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Кулинария | Блюда
@kulinar_b · 36,117
Telegram ranks this channel #62 of 71 here — alongside 70 others — read 1 September 2026
Ozon Tech
@ozon_tech · 30,231
Telegram ranks this channel #68 of 98 here — alongside 97 others — read 8 September 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“IT мероприятия России / ITMeeting / IT events” (@iteventsrus), 17,036 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/iteventsrus.

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.