Personal blog — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
5 measurements spanning 50 days, net -1. 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 138–140 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
26 Sept 2026, 20:02
138
-1
4 Sept 2026, 05:55
139
-1
21 Aug 2026, 11:15
140
+1
8 Aug 2026, 22:31
139
no change
7 Aug 2026, 16:16
139
first reading
Engagement
5 posts held, back to 1 August 2026 — 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 5 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
35s
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
40 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 25.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5359453594326157840
10
25.0%
custom 5364120084883202415
9
22.5%
custom 5264977413464416973
5
12.5%
custom 5197257143689972462
4
10.0%
🙈
4
10.0%
💔
3
7.50%
😁
3
7.50%
custom 5262584313521660379
2
5.00%
Custom emoji. 5 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 5 of the 5 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 40 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 1 August 2026 to 8 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.
8 августа, суббота
🤩спойлер: я выжила
— супер статистика, вы просили, я делаю :)
🤩подъем: 5:50 утра
🤩выйти в 6:50 с мокрой головой: выполнено
🤩попытка взломать офисную дверь в 8 утра: 1 🤭
🤩праздников: 4 (2 проводила как аниматор, один из которых 4 часа, а 2 координировала как агент)
🤩поездки на такси: 6
🤩еда: кусочек тортика в 20:00 и в 22 булочка хихик
🤩красивые дома: много
🤩красивые закаты: 1
🤩потрясающее мыльное…
а если серьезно, то в сентябре в любом случае надо было бы переезжать
но я решила уже в начале июля на 3-4 месяца сначала вернуться домой, дабы замедлиться и сделать жесткую, так сказать, рекомпозицию жизни 🤭
— вот наблюдаю за изменениями во всех сферах жизни
например, август последний месяц провожу праздники и все, на этот раз точно перестаю и перехожу в другую деятельность 😄
Showing the 5 most recent of 5 posts we hold for @dashkaami. 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.
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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“Даш, что на этот раз?” (@dashkaami), 138 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/dashkaami.
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.
