Telegram RegisterThe public register of Telegram
Telegram profile photo for nastya

Channel

nastya

@nastyshka_kkk

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

16subscribers

-1 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-1002346370014
TypeChannel
Username@nastyshka_kkk
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live16 September 2026
Measurements held3
Confirmed unchanged4 times, most recently 16 September 2026
On Telegramt.me/nastyshka_kkk

Growth

161716.57 August 2026 — 17 subscribers11 August 2026 — 17 subscribers23 August 2026 — 16 subscribers7 August 202623 August 2026
3 measurements spanning 16 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 16–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 17:3516-1
11 Aug 2026, 20:0117no change
7 Aug 2026, 18:2017first reading

Engagement

12 posts held, back to 24 June 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
24s
Average length
8s

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

48 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 31.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52333825087536103701531.3%
1020.8%
custom 5283155506062451750816.7%
custom 537327606180507143048.33%
custom 547012810261085409748.33%
custom 523572880214275960536.25%
custom 531699833223147544236.25%
custom 521772048530697373012.08%

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 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 48 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 24 June 2026 to 4 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

4 Aug 2026, 09:48 UTC20 views4 reactionsread 11 August 2026
Video

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

custom 52831555060624517504

26 Jul 2026, 16:48 UTC32 views6 reactionsread 11 August 2026
Video

я на танцах миллион лет не была, считаю это лучшие движения из подвластных мне сейчас в этой хореографии 🤣🤣🤣 те самые 5 секунд, которые вообще можно выложить 😅😅😅 жду когда мои функциональные тренировки на танцах будут постепенно превращаться в танцевальные 😍😍 ох уж этот период адаптации 😁😁 благо людей было адекватное количество, так я на шаг ближе к цели 👀

custom 537327606180507143032custom 53169983322314754421

20 Jul 2026, 08:01 UTC42 views7 reactionsread 11 August 2026
Photo

📍покровский берег наконец-то получилось покайфовать на солнышке 😍😍 и побыть на пикнике 😎 ещё там много пространства для тех, кто хотел бы поиграть в гольф 👃

5custom 52831555060624517502

18 Jul 2026, 16:04 UTC46 views10 reactionsread 11 August 2026
Photo

какой выбираем? 🤩 💖 - первый 💓 - второй ❤️ - третий 🤩 - четвертый

custom 52333825087536103704custom 52831555060624517502custom 53169983322314754422custom 54701281026108540972

17 Jul 2026, 17:29 UTC41 views3 reactionsread 11 August 2026

ещё я очень жду, когда напечаются блокноты🙀 с внутренними страницами разобрались 👌 сейчас решается вопрос обложки 🫠 общим разным мнением, решили, что мне надо выложить сюда голосование 😅 скоро будет 👌

custom 54701281026108540972custom 52333825087536103701

17 Jul 2026, 17:25 UTC36 views2 reactionsread 11 August 2026

сходила на танцы 🤪 но даже для себя в этот раз не сняла 😅 летом все активно стали заниматься 😁😁 у Вас также?) я боялась пошевелиться от количества людей сегодня 🥹

custom 52177204853069737301custom 52357288021427596051

13 Jul 2026, 10:51 UTC55 views10 reactionsread 11 August 2026
Video message

Video message, posted without a caption

custom 523338250875361037010

13 Jul 2026, 10:50 UTC50 views6 reactionsread 11 August 2026

ну всё, наконец то могу считать себя блондинкой 😍😍😍 всю прошлую неделю уже жила с этим ощущением 🥰 ловлю такую гармонию с цветом 🥰 в текущем периоде жизни даже не вижу себя иначе 😅 ощущаю в этом цвете энергетику: ⏺️жизни ⏺️развития ⏺️движения ⏺️яркости 😁😁 такие вот дела

3custom 52357288021427596052custom 53732760618050714301

24 Jun 2026, 12:04 UTC72 viewsread 11 August 2026

готовлюсь к менторингу 🙂 казалось бы психологи, коучи просто ведут диалог, но сколько стоит за тем, чтобы вести эти диалоги 😁😁😅

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

“nastya” (@nastyshka_kkk), 16 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/nastyshka_kkk.

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.