Telegram RegisterThe public register of Telegram
Telegram profile photo for Дневник певицы

Channel

Дневник певицы

@thesingerdiary

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

103subscribers

-2 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-1002545520010
TypeChannel
Username@thesingerdiary
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/thesingerdiary

Growth

1031051047 August 2026 — 105 subscribers9 August 2026 — 105 subscribers22 August 2026 — 103 subscribers7 August 202622 August 2026
3 measurements spanning 15 days, net -2. 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 103–105 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 13:46103-2
9 Aug 2026, 09:01105no change
7 Aug 2026, 18:04105first reading

Engagement

12 posts held, back to 27 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
53.9%
avg views ÷ 103 subscribers
Avg views / post
55.5
12 posts measured
Reaction rate
10.1%
reactions ÷ views · ER floor
Posts in window
12
of 12 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held12 (27 July 20269 August 2026)
Views total666
Reactions total67
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 09:01 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
36s
Average length
18s

Measured directly from 2 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

67 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 35.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💯2435.8%
custom 52629299810795716251217.9%
custom 5265013461124923641811.9%
custom 5474160956642707749811.9%
custom 5451636889717062286710.4%
custom 547433175460716730457.46%
custom 519514433760791054434.48%

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

Measured over the 12 most recent posts we hold, published 27 July 2026 to 9 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.

Telegram Stars

Stars received
10
across the posts below
Posts paid on
10
of 12 we hold a reading for · 83%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @thesingerdiary. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 12 most recent posts we hold for this entry, published 27 July 2026 to 9 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

9 Aug 2026, 05:13 UTC17 views1 reactionsread 9 August 2026

И ещё...солнышки, у меня перебои с впн, поэтому посты будут с опозданием. Извините❤️ Всех обнимаю

💯1

Signed KUDRYASHOVA

9 Aug 2026, 05:12 UTC17 views1 reactionsread 9 August 2026
Photo

☺️❤️❤️☺️☺️❤️❤️❤️-> ❤️☺️❤️☺️☺️❤️ ❤️❤️☺️❤️☺️ ❤️ Кудряшечки, мы в пути. Я старшая по автобусу😹 Закинулась энергетиком. Бодренькая теперь😹

💯1

Signed KUDRYASHOVA

9 Aug 2026, 02:04 UTC24 views4 reactions1 Starread 9 August 2026
Photo

☺️❤️❤️☺️☺️❤️❤️❤️-> ❤️☺️❤️☺️☺️❤️ ☺️☺️❤️☺️❤️☺️ Всем доброе утречко😘 Настроение пока таковое, ибо я ещё не до конца проснулась. Сейчас умываемся, приводим себя в порядок. Пьём чаёчек и по-тихоньку выдвигаемся к месту сборчика

custom 52650134611249236414

Signed KUDRYASHOVA

8 Aug 2026, 19:49 UTC31 views2 reactions1 Starread 9 August 2026

☺️❤️❤️☺️☺️❤️❤️❤️-> ❤️☺️❤️☺️☺️❤️ Мини-влог ❤️ Стартуем с ❤️😊:❤️❤️

💯2

Signed KUDRYASHOVA

4 Aug 2026, 08:01 UTC66 views3 reactions1 Starread 9 August 2026

☺️❤️❤️☺️☺️❤️❤️❤️-> ❤️☺️❤️☺️☺️❤️ Мини-влог ❤️ 😊❤️☺️❤️☺️

custom 51951443376079105443

Signed KUDRYASHOVA

4 Aug 2026, 07:58 UTC67 views5 reactions1 Starread 9 August 2026
Photo

Привет, кудряшечки. Ну что? Заявку заполнили, билетик купили, осталось получить информацию и можно двигать

custom 54741609566427077495

Signed KUDRYASHOVA

3 Aug 2026, 13:39 UTC61 views10 reactions1 Starread 9 August 2026

Кудряшечки, приветик. У нас тут вроде как выезд намечается в Казань. Влог желаем? Давайте реакциями решим😹❤️

custom 52629299810795716257custom 54741609566427077493

Signed KUDRYASHOVA

28 Jul 2026, 14:11 UTC97 views9 reactions1 Starread 9 August 2026
Photo

Вот такие классные фотки получились у меня в воскресенье. Мне очень нравится. Спасибо @Vanek_6785, @anna_antonova0807, @dill0703, что попозировали мне❤️😻

💯7custom 54743317546071673042

Signed KUDRYASHOVA

28 Jul 2026, 14:07 UTC72 views6 reactions1 Starread 9 August 2026
Video

Со мной никогда не скучно, особенно @tcipovyazE Обработочка от @Prosto_Tasya56😹❤️

💯6

Signed KUDRYASHOVA

28 Jul 2026, 09:45 UTC71 views5 reactions1 Starread 9 August 2026

Кстати, я решила попробовать на матче портретную съёмку. Ребята, которых я успела сфоткать, остались довольны. Наверное вечером смогу закинуть фотки, только спрошу разрешения у людей, которых зацепила моя камера😹😹

custom 52629299810795716255

Signed KUDRYASHOVA

28 Jul 2026, 09:37 UTC73 views12 reactions1 Starread 9 August 2026
Video

Примерно так я выгляжу в реальной жизни❤️ Обработка @Prosto_Tasya56

custom 54516368897170622865custom 52650134611249236414custom 54743317546071673043

Signed KUDRYASHOVA

27 Jul 2026, 17:28 UTC70 views9 reactions1 Starread 9 August 2026
Photo

Привет, кудряшечки❤️ Футбольный выходной был у меня вчера. Из-за жары матч перенесли на 21:30 (по Оренбургу) Я приехала домой где-то в час, но оно того стоило. Первый тур и первая победа. Это супер💙🤍 P.S. на третьей фотке кстати, прошу знакомится, мой сммщик Тася😹❤️

💯7custom 54516368897170622862

Signed KUDRYASHOVA

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

“Дневник певицы” (@thesingerdiary), 103 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/thesingerdiary.

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.