Ukrainian UAV strike on the Port of Sochi, Russia (03.09.2026) https://redd.it/1w626xh @r_combatfootage

Channel
/r/CombatFootage
@r_combatfootage
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry
24,956subscribers
+314 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001430580846 |
|---|---|
| Type | Channel |
| Username | @r_combatfootage |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/r_combatfootage |
Topic
International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:37 | 24,956 | +19 |
| 16 Sept 2026, 05:55 | 24,937 | +14 |
| 14 Sept 2026, 15:36 | 24,923 | +34 |
| 13 Sept 2026, 02:55 | 24,889 | +20 |
| 11 Sept 2026, 03:37 | 24,869 | +38 |
| 8 Sept 2026, 05:17 | 24,831 | +18 |
| 4 Sept 2026, 22:58 | 24,813 | +11 |
| 3 Sept 2026, 09:07 | 24,802 | -5 |
| 2 Sept 2026, 01:14 | 24,807 | +11 |
| 1 Sept 2026, 02:27 | 24,796 | +5 |
| 31 Aug 2026, 05:17 | 24,791 | +9 |
| 30 Aug 2026, 07:28 | 24,782 | +15 |
| 29 Aug 2026, 07:57 | 24,767 | +6 |
| 28 Aug 2026, 09:12 | 24,761 | +12 |
| 27 Aug 2026, 09:58 | 24,749 | +4 |
| 26 Aug 2026, 11:55 | 24,745 | +5 |
| 25 Aug 2026, 12:32 | 24,740 | -8 |
| 24 Aug 2026, 14:34 | 24,748 | +10 |
| 23 Aug 2026, 01:29 | 24,738 | -9 |
| 21 Aug 2026, 13:02 | 24,747 | first reading |
Engagement
282 posts held, back to 3 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 58 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.88%
- avg views ÷ 24,956 subscribers
- Avg views / post
- 969
- 103 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 103
- of 282 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 282 (3 August 2026 – 3 September 2026) |
| Views total | 99,778 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:37 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 1h 18m
- Average length
- 18s
Measured directly from 266 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.
Recent posts
Novopavlivka: Ukraine's 42nd Mechanized Brigade "Perun" Battalion drone pilots repelled Russian infantry during night strikes. September 2, 2026 https://redd.it/1w5plbr @r_combatfootage
UA 71st Airmobile Brigade "Huntsmen" ground drone outmaneuvered an attacking Russian FPV drone, reversing at the last second. Posted September 2, 2026 https://redd.it/1w5ugn7 @r_combatfootage
Ukrainian reconnaissance and sabotage group (DRG) sets up an ambush. Confirming enemy location with UAV. As a result, 3 Russian soldiers were killed, confirmed by UAV. Sumy region https://redd.it/1w5k59y @r_combatfootage
The 59th Separate Assault Battalion of the Unmanned Systems Forces of Ukraine (SIGNUM) strikes Russian vehicles in occupied Vasylivka and Horlivka, both over 30 km from the front lines. August 2026 https://redd.it/1w5mc9n @r_combatfootage
SBU operator firing at HUR personel in Kiyv after the arrest of Stepan KAPLUNOV https://redd.it/1w5n5za @r_combatfootage
Ukrainian HIMARS GMLRS strike hit a group of Russian assault troops in the Kostiantynivka direction. Four Russian soldiers were killed and another four were wounded. Published 1st Sept 2026 https://redd.it/1w5kmbu @r_combatfootage
Cockpit cam of Ukrainian MiG-29MU1 destroying Russian drone at close range & low altitude using R-60 missile https://redd.it/1w5kewi @r_combatfootage
Ukraine's 43rd Mechanized Brigade "Nebesna Mara" helped repel a rare Russian mechanized attack in the Kupyansk direction, burning enemy tanks and armored vehicles using FPV strike drones. Posted August 18, 2026 https://redd.it/1w5fv3q @r_combatfootage
Multiple Russian targets hit by the Defense Forces of Ukraine, including sanctioned cargo vessel ALFA-1 in occupied Mariupol. August 2026 https://redd.it/1w5ez3e @r_combatfootage
The 9th Separate Unmanned Systems Brigade of Ukraine eliminates Russian infiltrators in northern Kivsharivka, Kharkhiv Oblast, August 2026 https://redd.it/1w5efh0 @r_combatfootage
Ukrainian MiG-29 hits Russian troop concentration with a precision-guided munition — E-105 highway east of Oktyabrskiy, Belgorod Oblast, August 2026 https://redd.it/1w5dssv @r_combatfootage
Showing the 12 most recent of 282 posts we hold for @r_combatfootage. 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.
Mentions
Named by 8 registered channels — 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.
@IngressPrimeFeedback · 321 postOctober Strike
@OctoberStrike · 71 postr/badcode
@r_badcode · 391 postr/Furrypasta
@r_furrypasta · 301 postr/GharKeKalesh
@r_gharkekalesh · 761 postI'm going to hell for this
@r_imgoingtohellforthis · 1261 post@r_invites
@r_invites · 1891 postRussianIsSoHard
@RussianIsSoHard · 61 post
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@war_noir · 53,378#1
@ukrainosrusijoskaras · 10,465#2
@intelslava · 390,719#3
@gimbaled · 44,837#4
@CombatFootageBackup · 4,000#5
@ourwars · 6,941#6
@warinukraineua · 20,916#7
@rnintel · 170,796#8
@tglobaleye · 11,276#9
@UkraineInAction · 12,193#10
@warfootage1 · 11,485#11
@warriorsukrainian · 40,875#12
@warleaks11 · 68,456#13
@most_recent_ukrainian_updates · 13,821#14
@pilotblog · 196,203#15
@BellumActaNews · 114,627#16
@Israel_Middle_East_Insight · 4,740#17
@information_about_Ukraine · 4,896#18
@CIG_telegram · 115,452#19
@osint_69 · 8,709#20
@skyoverukraine · 7,264#21
@EdgeProduction · 713#22
@NewsWorld_23 · 13,750#23
@middle_east_spectator · 404,186#24
@ClashReport · 109,374#25
@DDGeopolitics · 191,128#26
@UkraineWarPosts · 18,794#27
@Damhistory · 21,346#28
@ourwarstoday · 47,079#29
@frontier_conflict1 · 25,534#30
@worldnewschannel3 · 1,779#31
@A3OB_LATAM_OFICIAL · 3,971#32
@warmonitors · 152,372#33
@ukraine_dead_russian · 8,280#34
@Jimmyhillreports · 2,931#35
@noel_reports · 34,686#36
@AssyriaNewsNetwork · 8,728#37
@MorgothsDarkness · 1,280#38
@Slavyangrad · 113,042#39
@baronsandbadlands · 3,761#40
@Ukrainewarcombatdaily · 783#41
@liveukraine_media · 42,552#42
@entre_guerras · 136,560#43
@War_Drone · 970#44
@specialforcesZ · 1,344#45
@United24media · 69,089#46
@Voyna18 · 197,990#47
@ukraine_context · 93,532#48
@WarArchive_ua · 50,547#49
@exilenova_plus · 287,167#50
@MiliTJournal · 11,271#51
@ab3army · 277,454#52
@karymat · 73,150#53
@fortresskyiv · 6,920#54
@khornegroup · 18,632#55
@SVOI_PERIMETR_Z · 3,987#56
@vatnikcope · 5,259#57
@VenezuelaNetwork · 12,141#58
@lost_warinua · 18,997#59
Read from Telegram’s recommendation API, most recently 15 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@gimbaled · 44,837
Telegram ranks this channel #1 of 46 here — alongside 45 others — read 3 September 2026
@warleaks11 · 68,456
Telegram ranks this channel #23 of 74 here — alongside 73 others — read 27 August 2026
@contlictobservers · 45,634
Telegram ranks this channel #41 of 71 here — alongside 70 others — read 27 August 2026
@frontier_conflict1 · 25,534
Telegram ranks this channel #42 of 74 here — alongside 73 others — read 14 September 2026
@warvideos18 · 43,573
Telegram ranks this channel #52 of 76 here — alongside 75 others — read 28 August 2026
@warriorsukrainian · 40,875
Telegram ranks this channel #56 of 71 here — alongside 70 others — read 29 August 2026
@ourwarstoday · 47,079
Telegram ranks this channel #69 of 81 here — alongside 80 others — read 26 August 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Referenced elsewhere
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
“…February 2024|website=[[Ukrainska Pravda]]}}{{cite web |url=https://t.me/r_combatfootage/32676 |title=Another angle of the attack and crash of the…”
read 13 September 2026
Cite this entry
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“/r/CombatFootage” (@r_combatfootage), 24,956 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/r_combatfootage.
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.