Telegram RegisterThe public register of Telegram

Channel

[АРХИВ]ᅠᅠℒ𝘶𝘴𝘬!! — DESIGN

@Luskdesign

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

15subscribers

+0 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-1002606657493
TypeChannel
Username@Luskdesign
Description⌕ Люся, дизайнер готовый бесплатно сделать заказ ⌕ Начало— 16.05
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/Luskdesign

Growth

157 August 2026 — 15 subscribers11 August 2026 — 15 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 14–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 23:3115no change
7 Aug 2026, 16:1415first reading

Engagement

17 posts held, back to 7 September 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 pageof 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 17 posts for this entry, the most recent from 11 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
79
Links
38

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

19 reactions across 2 posts, in 6 distinct kinds. The most used accounts for 31.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5375182387334378777631.6%
custom 5339558902084153663421.1%
🐳421.1%
custom 5373275305890836049210.5%
💋210.5%
custom 522684709753744493415.26%

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

Measured over the 17 most recent posts we hold, published 7 September 2025 to 11 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Advertising

Ad load
17.6%
3 of 17 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
17.0
over 3 measured posts
Median views · rest
59.0
over 14 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 17 most recent posts we hold, published 7 September 2025 to 11 December 2025. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

11 Dec 2025, 07:30 UTC16 viewsread 11 August 2026
AdvertisementForwarded from @RaidGuardPhoto

❗️ УДАЛЕНИЕ ПОДПИСЧИКОВ — пугающая фраза, правда? Рейды, спам, удаление подписчиков — Это не вопрос «если», а вопрос «когда». Рейдеры уже в пути, чтобы удалить ваших подписчиков и заспамить канал. Не надейтесь на удачу. Защититесь. Встречайте Raid Guard — бот, который останавливает рейды и предотвращает удаление подписчиков. Всё это не мечты, а реальность, необходимая каждому. 🤩 Подключите Raid Guard — и забудьте

24 Oct 2025, 11:01 UTC17 viewsread 11 August 2026
AdvertisementForwarded from @RaidGuardPhoto

❗️ Ваш канал зарейдили — пугающее сообщение, правда? Рейды, спам, удаление подписчиков — Это не вопрос «если», а вопрос «когда». Рейдеры уже в пути, чтобы удалить ваших подписчиков и заспамить канал. Не надейтесь на удачу. Защититесь. Встречайте Raid Guard — бот, который останавливает рейды и предотвращает удаление подписчиков. Всё это не мечты, а реальность, необходимая каждому. 😈 Подключите Raid Guard — и забудь

21 Oct 2025, 10:07 UTC17 viewsread 11 August 2026
AdvertisementForwarded from @RaidGuardPhoto

🙏 Рейды. Спам. Удаление подписчиков. Это не вопрос «если», а вопрос «когда». Рейдеры уже в пути, чтобы удалить ваших подписчиков и заспамить канал. Не надейтесь на удачу. Защититесь. Встречайте Raid Guard — бот, который останавливает рейды и предотвращает удаление подписчиков. Всё это не мечты, а реальность, необходимая каждому. 😈 Подключите Raid Guard — и забудьте о рейдах, спаме и потере подписчиков. Спокойствие

16 Sept 2025, 12:01 UTC46 views2 reactionsread 11 August 2026
Forwarded from @DesignLuskaPhoto

〃 𝒩𝑒𝑤 𝒫𝑜𝑠𝑡 › ───────୨ৎ─────── ˖ ࣪ ִֶָ 𝑃𝑟𝑖𝑐𝑒 || — ⸰ 𖥔 ‌ࣳ 9 Реакций = новая работа !! 𝑇𝑎𝑔𝑠 ‹ #avatar #practice 𝆹𝅥 𝆹𝅥

💋2

14 Sept 2025, 09:12 UTC43 viewsread 11 August 2026
Forwarded from @DesignLuskaPhoto

〃 𝒩𝑒𝑤 𝒫𝑜𝑠𝑡 › ───────୨ৎ─────── ˖ ࣪ ִֶָ 𝑃𝑟𝑖𝑐𝑒 || — ⸰ 𖥔 ‌ࣳ 9 Реакций = новая работа !! 𝑇𝑎𝑔𝑠 ‹ #banner #order 𝆹𝅥 𝆹𝅥 ♱ 𝐑𝐄𝐖𝐈𝐄𝐖

13 Sept 2025, 15:26 UTC58 viewsread 11 August 2026

Собираюсь открывать заказы, переходите что бы следить за этим.

13 Sept 2025, 10:49 UTC59 viewsread 11 August 2026

Там всего шесть до тридцати осталось.

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

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

“[АРХИВ]ᅠᅠℒ𝘶𝘴𝘬!! — DESIGN” (@Luskdesign), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Luskdesign.

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.