Channel
@PERUN_42
On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,805subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002020727021 |
|---|---|
| Type | Channel |
| Username | @PERUN_42 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/PERUN_42 |
This channel’s posts match, word for word or near enough, posts on 376 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
326 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:53 | 1,805 | +1 |
| 10 Aug 2026, 00:42 | 1,804 | +1 |
| 6 Aug 2026, 19:10 | 1,803 | -1 |
| 6 Aug 2026, 06:51 | 1,804 | no change |
| 6 Aug 2026, 00:48 | 1,804 | first reading |
19 posts held, back to 2 July 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 2 pagesof Telegram’s post history, 20 posts per page.
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 6 August 2026 |
|---|---|
| Posts held | 19 (2 July 2026 – 6 August 2026) |
| Views total | 9,133 |
| Reactions total | 427 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:29 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.
Measured directly from 17 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.
838 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 69.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 582 | 69.5% | |
| ❤ | 170 | 20.3% | |
| 👍 | 75 | 8.95% | |
| 👏 | 9 | 1.07% | |
| 🤔 | 1 | 0.119% | |
| 🤝 | 1 | 0.119% |
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 19 of the 19 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 838reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 2 July 2026 to 6 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.
Єдиний зліт у карʼєрі окупанта може бути тільки внаслідок розриву FPV-дрона🔪 На Новопавлівському напрямку росіянин надихнувся прикладом своїх попередників і також спробував стрибнути у висоту. Вийшло просто жахливо. А щоб більше росіян навчилось літати — закиньте на Русоріз!
❤17🔥12
Цей кацап явно вивчав правила пожежної безпеки, але все наплутав. росіянин вирішив спробувати покачатися по землі перед ураженням операторами підрозділу Перун, натомість після — коли загорівся, з якоїсь причини завмер🤔 Ну головне, що здох. А щоб здихали й інші — закиньте на Русоріз!
🔥22❤6👍1
Професіоналізм, що наближає до головної мети.
❤22👍10
Один з бойових командирів батальйону безпілотних систем "Перун" 42 ОМБр в ефірі "Суспільне Новини"
❤22🔥9👍2
Картинка з FPV, звісно, лажа, але ж зате який результат😍 Росіянин пережив усі стадії прийняття перед тим, як нарешті здохнути від дрону операторів Перун. А щоб картинка була гарною і звʼязок не міг заглушити жоден РЕБ, закиньте на Digital Русоріз!
🔥31❤5👍1
«Гдє боєпріпаси?» На Новопавлівському напрямку оператори Перун знищили дуже жирну позицію російських артилеристів💥 Окрім того, вашими дронами виявили і знищили з десяток замаскованих гармат та окупантів у полі. Кожна знищена гармата чи БК до неї — це врятовані життя наших бійців! Допоможіть рятувати життя!
🔥35❤10👍3
На Новопавлівському напрямку свої правила. Оператори Перун вирізають російський транспорт та самих росіян, які назавжди залишаться гнити в землі💥 Допоможіть скоротити популяцію кацапів! Закиньте на Русоріз!
❤17🔥13👍3
Ворог досі час від часу використовує Starlink, який тим чи іншим способом опиняється в нього. Наприклад, на Новопавлівському напрямку оператори Перун 42-ї ОМБр спалили російський НРК із цією антеною💥 До того ж ще й знищили рідкісний танк, який кацапи марно ховали в посадці🔫 Допоможіть спалити все російське! Закиньте на Русоріз!
🔥25❤7👍1
Еволюція - це домінанта якості над кількістю. Доведено Перуном.
🔥48❤9👍2
На дикому сході росіяни не мають шансів вижити. Не дуже розумний кацап спробував вступити у двобій з вашим дроном під керуванням операторів Перун — і програв🔪 Окупанти мають дохнути у муках! Задля цього задонатьте на Русоріз!
🔥40👍7❤2
Робота професійної команди в поєднанні з нульовою толерантністю до ворога. Ми не просто спостерігаємо, ми діємо. Вчасно, влучно, ефективно. Перун.
🔥31❤10👍4
На Новопавлівському напрямку оператори Перун влаштовують двіжуху для російських окупантів. -9 кацапів завдяки вашим дронам😱 Допоможіть творити русоріз! Долучайтеся!
🔥43👍9👏4❤1🤝1
Showing the 12 most recent of 19 posts we hold for @PERUN_42. 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 — 32,728 of 1,169,250entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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.
“ББС ⚡️ Перун ⚡️ 42 ОМБР” (@PERUN_42), 1,805 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/PERUN_42.
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.