⛈️
🔥1
Signed Elena Burenkova

Channel
@lenor_USHASTIY
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
136subscribers
-2 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002645122010 |
|---|---|
| Type | Channel |
| Username | @lenor_USHASTIY |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/lenor_USHASTIY |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 01:21 | 136 | +1 |
| 10 Sept 2026, 05:39 | 135 | -1 |
| 17 Aug 2026, 19:24 | 136 | -2 |
| 9 Aug 2026, 18:00 | 138 | no change |
| 9 Aug 2026, 17:48 | 138 | first reading |
14 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 14 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 6 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 14 posts, in 3 distinct kinds. The most used accounts for 64.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 37 | 64.9% | |
| 🔥 | 15 | 26.3% | |
| ❤🔥 | 5 | 8.77% |
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 14 of the 14 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 14 most recent posts we hold, published 1 August 2026 to 8 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.
⛈️
🔥1
Signed Elena Burenkova
обожаю этот трек. Лет 10 или даже больше. Какие-то фантастические чувства вызывает во мне. Танцу это, конечно, не помогает. Но пусть) я тут теперь всем делиться решила (хочу потом отслеживать, как меняется мое движение)
🔥1
Signed Elena Burenkova
Решила попотеть еще больше
🔥1
Signed Elena Burenkova
Потные летние дни продолжаются 💦
❤5
Signed Elena Burenkova
Чмок 💋
❤5
Signed Elena Burenkova
Ностальгирую по Китаю
❤6
Signed Elena Burenkova
Кажется, на 4 день адской жары я адаптировалась (ну и без температуры легче двигаться😸) и мне даже нравится сегодня на улице. Дома, в транспорте и в зале по-прежнему находиться тяжеловато. Сегодня 2 технических и хорео класса и постановка - дай мне сил, лунная призма.
❤4
Signed Elena Burenkova
Человек все отработал и отрепетировал и выжил. Человек идет на свидание в кино🍿
❤8
Signed Elena Burenkova
и кондиционеров нет. Господи, я хочу переехать 😹😹😹
🔥3
Signed Elena Burenkova
я ненавижу жару и ненавижу болеть (ну там вряд ли кто-то меня не поддержит) памагити
🔥6
Signed Elena Burenkova
Video message, posted without a caption
🔥3
Signed Elena Burenkova
🌶️
❤🔥5
Signed Elena Burenkova
Showing the 12 most recent of 14 posts we hold for @lenor_USHASTIY. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“просто нравятся круж⭕️чки” (@lenor_USHASTIY), 136 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/lenor_USHASTIY.
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.