Telegram RegisterThe public register of Telegram
Telegram profile photo for KennixDev - Software Engineer

Channel

KennixDev - Software Engineer

@KennixDev

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

62subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001621120873
TypeChannel
Username@KennixDev
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live30 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 30 August 2026
On Telegramt.me/KennixDev

Growth

616261.57 August 2026 — 61 subscribers10 August 2026 — 61 subscribers23 August 2026 — 62 subscribers7 August 202623 August 2026
3 measurements spanning 16 days, net +1. 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 61–62 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 21:5962+1
10 Aug 2026, 04:4561no change
7 Aug 2026, 16:1561first reading

Engagement

15 posts held, back to 17 May 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 page of 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 15 posts for this entry, the most recent from 10 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

30 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 36.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1136.7%
custom 4958617898751886363516.7%
custom 5370955972011366737413.3%
🤔310.0%
custom 520887870671763674326.67%
custom 535066385356058156926.67%
👾26.67%
🤯13.33%

Custom emoji. 4 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 are Telegram’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 13 of the 15 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 17 May 2025 to 10 February 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
6
across the posts below
Posts paid on
2
of 14 we hold a reading for · 14%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @KennixDev. 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 15 most recent posts we hold for this entry, published 17 May 2025 to 10 February 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.

Recent posts

10 Feb 2026, 10:16 UTC105 views3 reactionsread 10 August 2026
Forwarded from @gamedev_my_love

🚀 JJS GAMES ищет Unity-программиста (2+ года) и 2D-художника в инди-команду JJS GAMES - делаем лёгкие, быстрые и драйвовые игры для: 🎮 Яндекс Игры; 📱 Google Play; 🌍 CrazyGames и других платформ. Мы активно растём, выпускаем проекты и расширяем команду. Ищем людей на энтузиазме, которым важно не просто закрывать задачи, а реально влиять на продукт и видеть результат своей работы в релизах. 🎯 Кого ищем 👨‍💻 Unity-раз

🤔3

Signed Innokenty [Kennix88]

23 Jan 2026, 09:14 UTC114 views2 reactionsread 10 August 2026
Forwarded from @dima_gamedev

Всем привет, друзья! 🐧 Хочу откровенно поделиться мыслями о нашем релизе на «Яндекс Играх». Проговорить вслух — тоже часть пути. Что было: 01.01.2026 наша маленькая команда JJS Games выпустила «Пингвинье Мемори». Мы пробыли на платформе 22 дня и, если честно, почти полностью потеряли аудиторию. Да, звучит грустно — но для нас это ценный урок, а не конец. Почему так вышло? Мы проанализировали и вот что поняли: 🎯 1

👾2

Signed Innokenty [Kennix88]

3 Jan 2026, 09:06 UTC110 views1 reactionsread 10 August 2026
Forwarded from @gamedev_my_love

🚀 А теперь, наши планы на будущее Сначала хочу поздравить всех с новым годом и поделиться новостями!🎄 Вместе с геймдизайнером мы выложили Пингвинье Мемори - нашу первую игру на Яндекс Играх. Подробнее в посте выше. 💡 Размышления и планы: Яндекс Игры начали урезать доходы для разработчиков и смещаются в сторону внутриигровых покупок. Для меня интереснее Steam - там больше свободы творчества и возможностей для раз

🔥1

Signed Innokenty [Kennix88]

2 Jan 2026, 19:32 UTC85 views1 reactionsread 10 August 2026
Forwarded from @gamedev_my_love

🚀 Наша первая игра на Яндекс Играх! Я вместе с геймдизайнером выложил Пингвинье-Мемори - карточную игру «на память» в холодной пингвиньей стилистике. Кстати, это первый опыт публикации на платформе Яндекс Игр. 🐧 О чём игра: - Собирайте пары карточек с пингвиньими спортивными предметами, чтобы заполучить священное яйцо. - За каждую комбинацию начисляются монеты, которые можно тратить на подсказки, перемещения карт

🔥1

Signed Innokenty [Kennix88]

2 Jan 2026, 19:32 UTC73 viewsread 10 August 2026

Мои друзья и партнёры, выложили свою первую игру на Яндекс игры. Давайте поддержим их☺

Signed Innokenty [Kennix88]

1 Dec 2025, 13:05 UTC164 views1 reactionsread 10 August 2026
File

File, posted without a caption

🔥1

Signed Innokenty [Kennix88]

1 Dec 2025, 13:05 UTC128 views2 reactionsread 10 August 2026

🤪 Подготовил сегодня сейф зоны для коротких видео (Шортс/Рилс/ТТ/ВкКлипы). Это зоны, где могут быть элементы интерфейса платформы, то есть акцентный контент там не стоит размещать. Также там есть превью зоны, а то как платформы обрезают кадр для превью (для тех, которых нет превью файла, там используется полный размер 9:16). — Исходник в фигме Вкратце: начинаю заниматься монтажом коротких видео. Сейчас делаю загото

🔥2

Signed Innokenty [Kennix88]

6 Oct 2025, 06:17 UTC421 views1 reactionsread 10 August 2026

Изменения за 2+ недели, с момента последнего сообщения (Скриншоты приложу ниже, следующим сообщением) 1. Реализовано пополнение баланса за TON. На бэкенде создан криптопроцессинг для обработки платежей в TON. Удивительно, но платежи в TON проходят быстрее, чем за Звезды. Телеграм. 2. Улучшена система приглашения друзей. Теперь при нажатии «Отправить сообщение» можно отправить оформленное сообщение с изображением, к

custom 49586178987518863631

Signed Innokenty [Kennix88]

1 Sept 2025, 14:29 UTC878 views2 reactionsread 10 August 2026

Помните я говорил про Open Dev Community? Теперь это Solyanka Community — Сообщество, объединяющее людей из разных сфер. Цель — стремиться развивать профессиональные навыки, общаться, находить единомышленников, получать поддержку и отдыхать. Немного поменялись принципы сообщества, теперь оно более обширное и включает в себя геймеров, стримеров/блогеров и т.д. Будем рады если вы вступите и будите участвовать в разв

🤯1custom 49586178987518863631

Signed Innokenty [Kennix88]

15 Aug 2025, 08:29 UTC654 views3 reactionsread 10 August 2026

🚀 КОЛЛАБОРАЦИЯ Объявляем о коллаборации "KennixDev" и "JJS Games" 🤝 В чем заключается коллаб? 1. Совместно мы разработаем ряд приложений/игр для Телеграм с последующим запуском и поддержкой их. 2. В планах разработать простые игры для телеграм на продажу, разного ценового диапазона. С возможностью запуска под ключ. Демо каждой игры будем запускать. 3, Разработка приложений/игр под заказ. ✏️ ПРИНИМАЕМ ЗАЯВКИ НА РАЗР

🔥3

Signed Innokenty [Kennix88]

2 Aug 2025, 14:34 UTC231 views2 reactionsread 10 August 2026
Photo

Что-то происходит 🤔

🔥2

Signed Innokenty [Kennix88]

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

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

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

“KennixDev - Software Engineer” (@KennixDev), 62 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/KennixDev.

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.