Telegram RegisterThe public register of Telegram
Telegram profile photo for Илюха Изъянов

Channel

Илюха Изъянов

@izyanov_design

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

536subscribers

+115 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-1003566434004
TypeChannel
Username@izyanov_design
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/izyanov_design

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 40% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

421536478.56 August 2026 — 421 subscribers6 August 2026 — 421 subscribers15 August 2026 — 467 subscribers21 August 2026 — 512 subscribers27 August 2026 — 518 subscribers3 September 2026 — 530 subscribers12 September 2026 — 536 subscribers6 August 202612 September 2026
7 measurements spanning 37 days, net +115. 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 404–553 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 07:57536+6
3 Sept 2026, 23:38530+12
27 Aug 2026, 14:59518+6
21 Aug 2026, 06:28512+45
15 Aug 2026, 07:05467+46
6 Aug 2026, 19:31421no change
6 Aug 2026, 15:18421first reading

Engagement

14 posts held, back to 6 July 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 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 14 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

157 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 80.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12780.9%
🐳138.28%
🗿117.01%
🤬63.82%

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

Measured over the 14 most recent posts we hold, published 6 July 2026 to 3 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

3 Aug 2026, 16:18 UTC180 views6 reactionsread 6 August 2026

Федю (бадди из Сбера) весь Сбер всегда ценил за возможность мутить совершенно сумасшедшие концепции. С одной стороны среда обязывала: студии, R&D команда, Лаборатория, с другой стороны уникальный, авторский вижн Отдельный кайф, когда братва рвётся воплощать свои идеи в жизнь. Зацените, что намутил Федя 👏

6

3 Aug 2026, 16:18 UTC180 views10 reactionsread 6 August 2026
Forwarded from @AcidCrunchPhoto

О старых идеях и их новых воплощениях У меня есть старая привычка: я почти каждый день в свободное время придумываю разного рода концепты. Мемные приложения, мобильные игры, отдельные фичи, странные сервисы. Большинство идей оседало в заметках. Самые везучие добирались до Figma, превращались в красивые макеты и отправлялись на цифровое кладбище за неимением знакомого разраба который бы доделал проект до конца. И т

10

27 Jul 2026, 12:18 UTC432 views25 reactionsread 6 August 2026
Video

UI анимации Опыт пользователя во многом определяется интерактивом: ui-анимации, физический отклик, саунд-дизайн. Я всегда делал анимации «по ощущению» и опирался только на свою интуицию: красиво или нет. Часть рефов вообще вызывала ощущение волшебства и недосягаемости — типа, как отдельный вид искусства Но! Есть пара материалов, после изучения которых магия анимаций становится ближе. Даже если часть из этого понима

25

27 Jul 2026, 08:10 UTC358 views17 reactionsread 6 August 2026
Photo

нишевого во мне дохуя

13🐳3🗿1

25 Jul 2026, 15:01 UTC386 views9 reactionsread 6 August 2026

Вайб-кодинг — Лови волну! 🖱 Принёс вам почитать: https://telegra.ph/Vajb-koding--Lovi-volnu-07-24 Выжимка: — Раньше между «придумал» и «проверил в деле» лежала пропасть: нарисовать, описать, передать в разработку, дождаться сборки. Проверка задумки — это розы и слёзы — поэтому ошибка стоила дорого, а смелые задумки стерилизовались ещё на макете: рисовали то, что с большей степенью вероятности получится собрать. Тепе

6🐳3

21 Jul 2026, 15:52 UTC453 views9 reactionsread 6 August 2026
Photo

я слишком молод для гемблы…

9

17 Jul 2026, 12:04 UTC630 views18 reactionsread 6 August 2026
Photo

Делюсь мыслями перед предстоящей работой над портфолио. Разделяете?

14🐳2🤬2

14 Jul 2026, 13:24 UTC667 views9 reactionsread 6 August 2026

я в телевизоре хвалебно вышло, оставим на откуп пиарщикам )) команде рилэйта и Сене респект!

8🐳1

13 Jul 2026, 11:14 UTC630 views7 reactionsread 6 August 2026
Photo

Хватит откладывать портфолио Больше 65% хотят переделать или оформить с нуля своё портфолио. Я тоже хочу обновить своё: поменять структуру, сделать всё ещё проще и чище, + освежить стили. Задумка уже есть, на реализацию нужно выделить пару дней Чтобы было веселее (и я был в фокусе), хочу собраться группой и вместе поработать над портфолио. За две недели проведём ~4 созвона и обсудим: • структура портфолио • оформлен

6🐳1

8 Jul 2026, 10:37 UTC548 views10 reactionsread 6 August 2026
Photo

Вертикальные отступы только вниз Опытным путём дошёл. Вертикальные отступы у блоков лучше задавать вниз Почему так: 1. Правишь один отступ вместо двух 2. Переставлять блоки легко, соседей править не нужно 3. Предсказуемо — отступ всегда на одном месте Обращаете внимание на такие детали? Или это уже слишком?

10

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

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

“Илюха Изъянов” (@izyanov_design), 536 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/izyanov_design.

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.