Telegram RegisterThe public register of Telegram
Telegram profile photo for Рейд в аду

Channel

Рейд в аду

@reidvady

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

171subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002290886424
TypeChannel
Username@reidvady
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 30 August 2026
On Telegramt.me/reidvady

Growth

1711731727 August 2026 — 171 subscribers8 August 2026 — 171 subscribers16 August 2026 — 173 subscribers24 August 2026 — 171 subscribers7 August 202624 August 2026
4 measurements spanning 17 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 171–173 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 12:53171-2
16 Aug 2026, 14:27173+2
8 Aug 2026, 14:46171no change
7 Aug 2026, 14:05171first reading

Engagement

20 posts held, back to 1 August 2025the 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 1 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 06s
Average length
49s

Measured directly from 5 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.

Reaction mix

221 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 52.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥11652.5%
👍5926.7%
3917.6%
🆒31.36%
👏31.36%
😁10.452%

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 20 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 221reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 1 August 2025 to 1 June 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.

Recent posts

1 Jun 2026, 14:33 UTC319 views10 reactionsread 8 August 2026
Photo

Photo, posted without a caption

👍5🔥4😁1

1 Jun 2026, 09:31 UTC258 views11 reactionsread 8 August 2026

https://vkvideo.ru/video707102_456240375?list=9a55a689430b2fbcc3

👍5🔥42

24 May 2026, 19:00 UTC407 views7 reactionsread 8 August 2026
Video

В данном видео мы видим работу по цели размером с буханку хлеба, на дистанции 400 метров(!), было 6 попаданий. Это не позёрство и не хвастовство - это демонстрация возможностей обученного стрелка и подготовленного комплекса. Важно: Обучение личного состава МОГ набранных из резервистов, является сейчас точкой предкновения - программ обучения нет, патронов дают ничтожно мало, инструкторов нет, понимания необходимости о

👍51🔥1

23 May 2026, 13:33 UTC365 views23 reactionsread 8 August 2026
Video

Video, posted without a caption

👍163👏3🔥1

16 May 2026, 09:32 UTC429 views31 reactionsread 8 August 2026
Video

Video, posted without a caption

🔥185👍5🆒3

14 May 2026, 14:44 UTC393 views7 reactionsread 8 August 2026

Итак, уважаемые участники, мы встречаемся с вами на Ранчо - 16 мая в 8:00. Регистрируемся и проводим, ганчек и жеребьевку, а затем взвешивание в снаряге и без, в 8:30 прилетает вертолёт; 8:45 брифинг - оглашение легенды и порядок прохождения матча; 9:00 первый старт тактических пар. 13:00 Обед, затем старт одиночек. 17:00 Дуэль. Весь день действует упражнение "Неваляшка", как для пар так и для одиночек. Брифинг: По с

6🔥1

5 May 2026, 01:24 UTC426 views13 reactionsread 8 August 2026

Уважаемые друзья, близится пятый "Рейд", мы активно готовимся и хотим увидеть вас на нашем мероприятии! Прошу регистрироваться активнее, ваша регистрация подсказывает нам, что наши усилия не напрасны! Что мы не зря вообще затеяли строить Полигон. Нам нужно знать сколько купить гранат, кубков, дымов, порций еды, пригласить специалистов по дронам, а им взять с собой батареек и т.д. Неужели вам не нравиться всё то что м

13

28 Apr 2026, 12:58 UTC499 views10 reactionsread 8 August 2026
Video

Видео от наших друзей и партнёров, а так соорганизаторов - "Академии тактики". Люди собравшие потрясающую команду, способную за пару дней сотворить безумие на стрельбище!! Какие же красавцы!!

🔥6👍4

22 Apr 2026, 14:28 UTC487 views14 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥10👍31

22 Apr 2026, 14:27 UTC453 views17 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥12👍41

22 Apr 2026, 14:27 UTC406 views19 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥14👍41

19 Apr 2026, 05:17 UTC536 views1 reactionsread 8 August 2026

Доброе утро, уважаемые стрелки, регистрация на матч продолжается! Мы активно готовимся - закупаем пиротехнику, завозим покрышки и очищаем окопы, согласовываем места посадки и маршруты пролета вертолетов, заключаем договора со скорой, считаем как и где вас вкусно покормить. Разрабатываем медали и награды для этапов, консультируемся со специалистами и закупаем мишени. А пока давайте обсудим, что вас останавливает от ре

👍1

Showing the 12 most recent of 20 posts we hold for @reidvady. 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.

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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“Рейд в аду” (@reidvady), 171 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/reidvady.

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.