Telegram RegisterThe public register of Telegram
Telegram profile photo for Дневник Стилиста

Channel

Дневник Стилиста

@dnevnikstilista

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

1,941subscribers

-3 since we began measuring on 17 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001622384130
TypeChannel
Username@dnevnikstilista
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 September 2026
Last confirmed live19 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/dnevnikstilista

Growth

1,9411,9441,942.517 September 2026 — 1,944 subscribers17 September 2026 — 1,944 subscribers19 September 2026 — 1,941 subscribers17 September 202619 September 2026
3 measurements spanning 2 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 1,941–1,944 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 11:171,941-3
17 Sept 2026, 12:221,944no change
17 Sept 2026, 11:471,944first reading

Engagement

18 posts held, back to 2 May 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.

ERR · 30 days
17.6%
avg views ÷ 1,941 subscribers
Avg views / post
342
13 posts measured
Reaction rate
2.19%
reactions ÷ views · ER floor
Posts in window
13
of 18 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 11 of 13 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 15 September 2026
Posts held18 (2 May 202615 September 2026)
Views total4,442
Reactions total84
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Sept 2026, 12:22 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.

Reaction mix

92 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 48.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4548.9%
2426.1%
👍1819.6%
💯33.26%
👌11.09%
🥰11.09%

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

Measured over the 18 most recent posts we hold, published 2 May 2026 to 15 September 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

15 Sept 2026, 13:12 UTC207 viewsread 17 September 2026

Первые 3 дня — полный доступ ко всем функциям бесплатно. https://t.me/ipshka_buh_bot?start=ref_4

15 Sept 2026, 13:12 UTC206 views1 reactionsread 17 September 2026

Мои друзья разработали бота, который сможет заменить вам бухгалтера. Он умеет вести финансовый учет, формировать договоры, отчеты и ещё много разных документов.

👍1

15 Sept 2026, 13:10 UTC205 views2 reactionsread 17 September 2026

Сегодня советы будут не только по стилю. Но и для бизнеса.

🔥2

8 Sept 2026, 07:46 UTC394 views11 reactionsread 17 September 2026
Photo

РЫЖИЙ-БЕЖЕВЫЙ-СЕРЫЙ Серый с бежевым хорош, а как акцентный цвет рыжий и оранжевые оттенки часто смотрятся выигрышно и эффектно.

👍7🔥3💯1

8 Sept 2026, 07:44 UTC328 views10 reactionsread 17 September 2026
Photo

СИНИЙ-СЕРЫЙ-БЕЛЫЙ Серый с синим всегда хорошо. А белый дополнит образ как универсальный цвет-ахромат, который вписывается во многие сочетания.

👍54💯1

8 Sept 2026, 07:43 UTC316 views10 reactionsread 17 September 2026
Photo

БОРДО + БЕЖ Эти два цвета выглядят дорого, а в сочетании еще больше усиливают друг друга.

5🔥3👍1💯1

7 Sept 2026, 17:15 UTC347 views21 reactionsread 17 September 2026

Сегодня три новых сочетания, каждое из которых мне нравится даже больше, чем первые три. Дайте немного 🔥

🔥201

6 Sept 2026, 16:54 UTC390 views5 reactionsread 17 September 2026

Это базовые, простые сочетания. Но мне больше нравятся образы посложнее, поярче. Осенью особенно. А вы что скажете? Пишите в комментариях, какой стиль вам ближе

5

6 Sept 2026, 16:52 UTC395 viewsread 17 September 2026
Photo

серый с бежевым и молочным уже стал базой, благодаря коллекциям таких брендов как Loro Piana и Brunello Cucinelli. Универсально, солидно и свежо.

6 Sept 2026, 16:51 UTC388 views3 reactionsread 17 September 2026
Photo

Черный с серым — беспроигрышное сочетание для мужчин, которые не хотят сложных сочетаний и ярких цветов.

🔥3

6 Sept 2026, 16:51 UTC380 views4 reactionsread 17 September 2026
Photo

Синий универсальнее, чем черный. Выбирайте за основу в гардеробе его. И одно из эффектных сочетаний на все времена — это синий с разными оттенками коричневого.

🔥4

5 Sept 2026, 15:42 UTC413 views9 reactionsread 17 September 2026

Сегодня начнем тему цветовых сочетаний на осень. От простых к сложным. Каждый день буду делиться с вами тремя сочетаниями, и так три дня 👌🏼

👍4🔥21👌1🥰1

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Мужской стилист Денис Гаврилов
@denisgavrilovstyle · 22,214
Telegram ranks this channel #5 of 61 here — alongside 60 others — read 21 September 2026
Александр Ганин | О стиле
@sashganinstyle · 23,896
Telegram ranks this channel #12 of 51 here — alongside 50 others — read 17 September 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Дневник Стилиста” (@dnevnikstilista), 1,941 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/dnevnikstilista.

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.