Первый полуфинальный матч! Команды: ЛТ-028 (АТОМ), ЛТ-009 (ETERNITY), ЛТ-008 (SakhSplash), ЛТ-018 (OVERDRIVE TUSUR)
🔥7❤4

Channel
@SiberianRC
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
534subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001479389914 |
|---|---|
| Type | Channel |
| Username | @SiberianRC |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/SiberianRC |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 02:11 | 534 | no change |
| 9 Aug 2026, 10:33 | 534 | first reading |
10 posts held, back to 13 December 2025 — the 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 19 April 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
216 reactions across 10 posts, in 17 distinct kinds. The most used accounts for 32.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 70 | 32.4% | |
| 🔥 | 46 | 21.3% | |
| ❤🔥 | 28 | 13.0% | |
| custom 5226593548438095886 | 17 | 7.87% | |
| 👍 | 16 | 7.41% | |
| 👀 | 9 | 4.17% | |
| 🎄 | 8 | 3.70% | |
| 🐳 | 4 | 1.85% | |
| 💘 | 3 | 1.39% | |
| 🕊 | 3 | 1.39% | |
| 🎅 | 2 | 0.926% | |
| 💋 | 2 | 0.926% | |
| 💩 | 2 | 0.926% | |
| 🤓 | 2 | 0.926% | |
| 🤩 | 2 | 0.926% | |
| custom 5300839192090135053 | 1 | 0.463% | |
| custom 5463392464314315076 | 1 | 0.463% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 10 of the 10 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 216reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 13 December 2025 to 19 April 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.
Первый полуфинальный матч! Команды: ЛТ-028 (АТОМ), ЛТ-009 (ETERNITY), ЛТ-008 (SakhSplash), ЛТ-018 (OVERDRIVE TUSUR)
🔥7❤4
🚀 Через пару минут полуфинал! Мы в альянсе с ITRex и ETERNITY — втроём мощь, скорость и тактика. Дальше только победа! ⚡️ Пожелайте удачи 🤝🔥
❤9🕊3
Всем привет! На связи ETERNITY.👋 На момент начала написания этого поста до начала церемонии открытия международного чемпионата по робототехнике «Красноярск 7.0» осталось 2 часа и 28 минут, вероятно выложен он будет уже на самом открытии.🤩 Согласны, время поджимает, но всё же мы крайне рады приветствовать команды-участницы сего прекрасного мероприятия в нашем родном городе. Пока робот уже собран в коробку, полностью…
🔥8❤3
Всем привет! Вчера завершился финальный этап чемпионата ЛИГА Инженеров сезона 2025-2026 Код Истории в Минске! В результате чемпионата наша команда получила награду финалистов в номинации "Инженерный подход". Мы хотим поблагодарить всех организаторов, участников, волонтёров, судей и экспертов. Это были хоть и очень тяжёлые, но потрясающие три дня! Всем желаем удачи и до встречи в следующем сезоне!
❤🔥11❤5💋2
Это СУДЬБА! Вчера мы прошли инспекции, и расположились в нашей технической зоне. В ходе тренировок мы выявили проблемы с модулем сбора, которые нам удалось исправить за ночь. Сегодня мы прошли собеседование с экспертами и совсем скоро начнутся квалификационные матчи. Сейчас решаем проблемы с программным кодом.
❤🔥16👍3🔥2❤1custom 52265935484380958861
Всем привет на связи DESTINY🌟. Мы добрались до Минска, было тяжело, наш рейс отменили и мы экстренно меняли вид транспорта. Мы остановились в кампусе Технодом. Если здесь есть команды которые хотят познакомиться или кому нужна помощь, то обращайтесь!
🔥23❤7👍4🐳2💘1custom 53008391920901350531
Всем привет!👋 На связи Eternity — новая команда лиги технологий. Мы начали свой путь в этой лиге ещё в прошлом календарном году, но, к сожалению, по независящим от нас причинам, доступа к публикации новостей у нас не было.🤩 Мы исправились, поэтому постараемся компенсировать всё упущенное.👍 За это время мы успели поучаствовать в двух чемпионатах, о чем и расскажем поподробнее: Первым был робосиб, но, к сожалению…
custom 522659354843809588614👍7❤3🤓1custom 54633924643143150761
Здравствуйте дорогие Друзья! Наша команда DESTINY 🌟 уже на Региональном отборочном турнире Сибири 2026 в городе Братск. Мы уже прошли тех.осмотр и собеседование. А у нашего участника Никиты уже взяли интервью. Всем участникам чемпионата желаем хорошо провести время и получить удовольствие!
👀9🔥6👍2custom 52265935484380958862🐳1
Дорогие друзья мы всей командой DESTINY 🌟 хотим вас поздравить с новым годом! 🎄 В 2026 мы желаем всем знаний, опыта, новых вершин, побед.
❤19🎄8🎅2💘2🤩2❤🔥1
Прямо сейчас у нас проходит товарищеская встреча лиги решений, которую судим мы, участники команды DESTINY
❤19💩2🐳1🤓1
Showing the 10 most recent of 10 posts we hold for @SiberianRC. 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 — 640,594 of 1,478,351entries 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.
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.
Named by 3 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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Siberian Robotics Community” (@SiberianRC), 534 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/SiberianRC.
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.