Channel
@ukrainabackup
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
41subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001734649952 |
|---|---|
| Type | Channel |
| Username | @ukrainabackup |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/ukrainabackup |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:52 | 41 | no change |
| 11 Aug 2026, 15:17 | 41 | first reading |
20 posts held, back to 8 March 2024 — 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 20 posts for this entry, the most recent from 20 February 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 18 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.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 18 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
⚡ЗНИЩЕНО ворожий ЗРК «БУК» на Запорізькому напрямку ⚫ Оператори 3-го окремого полку ССО під час розвідувальних дій на Запорізькому напрямку виявили зенітний ракетний комплекс «БУК» противника. ⚫ Оператори навели на ворожу ціль вогонь HIMARS ракетно-артилерійського підрозділу Сил оборони.
Ukraine's Special Operation Forces asked for Support - and we want to help!
«Небесна кара»: Злата Огнєвіч заспівала про дрони СБУ, які щодня несуть з неба справедливе покарання окупантам🔥
Мій колега зробив це відео, але тікток його заблокував. Він дуже хоче поділитися цим відео зі всіма українцями.
I wanted to create a victory hype song for the brave soldiers of Ukraine and pay my respects for their defence of the free world. I collaborated with Ukrainians to make this!
Піша прогулянка Хрещатиком
The Making-Of "St. Javelin" - Protector of Ukraine!
A russian occupier is happy about ruining and capturing Avdiivka because now he can loot the belongings of Ukrainian civilians killed by russia.
Russian Iskander missile hits Mykolaiv, Ukraine / 17.03.2024
A Ukrainian missile attack killed at least two people in western Russia and a separate drone strike set an oil refinery ablaze on the second day of an election that President Vladimir Putin has accused Kyiv of trying to disrupt
RU POV: Moscow girl poured dye into ballot box
Showing the 12 most recent of 20 posts we hold for @ukrainabackup. 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.
Citation-graph rank — 1,287,167 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“r/Ukraina Subreddit - Ucraina / Ukraine / Украина / україна / Ucrania Reddit Backup Telegram Channel by RTP” (@ukrainabackup), 41 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ukrainabackup.
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.