Channel
@MARIUPOL20222022
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
274subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001628887613 |
|---|---|
| Type | Channel |
| Username | @MARIUPOL20222022 |
| Created | 3 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/MARIUPOL20222022 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 06:40 | 274 | -2 |
| 6 Sept 2026, 08:21 | 276 | -1 |
| 28 Aug 2026, 04:08 | 277 | -1 |
| 8 Aug 2026, 08:34 | 278 | no change |
| 7 Aug 2026, 19:54 | 278 | first reading |
15 posts held, back to 3 March 2022 — 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 15 posts for this entry, the most recent from 1 August 2024. 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.
214 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 46.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 100 | 46.7% | |
| 😢 | 76 | 35.5% | |
| 😱 | 11 | 5.14% | |
| 👎 | 9 | 4.21% | |
| 🤔 | 6 | 2.80% | |
| 🤯 | 4 | 1.87% | |
| ❤ | 3 | 1.40% | |
| 👏 | 3 | 1.40% | |
| 🔥 | 2 | 0.935% |
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 10 of the 15 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 214 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 3 March 2022 to 1 August 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Video, posted without a caption
😢31👍23🤯3❤1
Video, posted without a caption
😢38👍15🤔6👏3😱2
Photo, posted without a caption
👍16😱4
Після вчорашнього бомбардування Маріуполя за даними поліції вже відомо про загибель п’ятьох осіб, з яких двоє дітей. Велика кількість поранено.
👍7😢7❤1😱1
https://t.me/MARIUPOL202220222
👍4👎1🔥1😱1
Video, posted without a caption
👍6😱3
Эвакуированные. Сартана
👍1
Showing the 12 most recent of 15 posts we hold for @MARIUPOL20222022. 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Мариуполь. Левый. Восточный.” (@MARIUPOL20222022), 274 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/MARIUPOL20222022.
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.