Ecommerce storefront — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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
14 measurements spanning 66 days, net -16. 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 1,272–1,292 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Oct 2026, 12:37
1,274
-1
5 Oct 2026, 16:37
1,275
-4
27 Sept 2026, 20:40
1,279
-5
18 Sept 2026, 16:21
1,284
+5
14 Sept 2026, 05:59
1,279
-2
10 Sept 2026, 11:41
1,281
-1
5 Sept 2026, 03:21
1,282
-1
1 Sept 2026, 12:03
1,283
-1
24 Aug 2026, 09:54
1,284
-1
17 Aug 2026, 18:58
1,285
-2
14 Aug 2026, 21:04
1,287
-1
11 Aug 2026, 02:48
1,288
-2
7 Aug 2026, 22:33
1,290
no change
7 Aug 2026, 18:39
1,290
first reading
Engagement
15 posts held, back to 16 May 2025 — 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 15 posts for this entry, the most recent from 17 November 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
25s
Average length
6s
Measured directly from 4 videos 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
478 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 70.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
335
70.1%
🔥
80
16.7%
custom 5276155963500415100
36
7.53%
👍
22
4.60%
custom 5294053474474941060
4
0.837%
🎉
1
0.209%
Custom emoji. 2 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 15 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 478 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 16 May 2025 to 17 November 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.
Привет, дорогие!
В преддверии прекрасного праздника «День Мамы» мы решили запустить распродажу контентов к этому дню 🙌
Обзоры контентов по ссылкам:
🌷ДЕНЬ МАМЫ 2023 - https://t.me/DILANA_DECOR/1456
🌷ДЕНЬ МАМЫ 2024 - https://t.me/DILANA_DECOR/2255
📎СТОИМОСТЬ КАЖДОГО - 1️⃣9️⃣9️⃣0️⃣ вместо 3590₽
*список занятых городов в комментариях
Для покупки пишите мне в личные сообщения @DILANADECOR 🤍
Сегодня делали тот самый шар, про который я спрашивала)
У нас были фото только в стекле, а клиенту нужно было показать без стекла)
В общем такой роскошный цвет для девичника 🤩
Девочки мальчики, нужна ваша помощь 🫶
Может быть у кого-то есть фото шара 24’’ шелк розовый цветок с надписью?)
Можно в личку фото, очень буду благодарна 🤍 @dilanadecor
Добренького 🤍
Собираю букет из шдм и больше всего не люблю в этом процессе обрабатывать шары, то еще развлечение 🤪
Субтитры можно прочесть по выражению моего лица 🤣
Рубрика «беременные будни» 😂
Сегодня состоялась такая важная покупка 🥹
Увидела эту коляску и просто в неё влюбилась 💔
С каждым разом приходит больше осознания о приближающемся волшебном периоде 🥹
Доброго утра 🤍
Часто моё утро проходит так, в клинике)
И всегда меня сопровождает этот серьезный парень, переживает и поддерживает 🥹🫶🏼
❤20
Signed Dilana
Showing the 12 most recent of 15 posts we hold for @DILANA_DECOR. 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.
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 12 October 2026 — this
entry's latest reading, not the date you are reading this.
“DILANA DECOR 🤍 Аэродизайн” (@DILANA_DECOR), 1,274 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/DILANA_DECOR.
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.