Telegram RegisterThe public register of Telegram

Channel

RULKC

@linux_kernel_O

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

780subscribers

+0 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-1001997827165
TypeChannel
Username@linux_kernel_O
DescriptionRussian Linux Kernel Community Общаемся тут: https://t.me/osdevconf Про сообщество тут: http://rulkc.org/
CreatedBetween 1 October 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/linux_kernel_O

Growth

7806 Aug 2026, 22:18 — 780 subscribers6 Aug 2026, 22:30 — 780 subscribers6 Aug 2026, 22:186 Aug 2026, 22:30
2 measurements taken within a single day. 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 779–781 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 22:30780no change
6 Aug 2026, 22:18780first reading

Engagement

16 posts held, back to 31 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
145.5%
avg views ÷ 780 subscribers
Avg views / post
1,140
4 posts measured
Reaction rate
1.83%
reactions ÷ views · ER floor
Posts in window
4
of 16 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 5 August 2026
Posts held16 (31 December 20255 August 2026)
Views total4,540
Reactions total83
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 22:30 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
55
Videos
9
Links
48

Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

319 reactions across 16 posts, in 14 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥13742.9%
👍5416.9%
🎉3310.3%
👏3210.0%
154.70%
🎄144.39%
👎82.51%
🤩61.88%
🤯61.88%
51.57%
🫡41.25%
🌚20.627%
😎20.627%
🤣10.313%

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

Measured over the 16 most recent posts we hold, published 31 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.

Recent posts

5 Aug 2026, 09:59 UTC344 views4 reactionsread 6 August 2026
Photo

#партнёрский_пост Всем привет. Конференция Импульс Т1 ищет спикеров! 19 ноября пройдёт технологическая конференция Импульс Т1. До 15 августа принимают заявки от экспертов, которые готовы поделиться рабочими кейсами и опытом. В этом году на конференции будет упор на практику: выступления пройдут в формате диалога с аудиторией, а в программе появятся мастер-классы, лаборатории и игровые симуляции. Предложить тему в

🔥2👍1👎1

1 Aug 2026, 05:51 UTC436 views25 reactionsread 6 August 2026
Forwarded from @bitemask

Posted without readable text

🔥14👏5🤩5🎉1

23 Jul 2026, 10:04 UTC≈2,580 views27 reactionsread 6 August 2026
Photo

❌🔤🔤🔤🔤🔤🔤❌ ❌🔤🔤🔤🔤🔣❌❌ ❌🔤🔤🔤❌1️⃣4️⃣❌ ❌6️⃣⏺3️⃣0️⃣🔤🔤❌ Всем привет! И сегодня у нас очумелые новости 🎱 Мы открываем регистрацию на третий митап RULKC 🔥 В этот раз предлагаем встретиться на территории всем нам хорошо известной компании, которая уже на протяжении почти трёх десятилетий является одной из самых технологичных в стране и за её пределами - Яндекс🌹 Вас ожидают два технических доклада по ядру Linux, свежие новости п

🔥15🎉63😎2👍1

16 Jul 2026, 06:34 UTC≈1,180 views27 reactionsread 6 August 2026

👩‍💻😒 LINUX IS NOT ANTI-AI PROJECT Ночью 15 июля на LKML разгорелся очередной горячий спор о месте LLM-инструментов в разработке ядра. Тред на LKML, начавшийся как техническое обсуждение интеграции AI-ревьюера Sashiko с системой отслеживания патчей Patchwork, перерос в принципиальный спор о роли LLM в Linux ядре и завершился политическим вердиктом Линуса Торвальдса, который фактически легализует использование AI-инс

👏14🤯6👎3🌚2🫡2

25 May 2026, 10:05 UTC≈1,230 views31 reactionsread 6 August 2026
Photo

Russian Linux Kernel Community — серебряный призёр IT HR AWARDS 2026 в номинации «Люди в фокусе» В конце апреля в Санкт-Петербурге прошла ежегодная премия IT HR AWARDS. Сообщество Russian Linux Kernel Community (RULKC) заняло II место в партнёрской номинации от Selectel «Люди в фокусе» в треке «Сообщества». Вячеслав Бочаров, член оргкомитета RULKC, участвовал в церемонии награждения премии, отметил: "Участие в так

🔥20👍6🎉3👏1🤣1

16 Apr 2026, 12:16 UTC≈1,890 views17 reactionsread 6 August 2026

Друзья, всем привет! 👋 Как и обещали, запись второго митапа готова и уже ждёт вас на видеоплатформах. Специально для тех, кто не смог быть в Технопарке лично, мы подготовили качественную запись каждого из двух докладов. Можно смело открывать предпочитаемую платформу и смотреть: 📖 Первый доклад: Linux Device Drivers для свежих ядер 🔧 Второй доклад: Пара слов о LOCKDEP 📍 Где смотреть? Выбирайте удобную платформу:

🔥83👍3👎21

13 Apr 2026, 08:01 UTC≈1,580 views22 reactionsread 6 August 2026
Photo

Релиз Linux 7.0 🐧 12 апреля 2026 года состоялся стабильный релиз ядра Linux 7.0. Смена мажорной версии (с 6.x на 7.0) произошла не из-за одного кардинального нововведения, а согласно предпочтению Линуса Торвальдса повышать major-версию после достижения номера X.19. Тем не менее, новая ветка включает множество значительных улучшений. Ключевые изменения: · Поддержка нового оборудования – расширена работа с будущими

🔥13👍54

10 Apr 2026, 15:20 UTC≈1,450 views15 reactionsread 6 August 2026
Photo

Всем привет! Наш партнёр Yandex Cloud приглашает участников RULKC на ежегодный митап about:cloud — infrastructure 16 апреля. На митапе вы сможете заглянуть «под капот» инфраструктурных сервисов Yandex Cloud: разберём реальные нетривиальные кейсы, обсудим ошибки, которые можно избежать в разработке, и поговорим с разработчиками — честно и без воды. В программе 5 докладов (разверни, чтобы узнать какие) 1. IaC для уп

🔥7👍5👏3

27 Mar 2026, 16:20 UTC≈1,410 views12 reactionsread 6 August 2026
Photo

Поехали! 🫡 Ссылка на трансляцию: https://mts.mts-link.ru/j/MTC/16871997784/stream-new/15975526230

👍6🔥4🫡2

27 Mar 2026, 13:32 UTC≈1,150 views4 reactionsread 6 August 2026
Photo

Скоро начинаем! 👋 ‼️Вход в Медиарум отдельный!

3🔥1

25 Mar 2026, 08:53 UTC≈7,740 views7 reactionsread 6 August 2026
Photo

🚶🚶🚶🚶🚶🚶🔠🔠🔠🔠🔠💡🔠🔠🔠🔠🔠🔠🔣2️⃣ Друзья, всем привет! Напоминаем, что 27 марта на базе технопарка МТС RULKC проведет второй по счету (и первый в 2026) митап. В этот раз представим два доклада. 📖 Первый доклад: Linux Device Drivers для свежих ядер Классическая книга, которая выросла вместе с ядром, — теперь в новом контексте. Разберём, что изменилось в написании драйверов за последние годы и как не потеряться в актуальном A

🔥4🎉2👏1

16 Mar 2026, 10:04 UTC≈1,360 views11 reactionsread 6 August 2026
Photo

Всем привет. До митапа RULKC который пройдет 27 марта меньше двух недель. Регистрации уже идут и если у Вас был план поучаствовать, то самое время зарегистрироваться. Регистрация на митап доступна по ссылке: https://tabs.mts.ru/share/shrjzSDNCwDjT3kp6VNWE --- А пока наши коллеги из ИнженеркаТех продолжают разбирать неочевидные, но невероятно мощные инструменты инженера. На очереди – Nix. 📹 Открытый воркшоп в рамка

4👍2👎2🔥2👏1

Showing the 12 most recent of 16 posts we hold for @linux_kernel_O. 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 — 115,485 of 1,160,990entries 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

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 4 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.

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

“RULKC” (@linux_kernel_O), 780 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/linux_kernel_O.

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.