Быть воином, жить вечно...
❤20custom 54741880364114972608custom 54742060237345360563

Channel
@fedorovskiyceprey
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
285subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002051721238 |
|---|---|
| Type | Channel |
| Username | @fedorovskiyceprey |
| 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 | 13 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 4 times, most recently 13 September 2026 |
| On Telegram | t.me/fedorovskiyceprey |
Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 08:14 | 285 | -2 |
| 15 Aug 2026, 08:03 | 287 | -1 |
| 6 Aug 2026, 23:03 | 288 | no change |
| 6 Aug 2026, 01:36 | 288 | first reading |
18 posts held, back to 3 January 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 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 18 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
304 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 54.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 166 | 54.6% | |
| 🔥 | 79 | 26.0% | |
| 👍 | 27 | 8.88% | |
| custom 5274014303828057007 | 9 | 2.96% | |
| custom 5474188036411497260 | 8 | 2.63% | |
| 😎 | 7 | 2.30% | |
| custom 5474206023734536056 | 6 | 1.97% | |
| custom 5454080111928184554 | 2 | 0.658% |
Custom emoji. 4 of the rows above are 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 counts beside them are Telegram’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 18 of the 18 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 304 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 3 January 2026 to 4 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.
Быть воином, жить вечно...
❤20custom 54741880364114972608custom 54742060237345360563
Что люди думаю когда по ним ведется огонь? Я думал за своих товарищей что бы ни кого не ранило. И ждал приказа командира группы.
🔥16❤5
Раненый в левую ногу и левую руку, пошел чистить дорогу домой для эвакуации нашей группы. Так как обстановка на данном участке фронта была очень напряженная командиром было принято решение не запрашивать эвакуацию в эфире а произвести ее своими силами на двух автомобилях на которых приехали на задачу. Общими усилиями выкатились без потерь но не без приключений без них мы никуда.
🔥9❤8👍2
Мы смотрели смерти в глаза, но она отвернулась от нас, значит еще не время. Быть воином значит жить вечно… Группа «АИДА» навсегда
❤26🔥11custom 52740143038280570079custom 54742060237345360563
Лучшая работа в мире
❤15
На гражданку накинули брони и поехали)
🔥25👍8❤4
Актуальные часы в данное время года, и времени) советую к приобретению) и кстати не дешевые)
😎7
🇷🇺 - Все что нас не убивает, делает нас сильнее. - пытался подбодрить меня мой разведчик. Я холодно улыбнулся и посмотрел на него: - Чья эта фраза, знаешь? - Не знаю. Но смысл понятен. - И в чем же он? - Испытания нас закаляют и если мы не сломались, то становимся крепче. Помолчав несколько секунд, я продолжил: - Эта фраза принадлежит Ницше. Человеку, который очень долго всматривался в бездну. В его трактате "по ту с…
❤14
🇷🇺 Спасение смежников с ВДВ отрядом "Д" группы Аида СпН "Ахмат" и эвакуация в госпиталь. Погибшему - вечной жизни. Зов Аида в ТГ Зов Аида в Мах
👍7❤3
🇷🇺 Отряд "Д". Сумская область. Зов Аида в ТГ Зов Аида в Мах
🔥3
Вот такие виды у нас на позициях. Жизнь обретает больший смысл тогда когда за ней кто то охотится. Всем мира. Враг будет разбит.
❤13
Скоро чьи то жопки сгорят) земля бетоном свинки
👍6
Showing the 12 most recent of 18 posts we hold for @fedorovskiyceprey. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“soldier's everyday life” (@fedorovskiyceprey), 285 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/fedorovskiyceprey.
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.