Telegram RegisterThe public register of Telegram
Telegram profile photo for Axelix Project

Channel

Axelix Project

@axelix_official

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

137subscribers

+2 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-1003878960892
TypeChannel
Username@axelix_official
Created26 February 2026measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/axelix_official

Growth

1351371366 August 2026 — 135 subscribers8 August 2026 — 135 subscribers15 August 2026 — 137 subscribers6 August 202615 August 2026
3 measurements spanning 9 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 135–137 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 00:47137+2
8 Aug 2026, 23:45135no change
6 Aug 2026, 05:50135first reading

Engagement

16 posts held, back to 26 February 2026the 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
139.4%
avg views ÷ 137 subscribers
Avg views / post
191
4 posts measured
Reaction rate
8.90%
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 8 August 2026
Posts held16 (26 February 20268 August 2026)
Views total764
Reactions total68
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 23:45 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
41s
Average length
41s

Measured directly from 1 video 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

195 reactions across 12 posts, in 12 distinct kinds. The most used accounts for 47.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥9347.7%
4623.6%
👍2814.4%
🎉84.10%
🙏63.08%
🤝52.56%
21.03%
21.03%
💯21.03%
🍌10.513%
🐳10.513%
🫡10.513%

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 12 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 195reactions 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 26 February 2026 to 8 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

8 Aug 2026, 11:25 UTC58 views9 reactionsread 8 August 2026
Video

Axelix помогает обнаружить In Memory Pagination, N + 1 и ряд других проблем Hibernate в ваших сервисах. Но можно ли избежать некоторые из них при разработке (например, с помощью тестов)? На этот вопрос, ответил наш тех. лид Михаил Поливаха в своей статье 👇 https://habr.com/ru/companies/spring_aio/articles/1068176/

4🔥32

4 Aug 2026, 08:20 UTC141 views16 reactionsread 8 August 2026
Video

Вы можете ускорить отладку, изменяя уровни логирования в реальном времени - как в рабочей, так и в тестовой среде. Данная функциональность уже доступна в GA версии Axelix 😊 - Maven Central 📦 - Реестр контейнеров GitHub 🐳 - Helm Chart

🔥123🙏1

31 Jul 2026, 09:44 UTC312 views28 reactionsread 8 August 2026
Video

Друзья, мы это сделали. Axelix, наконец-то, вышел в GA! 🎉 Сегодня мы объявляем об общедоступной версии Axelix 1.0.0 - первом стабильном релизе, готовом к использованию в продакшене! Мы выпустили статью Axelix выходит в общий доступ. Путь в тысячу миль начинается с первого шага, в которой рассказали мотивацию за Axelix. Вместе с сообществом мы проделали большую работу: 1. Исправили все известные и зарепорченые нам

🔥14🎉86

24 Jul 2026, 15:02 UTC253 views15 reactionsread 8 August 2026

Всем привет! Мы уже очень близки к GA релизу, находимся на стадии финального тестирования. Как и говорили, летом выйдет GA. Уже совсем скоро :) А пока, мы выпустили статью "Натуральные ключи в БД. Последний раз объясняю!" под авторством нашего тех. лида - Миши Поливахи. В ней мы рассказываем на примере про конкретную ситуацию, которая рассказывает про важность суррогатного ID в БД и почему не стоит надеяться на на

👍64🔥4🫡1

5 Jul 2026, 09:25 UTC389 views6 reactionsread 8 August 2026

Друзья, привет! Если вам было интересно - Посмотреть на Axelix вживую - Детально разобраться в возможностях проекта - Узнать о текущем статусе разработки То сегодня в 21:00 МСК совместно с авторами канала Staff Engineer будет проведён стрим, где разберем все эти темы. Если вы человек технический, вам наверняка будет любопытно послушать, почему в Axelix были приняты те или иные архитектурные решения. Ссылка на ст

🔥41👍1

25 Jun 2026, 11:13 UTC537 views11 reactionsread 8 August 2026

Всем привет! За последний месяц к нам начали всё больше и больше приходить контрибьютеры со стороны - спасибо всем, кто неравнодушен сообществу! Мы стараемся поддерживать высокую планку качества как продукта, так и самой кодовой базы. Поэтому, у нас есть ряд довольно необычных и строгих проверок на этапе CI. В частности, мы ограничиваем размер PR-а для всех (в том числе для core команды) 500 строками кода. Мы неод

5🔥4👍2

10 Jun 2026, 06:48 UTC493 views25 reactionsread 8 August 2026

Друзья, привет! У нас по горячим следам и федбеку вышел второй Milestone, в котором 1. Мы исправили все известные и зарепорченые нам уязвимости. 2. И мы также исправили ряд багов, с которыми столкнулись пилотные команды. Напоминаем, что этим летом у нас выйдет полноценный GA релиз. Мы знаем, что большинство ждёт именно его :) Docker Образ: https://github.com/axelixlabs/axelix/pkgs/container/axelix/930040455?tag=1

10🔥7👍61🐳1

27 May 2026, 15:33 UTC431 views26 reactionsread 8 August 2026

Друзья, спустя примерно месяц после JPoint мы всё же это сделали: Мы выпустили первый Milestone релиз 🥂 Обращаем Ваше внимание, что первый GA релиз будет чуть позже, после того, как команда соберёт ранний feedback и адаптирует продукт под рынок. Дистрибутивы можно найти по следующим ссылкам: 1. Helm Chart Исходный код (если будет желание доработать) Helm Chart также есть на Artifacts Hub 2. Docker или Docker Com

🔥137🤝51

26 Apr 2026, 13:55 UTC343 views15 reactionsread 8 August 2026

Всем привет! Я надеюсь, что с частью из Вас мы увидимся на JPoint. Будет здорово пообщаться лично. На JPoint буду выступать я (Михаил Поливаха) и член core команды Axelix (Никита Кириллов). Axelix с момента презентации в МТС-Банке обзавёлся рядом крутых и полезных фич, которые попадут в первый релиз. На JPoint мы также обязательно её покажем! У нас в близжайшее время появятся первые Early Access билды, практически

🔥103🙏2

23 Mar 2026, 15:22 UTC273 views17 reactionsread 8 August 2026

Привет, друзья! Спустя довольно долгий ревью, мы-таки добавили поддержку логина через OIDC/OAuth2 в Axelix, ряд людей на митапах об этом просили. Кроме того, к первому релизу мы сделаем полноценную ролевую модель, которую нас также очень просили. Она пока в реализации. Теперь про релиз. Первый релиз мы сделаем чуть раньше JPoint, на котором и будем показывать уже всё, что есть. На самом деле мы завезли много новы

🔥93👍2💯2🍌1

6 Mar 2026, 13:51 UTC279 views19 reactionsread 8 August 2026

На МТС Банк митапе в кулуарах участники подняли вопрос о том, что рано или поздно Axelix скорее всего понадобиться БД. Сейчас Axelix полностью stateless. На самом деле, у нас и раньше на internal design звонках уже этот вопрос всплывал. В целом, любая система: - Zipkin - Grafana - SonarQube и т.д. Всем им нужна БД по разным причинам. Им всем нужно где-то хранить разную информацию: - Маппинг атрибутов пользователе

👍11🔥8

Showing the 12 most recent of 16 posts we hold for @axelix_official. 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 — 644,706 of 1,481,217entries 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.

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.

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

“Axelix Project” (@axelix_official), 137 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/axelix_official.

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.