Channel
@KenaxeSkins
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
462subscribers
-8 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002266831702 |
|---|---|
| Type | Channel |
| Username | @KenaxeSkins |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/KenaxeSkins |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 10:37 | 462 | -12 |
| 30 Aug 2026, 03:05 | 474 | -2 |
| 23 Aug 2026, 12:36 | 476 | +6 |
| 6 Aug 2026, 20:04 | 470 | no change |
| 6 Aug 2026, 19:52 | 470 | first reading |
19 posts held, back to 15 July 2026 — 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 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 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
220 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 68.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 150 | 68.2% | |
| 🔥 | 24 | 10.9% | |
| 👌 | 21 | 9.55% | |
| 💘 | 7 | 3.18% | |
| 🎉 | 5 | 2.27% | |
| 🍌 | 3 | 1.36% | |
| 🥰 | 3 | 1.36% | |
| 👏 | 2 | 0.909% | |
| 💋 | 2 | 0.909% | |
| 🤔 | 2 | 0.909% | |
| 🤯 | 1 | 0.455% |
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 220 reactions 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 15 July 2026 to 6 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.
Обычный парень 😗 Быть может это довольно-таки непримечательный скин, однако главное, что я смог выполнить простую задачу клиента, а он в свою очередь доволен результатом! Заказать скин. 👈
❤6🔥1🥰1
Вишневое настроение 🌸 Продолжая серию костюмов для моего основного скина в этот раз я одел моего персонажа в тематическое худи и светлые джинсы, которые идеально впишутся в биом вишневой рощи. Есть идеи для новых костюмов? Пиши в комментарии! Заказать скин. 👈
❤9💘1
Инопланетный заказ 👽 Заказчик попросил сделать скин его персонажа, а также одеть его в простенькую рубашку, галстук и такие клетчатые шорты. И, разумеется, клиент остался доволен результатом! Заказать скин. 👈
❤12
Варден и мороженое 👀 Две новые вариации моего персонажа, и я точно уверен, что следующий костюм будет посвящен биому цветущей вишни. Есть ли у вас идеи для новых вариаций? Пишите в комментарии! Заказать скин. 👈
❤10🔥2🥰2
Сегодня я создал второй, неосновной канал связанный с моим творчеством. В нем я буду постить то, что стараюсь не постить тут чтобы не заполнять канал постами: сникпики, опросы, незначительные новости и т.д. Кто хочет – залетайте: https://t.me/+0bUIh4KBi6g1MWZh
❤6
Напоминаю, что розыгрыш начался! Шансы очень высоки
🎉5❤2
Тигровое худи 🐯 Две вариации моего основного скина, сделанные для ивента на одном сервере. Возможно в будущем будет еще больше разных забавных вариаций одежды для моего персонажа) Заказать скин. 👈
❤12🔥2
Милый аксолотль 💞 Простенький скин на заказ, задачей которого было сделать аксолотля. Вышла такая очаровательная работа, которая сразу же понравилась клиенту. Заказать скин. 👈
❤10🔥2
Напоминаю, что через неделю начнется розыгрыш на моем Бусти, и я советую всем приобрести подписку! На данный момент всего 4 платных подписчика, а это значит что шансы очень высоки! 😙
🔥7🍌2❤1
Трейд с ббюзером 🏰 Это мой второй трейд с ним (первый я не публиковал вроде), но в этот раз на определенную тематику. Посмотреть его часть работы можно в его канале. Ставьте лайки пишите комментарии все дела 🫶🫶 Заказать скин. 👈
❤8🔥1
Уютный котик 🐱 Заказчик попросил меня изобразить его кота в виде Майнкрафт скина, а также одеть его в милый, бежевый свитер. Заказать скин. 👈
❤14🔥1
Они из Dead by Daylight 👹 Хоть я и не играл в эту игру, я смог выполнить этот заказ, сохранив все главные детали персонажа. Как сказал заказчик, получилось у меня очень хорошо! Заказать скин. 👈
❤10🔥1
Showing the 12 most recent of 19 posts we hold for @KenaxeSkins. 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.
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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Kenaxe” (@KenaxeSkins), 462 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/KenaxeSkins.
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.