Channel
@nastyushkas_tales
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
432subscribers
-10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001615964051 |
|---|---|
| Type | Channel |
| Username | @nastyushkas_tales |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/nastyushkas_tales |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 15:57 | 432 | -6 |
| 9 Sept 2026, 10:20 | 438 | +1 |
| 1 Sept 2026, 01:18 | 437 | -2 |
| 24 Aug 2026, 20:34 | 439 | -1 |
| 16 Aug 2026, 06:13 | 440 | -2 |
| 8 Aug 2026, 05:05 | 442 | no change |
| 7 Aug 2026, 12:59 | 442 | first reading |
8 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 8 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
308 reactions across 8 posts, in 9 distinct kinds. The most used accounts for 25.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5444938926873672521 | 79 | 25.6% | |
| custom 5336862143658617714 | 76 | 24.7% | |
| custom 5210945135742841384 | 60 | 19.5% | |
| custom 5251291616139836791 | 22 | 7.14% | |
| custom 5341704951213089889 | 18 | 5.84% | |
| custom 5341562293874347530 | 17 | 5.52% | |
| ❤ | 16 | 5.19% | |
| custom 5456553111147542783 | 15 | 4.87% | |
| 💔 | 5 | 1.62% |
Custom emoji. 7 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 8 of the 8 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 308 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 1 August 2026 to 7 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.
— 🤍🏐✨ где бы я ни была, этот вид спорта всегда будет рядышком со мной! Пс, друзья отказались делать селфи, но в следующий раз пообещали сделать много контента!!! Сегодня было много красивых сейвов от самых бесполезных игроков 😛
custom 52109451357428413842custom 53417049512130898892custom 54449389268736725212
🐕 oups! 🐕 нас засекли, при съемке шладкой булочки 🫳🐕
custom 52109451357428413846custom 53368621436586177144custom 54449389268736725213❤1
Гостили у родных тут денечек 🏠 Хочется приезжать, как можно чаще, тем более моему ушастому компаньону, очень понравилось исследовать огромные территории ;) пс, а ещё портить грядки, но мы считаем это, конечно же, не правдой, потому что бабуля следит за моими сказками 🤭 — вот такие дела!
custom 54449389268736725214custom 53368621436586177143custom 53415622938743475303❤2
Я так хочу, чтобы ☀️☀️ не кончалось!
custom 544493892687367252114custom 521094513574284138413custom 533686214365861771413❤4
И почему понедельники такие тяжёлые 🐕 За целый день только нашлось времечко сесть, да выложить свои photo-dumps, но вот только время уже спать пора! — но я чувствую, что вот уже скоро этот канал снова наполниться моей любимой эрой: путешествия – on ✅💼 Надеюсь, что твой понедельник прошел ярко⭐️⭐️⭐️ расскажи как!
custom 534170495121308988916custom 545655311114754278315custom 534156229387434753014❤3custom 53368621436586177141
🐕 🔸🔸 🐕 — долго же я выбирала кадры 🔠🔠🔠🔠🎨🎨🎨 🎨🎨🎨 🎨🎨🎨 А потом поняла, что главное достижение — это то, что мы, наконец-таки, решились на +1 булочку [читайте как сосиску] в нашей семье! 🐕 Весь июль, мы старались сделать так, чтобы ему было максимально комфортно и хорошо у нас в домике: научились вставать на утренние прогулки & собираться за пару секунд, покупали [и в…
custom 521094513574284138413custom 533686214365861771413custom 544493892687367252111💔5❤3
Раз уж я решила вернуться, то поделюсь своими сказками 📸 J u n e ▫️▫️▫️▫️: июнь был наполнен множеством путешествий! 🐸 самыми тёплыми и искренними посиделками с друзьями&семьей и ощущением, что июнь’27 будет незабываемым! — узнаем в следующей серии [году] 🐶🐕 Ну, а про путешествия расскажу, конечно же ⭐️⭐️ #какаяесть_N
custom 544493892687367252125custom 533686214365861771424custom 525129161613983679122❤3custom 52109451357428413841
Последний месяц ☀️☀️☀️ желаю тебе провести на море 🤩🤩🤩
custom 521094513574284138425custom 544493892687367252120custom 533686214365861771418
Showing the 8 most recent of 8 posts we hold for @nastyushkas_tales. 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Настюшкины сказки ✨” (@nastyushkas_tales), 432 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/nastyushkas_tales.
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.