💐⭐️
custom 54268490443139589275custom 53147539927759708034custom 53463316961427669332custom 52695988154547966031custom 53436091593235053971
Signed настя

Channel
@nastya_like13
On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
93subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002009932927 |
|---|---|
| Type | Channel |
| Username | @nastya_like13 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 28 August 2026 |
| On Telegram | t.me/nastya_like13 |
@nastya_like13 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 06:19 | 93 | +1 |
| 9 Aug 2026, 13:46 | 92 | no change |
| 8 Aug 2026, 09:32 | 92 | -1 |
| 7 Aug 2026, 17:39 | 93 | first reading |
4 posts held, back to 11 July 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 4 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 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.
57 reactions across 4 posts, in 11 distinct kinds. The most used accounts for 19.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5269598815454796603 | 11 | 19.3% | |
| custom 5251741290625796929 | 8 | 14.0% | |
| custom 5249308707048687264 | 7 | 12.3% | |
| custom 5426937026719019823 | 6 | 10.5% | |
| custom 5426849044313958927 | 5 | 8.77% | |
| custom 5278409133408671341 | 4 | 7.02% | |
| custom 5314753992775970803 | 4 | 7.02% | |
| custom 5375566928641287609 | 4 | 7.02% | |
| custom 5424950170552922458 | 4 | 7.02% | |
| custom 5343609159323505397 | 2 | 3.51% | |
| custom 5346331696142766933 | 2 | 3.51% |
Custom emoji. Every 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 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 4 of the 4 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 57 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 11 July 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 54268490443139589275custom 53147539927759708034custom 53463316961427669332custom 52695988154547966031custom 53436091593235053971
Signed настя
🫧🩰
custom 52517412906257969297custom 54269370267190198234custom 52493087070486872643custom 53755669286412876092custom 53436091593235053971
Signed настя
⭐️🌼
custom 52695988154547966036custom 53755669286412876092custom 52517412906257969291custom 54249501705529224581custom 54269370267190198231
Signed настя
🧋✨
custom 52493087070486872644custom 52695988154547966034custom 52784091334086713414custom 54249501705529224583custom 54269370267190198231
Signed настя
Showing the 4 most recent of 4 posts we hold for @nastya_like13. 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“настя🌸” (@nastya_like13), 93 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/nastya_like13.
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.