Telegram RegisterThe public register of Telegram
Telegram profile photo for дарья тут

Channel

дарья тут

@daryaisnothere

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

6,542subscribers

+1,286 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002401391108
TypeChannel
Username@daryaisnothere
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/daryaisnothere

Growth

5,2566,5425,8997 August 2026 — 5,256 subscribers7 August 2026 — 5,256 subscribers8 August 2026 — 5,281 subscribers10 August 2026 — 5,362 subscribers14 August 2026 — 5,621 subscribers17 August 2026 — 5,736 subscribers20 August 2026 — 6,125 subscribers24 August 2026 — 6,329 subscribers27 August 2026 — 6,387 subscribers31 August 2026 — 6,425 subscribers2 September 2026 — 6,542 subscribers7 August 20262 September 2026
11 measurements spanning 26 days, net +1,286. 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 5,063–6,735 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 15:366,542+117
31 Aug 2026, 00:476,425+38
27 Aug 2026, 21:286,387+58
24 Aug 2026, 14:086,329+204
20 Aug 2026, 18:486,125+389
17 Aug 2026, 15:575,736+115
14 Aug 2026, 01:585,621+259
10 Aug 2026, 16:315,362+81
8 Aug 2026, 00:445,281+25
7 Aug 2026, 16:015,256no change
7 Aug 2026, 15:505,256first reading

Engagement

12 posts held, back to 1 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
34.1%
avg views ÷ 6,542 subscribers
Avg views / post
2,230
6 posts measured
Reaction rate
6.79%
reactions ÷ views · ER floor
Posts in window
6
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 11 August 2026
Posts held12 (1 August 202611 August 2026)
Views total13,380
Reactions total909
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:25 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

2,304 reactions across 12 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53552514369784552442,304100.0%

Custom emoji. One row above is a 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 count beside it is 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 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 2,304 reactions 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 1 August 2026 to 11 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

11 Aug 2026, 18:32 UTC≈1,440 views58 reactionsread 12 August 2026
File

оставляю вам инструкцию для заказа товаров из Китая😍🔥⭐️ читайте комментарии! #полезное@daryaisnothere

custom 535525143697845524458

10 Aug 2026, 16:10 UTC≈2,410 views245 reactionsread 12 August 2026
Photo

Катя Романова сохранила мое видео, это можно считать успехом в блоггерской карьере?🥺

custom 5355251436978455244245

10 Aug 2026, 15:15 UTC≈2,460 views141 reactionsread 12 August 2026
Photo

🤩😍😚 спустя год сходила на тренировку по теннису! конечно, я уже все забыла, хочу снова попробовать заниматься с тренером, потому что очень мне нравится нагрузка на тело и формат тренировок😱 у нас был tennis date, и мы с Сережей даже ни разу не поссорились🤩😚

custom 5355251436978455244141

9 Aug 2026, 12:14 UTC≈2,720 views185 reactionsread 12 August 2026
Photo

молюсь на эти румяна💄🍎 если вы искали себе новые румяна, которые: а) отлично тушуются б) красивого оттенка в) не съедаются то я вам очень советую свои, они стоят 600р, я пользовалась 1.5 года и только вот вот снова обновила их 🤍🐆🧸 shu 355 оттенок делитесь своими бьюти находками, чтобы каждый нашел себе идеальную баночку! #бьюти@daryaisnothere

custom 5355251436978455244185

8 Aug 2026, 15:37 UTC≈3,000 views158 reactionsread 12 August 2026
Photo

ремонт 🕰️🧺 мы запланировали небольшой ремонт в квартире, после щенячества Тоши нужно стены привезти в порядок, двери, пол🌟🌟 сегодня ездили в магазин, покупали краску для стен, взяли очень красивый синий оттенок для коридора (скинула в комменты), делиться с вами процессом? и скоро засниму видео с покупками Таобао для дома, там постельное белье, фурнитура, декор и много всего🛏️🧴♟️ #покупки@daryaisnothere

custom 5355251436978455244158

7 Aug 2026, 08:10 UTC≈3,610 views254 reactionsread 12 August 2026
Photo

девчонки!🧘‍♀️😚 пока ничего не пощу, заболела, отлеживаюсь в кровати(👱‍♀️☕️

custom 5355251436978455244254

6 Aug 2026, 05:35 UTC≈2,650 views264 reactionsread 8 August 2026
Photo

наконец-то дома😚⭐️ как же я люблю возвращаться домой!

custom 5355251436978455244264

3 Aug 2026, 14:40 UTC≈3,800 views280 reactionsread 8 August 2026
Photo

🍟🪧🤍

custom 5355251436978455244280

2 Aug 2026, 07:03 UTC≈3,950 views240 reactionsread 8 August 2026

спасибо большое за 5000! это для меня огромное достижение, спасибо, что вы есть, что вы рядом 🩷 скоро в честь этого будет розыгрыш, хочу поблагодарить вас за все🌟

custom 5355251436978455244240

1 Aug 2026, 17:14 UTC≈4,470 views159 reactionsread 8 August 2026
Photo

center of attention 🍊🌟🌟 опробовала линейку cosrx с PDRN, и боже, у меня никогда не было настолько glass skin тоника, как этот🌟 с первого применения кожа сияет… жаль я не могу его привезти с собой домой, отдам Танюше, потому что в ручную кладь нельзя его… а все остальное с удовольствием буду использовать, все очень понравилось!🌟🌟🌕 как вам футболка?

custom 5355251436978455244159

1 Aug 2026, 06:46 UTC≈3,810 views198 reactionsread 8 August 2026
Photo

правило в отношениях🥰 мы с Сережей купероводы, поэтому в наших отношениях правило: видишь миник - покажи! вот такая коллекция с Минска у меня накопилась, очень нравится🤍

custom 5355251436978455244198

Showing the 12 most recent of 12 posts we hold for @daryaisnothere. 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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“дарья тут” (@daryaisnothere), 6,542 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/daryaisnothere.

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.