ΠΡΠΎ Π±ΡΠ» ΠΎΡΠ΅Π½Ρ Π³ΡΡΡΡΠ½ΡΠΉ ΡΠΈΠ»ΡΠΌ(
π2π1π’1
Signed .Β·:*π©πΆππππΆ*:Β·.

Channel
@nastya_20023
On this record: Topic Β· Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Cite this entry
98subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
| Telegram ID | -1001856668703 |
|---|---|
| Type | Channel |
| Username | @nastya_20023 |
| Created | 1 April 2023 β measured β cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/nastya_20023 |
Other / unclassifiable β 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 |
|---|---|---|
| 5 Oct 2026, 21:37 | 98 | -1 |
| 25 Sept 2026, 05:58 | 99 | -2 |
| 10 Sept 2026, 14:16 | 101 | -1 |
| 31 Aug 2026, 17:13 | 102 | +1 |
| 9 Aug 2026, 10:30 | 101 | no change |
| 7 Aug 2026, 19:56 | 101 | first reading |
5 posts held, back to 14 February 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 29 March 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.
49 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 26.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| customΒ 5316997365863828351 | 13 | 26.5% | |
| customΒ 5300889580646452682 | 10 | 20.4% | |
| β€ | 10 | 20.4% | |
| π | 7 | 14.3% | |
| customΒ 5300809844578603946 | 5 | 10.2% | |
| π | 2 | 4.08% | |
| customΒ 5312534452461654524 | 1 | 2.04% | |
| π’ | 1 | 2.04% |
Custom emoji. 4 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 49 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 14 February 2026 to 29 March 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.
ΠΡΠΎ Π±ΡΠ» ΠΎΡΠ΅Π½Ρ Π³ΡΡΡΡΠ½ΡΠΉ ΡΠΈΠ»ΡΠΌ(
π2π1π’1
Signed .Β·:*π©πΆππππΆ*:Β·.
Π‘ 8 ΠΌΠ°ΡΡΠ° Π²ΡΠ΅Ρ Π²ΡΠ΅Ρ !π
β€4customΒ 53008895806464526824customΒ 53169973658638283513π2customΒ 53008098445786039461
Signed .Β·:*π©πΆππππΆ*:Β·.
π
customΒ 53169973658638283515β€4customΒ 53008895806464526823π1customΒ 53125344524616545241
Signed .Β·:*π©πΆππππΆ*:Β·.
ΠΡ ΠΌΠΎΠΈππ₯Ή
customΒ 53008098445786039463β€2π1customΒ 53008895806464526821customΒ 53169973658638283511
Signed .Β·:*π©πΆππππΆ*:Β·.
π€
customΒ 53169973658638283514π2customΒ 53008895806464526822customΒ 53008098445786039461
Signed .Β·:*π©πΆππππΆ*:Β·.
Showing the 5 most recent of 5 posts we hold for @nastya_20023. 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 5 October 2026 β this entry's latest reading, not the date you are reading this.
ββ’πππ.π π‘ππ¦π βππ¦β (@nastya_20023), 98 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/nastya_20023.
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.