самый ожидаемый ребрендинг;)
💘8custom 53799591254069351535🍾3🤯1custom 52534888312141579211

Channel
@sashaenkaa
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
139subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002040390399 |
|---|---|
| Type | Channel |
| Username | @sashaenkaa |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/sashaenkaa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 03:44 | 139 | +2 |
| 8 Aug 2026, 23:17 | 137 | no change |
| 7 Aug 2026, 16:02 | 137 | first reading |
12 posts held, back to 9 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 12 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
90 reactions across 11 posts, in 16 distinct kinds. The most used accounts for 32.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💘 | 29 | 32.2% | |
| custom 5332504864977094890 | 8 | 8.89% | |
| ❤ | 8 | 8.89% | |
| custom 5379959125406935153 | 7 | 7.78% | |
| 🍓 | 7 | 7.78% | |
| custom 5208620394499569462 | 5 | 5.56% | |
| custom 5332490618570571640 | 5 | 5.56% | |
| 🎉 | 5 | 5.56% | |
| custom 5253488831214157921 | 3 | 3.33% | |
| 🌚 | 3 | 3.33% | |
| 🍾 | 3 | 3.33% | |
| custom 5363949149479793729 | 2 | 2.22% | |
| custom 5458769644984747638 | 2 | 2.22% | |
| custom 5458703811726035124 | 1 | 1.11% | |
| 🤝 | 1 | 1.11% | |
| 🤯 | 1 | 1.11% |
Custom emoji. 8 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 11 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 90 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 9 July 2026 to 3 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.
самый ожидаемый ребрендинг;)
💘8custom 53799591254069351535🍾3🤯1custom 52534888312141579211
Channel name was changed to «саша_степанова»
бабушкин первый деньродженьщенский сиксевен
💘5❤4🍓4custom 52086203944995694621
Posted without readable text
custom 52534888312141579212custom 53325048649770948901custom 54587038117260351241
мы ждали этот альбом всем селом
💘5custom 53324906185705716401custom 53799591254069351531
ЭЙФОРИЯ ДЛЯ ТЕБЯ И ДЛЯ МЕНЯЯЯЯЯЯЯ
custom 54587696449847476382custom 53325048649770948901custom 53799591254069351531
мне очень хорошо сейчас
🍓3❤2💘2custom 53324906185705716401
Video message, posted without a caption
💘3
оцениваем подгон пока что выглядит хорошо
custom 53324906185705716403💘1custom 52086203944995694621
тупа я
🌚3custom 53325048649770948902custom 53639491494797937292💘1🤝1
Video message, posted without a caption
🎉5❤2
🫶🫶🫶
💘4custom 53325048649770948904custom 52086203944995694623
Showing the 12 most recent of 12 posts we hold for @sashaenkaa. 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“саша_степанова” (@sashaenkaa), 139 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/sashaenkaa.
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.