Telegram RegisterThe public register of Telegram

Channel

Процессоры Эльбрус | Фан-клуб

@e2k_fans

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

1,578subscribers

+2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001375114359
TypeChannel
Username@e2k_fans
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/e2k_fans

Growth

1,5761,5781,5777 August 2026 — 1,576 subscribers7 August 2026 — 1,576 subscribers8 August 2026 — 1,577 subscribers10 August 2026 — 1,578 subscribers7 August 202610 August 2026
4 measurements spanning 4 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 1,576–1,578 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 23:131,578+1
8 Aug 2026, 01:381,577+1
7 Aug 2026, 08:321,576no change
7 Aug 2026, 08:241,576first reading

Engagement

19 posts held, back to 20 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
44.1%
avg views ÷ 1,578 subscribers
Avg views / post
695
9 posts measured
Reaction rate
5.16%
reactions ÷ views · ER floor
Posts in window
9
of 19 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 7 August 2026
Posts held19 (20 June 20267 August 2026)
Views total6,256
Reactions total323
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 18:00 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
8m 38s
Average length
2m 53s

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

561 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 46.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥25846.0%
👍25345.1%
376.60%
😁61.07%
😱30.535%
🎉20.357%
🤔20.357%

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

Measured over the 19 most recent posts we hold, published 20 June 2026 to 7 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

7 Aug 2026, 12:14 UTC175 views15 reactionsread 7 August 2026
Forwarded from @serpasPhoto

Вместе с ребятами из Codenrock для отборочного этапа Кубка сделали онлайн-компилятор под Эльбрусы (это когда код пишете в веб-форме, а компиляция происходит на удалённом сервере и вам отображается результат). Контраст с прошлым годом, когда нам приходилось доступ участников и их решения обрабатывать и перепроверять в полуручном режиме, колоссальный. Теперь хоть 1000 участников, разницы нет. Платформа всё сама сдела

🔥9👍41🎉1

1 Aug 2026, 10:08 UTC437 views42 reactionsread 7 August 2026
Forwarded from @imaxairuPhoto

ВНЕЗАПНО в OpenSSL работают ровные ребята и приняли поддержку Эльбруса у себя (e2k) https://github.com/openssl/openssl/pull/31269 📸 Скриншот Telegram | VK | MAX

👍26🔥16

23 Jul 2026, 21:13 UTC915 views33 reactionsread 7 August 2026

https://ixbt.games/news/2026/07/23/na-rossiiskom-processore-elbrus-protestirovali-the-witcher-3-i-quake-2-rtx.html

👍20🔥112

23 Jul 2026, 08:13 UTC644 views44 reactionsread 7 August 2026
Forwarded from @retro_museum

Сколько бы Я не просил Дмитрия, делать анонсы сильно заранее, чтобы в канале был какой-то эксклюзив, но Дмитрий ни в какую. Если ролик готов, значит сразу в релиз. Негоже, чтобы зрители ждали. Трудно с ним не согласиться=] Сегодня ваш любимый(судя по просмотрам на канале) Эльбрус. Установка видюхи от зеленых. И проверка на играх Смотреть на утюбе Смотреть на рутюбе

🔥2114👍9

20 Jul 2026, 06:15 UTC587 views57 reactionsread 7 August 2026
Forwarded from @elbrus_pc_testVideo

Ещё одна супер новость! Первый запуск GTA 5 нативно собранного для Эльбруса. В декабре 2024 года в сеть утекли исходники, что и позволило сделать такой порт. Ещё есть баги, но начало многообещающее🎉 Выражаю огромную благодарности товарищу "AiD iEvE" за такую невероятную работу💪

👍31🔥188

18 Jul 2026, 11:43 UTC600 views21 reactionsread 7 August 2026
Forwarded from @ElbrusMCSTPhoto

В МИФИ прошёл торжественный выпускной. Более 20 компаний-партнёров поздравили выпускников с окончанием университета. В этот день дипломы получили более 300 выпускников московской площадки и свыше 600 выпускников из 14 филиалов. Наша компания приняла участие в качестве одного из ведущих работодателей-партнёров. С поздравлением к выпускникам обратился Сергей Королёв, начальник отдела развития общего программного обесп

👍20🔥1

18 Jul 2026, 11:42 UTC392 views18 reactionsread 7 August 2026
Forwarded from @elbrus_pc_testPhoto

Всем привет. По ссылке из предыдущего поста добавлены драйвера для всех актуальных архитектур Эльбрус.

🔥12👍6

17 Jul 2026, 12:57 UTC376 views62 reactionsread 7 August 2026
Forwarded from @elbrus_pc_testPhoto

Разрывная пятничная новость🎉🎉🎉 Некий аноним связался со мной и прислал мне драйвер для видеокарт Nvidia собранный для Эльбруса из утекших исходников в 2022 году. Драйвер поддерживает видеокарты до RTX20 серии включительно. Пока есть сборка только для 8с2 (он же 8СВ), но обещает позже прислать под остальные e2k архитектуры (отдельным постом поделюсь всем присланным). Протестировано на Nvidia GTX1070 т.е. на архитектур

🔥43👍152🎉1😁1

16 Jul 2026, 18:19 UTC≈2,130 views31 reactionsread 7 August 2026
Photo

Среда рабочего стола Cosmic портирована под Эльбрус. На момент портирования это была последняя версия с гита. Сейчас уже появился новый минор. Примерно 2 недели ковырялся со сборкой различных всех компонентов и дико странной и не удобной системой зависимостей, которую наворотили System76. Потребовалось большое количество патчей, но все они сравнительно небольшие. Один релиз требует 10 разных версий одного и того ж

👍23🔥8

14 Jul 2026, 11:47 UTC496 views22 reactionsread 7 August 2026
Forwarded from @serpasPhoto

Друзья, регистрация на «Кубок СЭРПАС 2026» открыта! Алгоритмическое программирование на процессорах Эльбрус (e2k), C/C++, один трек, два этапа, 4 задачи, призовой фонд 400 000 ₽ и стажировка для победителя в МЦСТ. Целевая аудитория — студенты и выпускники технических специальностей от 18 до 24 лет. В этом году отборочный этап проходит на Codenrock (да, они интегрировали наши серверы на Эльбрус-8СВ в свою платформ

🔥13👍72

9 Jul 2026, 18:43 UTC≈1,350 views44 reactionsread 7 August 2026

Sitronics Group создала опытные образцы серверной платформы на базе 16-ядерных микропроцессоров «Эльбрус-16С» разработки АО «МЦСТ». Сервер предназначен для построения защищенных узлов критической информационной инфраструктуры.

🔥30👍14

27 Jun 2026, 16:53 UTC≈1,400 views26 reactionsread 7 August 2026

На данный конкретный момент больше всего нагрузки в том же ведьмаке, сжирается - внезапно, Ведьмаком. 1. Код RedEngine - это боль. Любой закрытый движок - это боль. Разработчики CDPR перешли на UE5, потому что не осталось людей хорошо умеющих в него, а обучать каждый раз новые кадры - это боль в квадрате. 2. Никаких подробных открытых документаций, сама по себе архитектура весьма специфична. Это не UE или Unity. Но

👍17🔥5😱3😁1

Showing the 12 most recent of 19 posts we hold for @e2k_fans. 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 — 921,789 of 1,176,613entries 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

Republished by

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

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

“Процессоры Эльбрус | Фан-клуб” (@e2k_fans), 1,578 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/e2k_fans.

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.