Я обещала выслать вам фото с огоньками. Интересно, сможете ли вы угадать, есть ли у меня диплом/свидетельство строителя? 1。 да- ❤️ 2。 нет- 🔥
🔥16❤4

Channel
@randelina_run
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
190subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002486334173 |
|---|---|
| Type | Channel |
| Username | @randelina_run |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/randelina_run |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 22:04 | 190 | +2 |
| 14 Aug 2026, 10:35 | 188 | +2 |
| 8 Aug 2026, 12:16 | 186 | no change |
| 7 Aug 2026, 17:57 | 186 | first reading |
11 posts held, back to 10 June 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 pageof 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 11 posts for this entry, the most recent from 25 July 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.
124 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 58.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 73 | 58.9% | |
| ❤ | 29 | 23.4% | |
| 😍 | 11 | 8.87% | |
| 🍓 | 4 | 3.23% | |
| 👍 | 3 | 2.42% | |
| custom 5456140674028019486 | 2 | 1.61% | |
| 👌 | 1 | 0.806% | |
| 💘 | 1 | 0.806% |
Custom emoji. One 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 count beside it isTelegram’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 11 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 124reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 10 June 2026 to 25 July 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。 да- ❤️ 2。 нет- 🔥
🔥16❤4
Как- то так 🤔 Буду стараться сделать всё идеально. 🤩
🔥6custom 54561406740280194861
Выполняем задания 📋 7 🔥 и расскажу, что тут у нас интересного。
🔥12❤2
Тренька 🩶
🔥4❤1👌1👍1
Любовь — это, по-вашему, что? #пустота #вот #что #у #меня
❤12🔥4💘1
🚲 Много материала в голове, сьемок , проектов 🚲
🔥8❤3👍1custom 54561406740280194861
Ролик скоро ➡️ Выйдет …. Смотреть в инсте: https://www.instagram.com/randelina_run?igsh=MXBxcHRzZnM1Ynpkdw%3D%3D&utm_source=qr
🔥4❤3😍1
Собираете ли вы землянику? 🍓
😍8🍓4🔥1
Отдых на даче)))
🔥7❤4😍2
🎉🤩🖤Разрешите представить вам специального гостя нашего турнира-международного гроссмейстера, заслуженного мастера спорта России, трехкратную чемпионку Европы, двукратную чемпионку Мира и трехкратную Олимпийскую чемпионку Гунину Валентину Евгеньевну.🖤♟ Участки игры Государственная Дума Газпромбанк МИФИ Следственный комитет РФ Технополис Следственный департамент МВД Т. Д
🔥5👍1
Тепло💐
🔥6
Showing the 11 most recent of 11 posts we hold for @randelina_run. 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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“RANDELINA🤍” (@randelina_run), 190 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/randelina_run.
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.