Telegram RegisterThe public register of Telegram
Telegram profile photo for Katdsgn | дизайню жизнь

Channel

Katdsgn | дизайню жизнь

@katdsgn_freelance

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

281subscribers

-3 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-1002147253980
TypeChannel
Username@katdsgn_freelance
CreatedBetween 1 March 2024 and 31 August 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/katdsgn_freelance

Growth

281284282.57 August 2026 — 284 subscribers8 August 2026 — 284 subscribers15 August 2026 — 281 subscribers7 August 202615 August 2026
3 measurements spanning 7 days, net -3. 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 281–284 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 01:28281-3
8 Aug 2026, 08:20284no change
7 Aug 2026, 22:01284first reading

Engagement

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

ERR · 30 days
31.4%
avg views ÷ 281 subscribers
Avg views / post
88.2
5 posts measured
Reaction rate
11.5%
reactions ÷ views · ER floor
Posts in window
5
of 7 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. It is computed over the 4 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held7 (3 July 20267 August 2026)
Views total441
Reactions total45
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 08:20 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
5s
Average length
5s

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

91 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 58.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5358.2%
🔥1617.6%
❤‍🔥1213.2%
🍓77.69%
😍22.20%
💋11.10%

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

Measured over the 7 most recent posts we hold, published 3 July 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, 16:31 UTC49 views3 reactionsread 8 August 2026
Forwarded from @YANtechPhoto

📌 До Yandex Ecom Open Air — 2 недели Пять треков и один летний фестиваль для ecommerce. Обсудим, как ИИ меняет путь к покупке, что сегодня двигает продажи и где бизнесу искать новые точки роста. Мы собрали программу — теперь составьте свою. 📌 По секрету: выступлениями дело не ограничится. Уже готовим множество подарков для участников офлайна и онлайна, сотни наборов мерча и десятки активностей от Яндекс Рекламы и

3

7 Aug 2026, 16:31 UTC51 viewsread 8 August 2026

мы готовимся а вы приходите онлайн / офлайн 🔥

6 Aug 2026, 12:03 UTC85 views14 reactionsread 8 August 2026
Photo

Я наконец победила бесконечный скролл Уже примерно неделю почти не листаю рилсы…. Если честно, я давно понимала, что как дизайнер и человек, который сам создаёт контент, мне хочется быть больше создателем, чем потребителем Но одно дело понимать, а другое — действительно перестать автоматически открывать инстаграм Особенно когда работа тоже связана с блогом: сторис, рилсы, публикации… А сейчас, когда я быстрее у

🔥14

3 Aug 2026, 15:05 UTC120 views10 reactionsread 8 August 2026

Кажется, проблема не в отсутствии времени Сегодня поймала себя на интересном моменте Знаю, что для многих дизайнеров соцсети — это самая больная тема Кажется, что нужно много времени постоянно что-то придумывать регулярно публиковать монтировать писать искать идеи… Сегодня у меня было буквально 30 минут В очереди в поликлинике Пока сидела там, успела: — подготовиться к съёмке двух рилсов — полностью прописат

❤‍🔥63🔥1

1 Aug 2026, 19:58 UTC136 views18 reactionsread 8 August 2026
Photo

Kimpact Design Awards 2026 сегодня прошёл без меня, но с моими презами 🥹 Безумно приятно получать весточки из зала! И каковы же результаты? В прошлом году в категории «Продающая презентация» мне покорилась номинация «Мощный первый экран» В этом году берём выше 🔥 Номинация «Креативный подход» в категории «Продающая презентация» 🔥 Номинация «Эффект вау» в категории «Свободная тема» Так сказать 2 из 2 Рада быть

10❤‍🔥6🍓2

5 Jul 2026, 12:18 UTC214 views15 reactionsread 8 August 2026
Photo

считаю, что более вайбовое начало отпуска нельзя и придумать [пока только на 2 недельки] а вообще это мы уехали к моим родителям на выходные дома ремонт [вообще отдельная история] а здесь тихо, спокойно и вкусно кормят 🥹

11😍2🍓1🔥1

3 Jul 2026, 18:59 UTC205 views31 reactionsread 8 August 2026
Photo

Кажется, я не писала сюда уже почти полгода… И, наверное, за это время произошло самое большое изменение в моей жизни [вдруг вы не подписаны на инсту и ещё не знаете] Да, нас скоро станет трое 🤍 [ну или 5, если считать котеек, а мы считаем] Когда я узнала о беременности, это было одновременно неожиданно и очень долгожданно [а случилось это ещё в феврале] Самое забавное, что буквально за несколько дней до этого у

26🍓4💋1

Showing the 7 most recent of 7 posts we hold for @katdsgn_freelance. 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 — 668,726 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.

Forward network

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.

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.

“Katdsgn | дизайню жизнь” (@katdsgn_freelance), 281 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/katdsgn_freelance.

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.