Telegram RegisterThe public register of Telegram
Telegram profile photo for Детектор SPV

Channel

Детектор SPV

@detektor_spv

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

363subscribers

+36 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003923419815
TypeChannel
Username@detektor_spv
CreatedBetween 1 April 2026 and 18 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/detektor_spv

Growth

3273633456 August 2026 — 327 subscribers6 August 2026 — 329 subscribers6 August 2026 — 329 subscribers13 August 2026 — 363 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +36. 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 322–368 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:48363+34
6 Aug 2026, 21:47329no change
6 Aug 2026, 09:40329+2
6 Aug 2026, 03:06327first reading

Engagement

16 posts held, back to 18 July 2026the 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.

ERR · 30 days
425.7%
avg views ÷ 363 subscribers
Avg views / post
1,550
16 posts measured
Reaction rate
0.137%
reactions ÷ views · ER floor
Posts in window
16
of 16 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. It is computed over the 8 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held16 (18 July 20266 August 2026)
Views total24,725
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 21:47 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.

Reaction mix

19 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 36.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
736.8%
👍421.1%
🤔315.8%
💯210.5%
15.26%
👌15.26%
👏15.26%

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

Measured over the 16 most recent posts we hold, published 18 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.

Recent posts

6 Aug 2026, 10:04 UTC≈1,510 viewsread 6 August 2026
Photo

📦 Аксессуар для детектора SPV — крепёжные стаканы Коллеги, для тех, кто использует детектор в движении или на различных поверхностях, мы подготовили варианты крепёжных стаканов. Как это выглядит: Детектор устанавливается в стакан и фиксируется защёлкой-прищепкой, которая надёжно удерживает его внутри. Стакан исключает случайное выпадение прибора даже при активном движении, тряске или работе в автомобиле. Доступ

5 Aug 2026, 16:49 UTC≈1,250 views0 reactionsread 6 August 2026
Photo

📡 Перехват на 5715 МГц — дальность около 10 км. Коллеги, свежее видео работы детектора SPV. Детектор перехватил сигнал на частоте 5715 МГц на дистанции около 10 км. Примечательно, что перехват осуществлялся в условиях небольшого лесного массива — листва и стволы создают дополнительное затухание, но SPV уверенно справился. • Дальность 10 км — серьёзный показатель, особенно с учётом лесного покрова. Спасибо коллеге

5 Aug 2026, 06:54 UTC≈1,330 viewsread 6 August 2026

📡 Обновление до v28: как перепрошить SPV Коллеги, в предыдущем посте анонсировали новую версию v28 с расширением диапазона до 8780 МГц. Теперь — детали по перепрошивке. Обновление программное, и нам все же удалось найти способ с минимальными аппаратными изменениями добиться работоспособности старых версий на новой прошивке. Какие версии можно обновить: • v25 и выше — обновляются напрямую, без аппаратных доработок

5 Aug 2026, 06:52 UTC376 views1 reactionsread 6 August 2026
Photo

📡 Расширение диапазона SPV до 8780 МГц. Коллеги, мы расширили рабочий диапазон до 8780 МГц. В этот раз — программное расширение, без серьёзных аппаратных изменений. Основной диапазон: • 1.2 ГГц: 1060–2600 МГц • 3.3 ГГц: 2900–4040 МГц • 5.8 ГГц: 4867–6060 МГц • 7.2 ГГц: 6080–8480 МГц Расширенный диапазон: • 1.2 ГГц: 1040–2700 МГц • 3.3 ГГц: 2810–4040 МГц • 5.8 ГГц: 4867–6060 МГц • 7.2 ГГц: 6080–8780 МГц Важно: На

👌1

1 Aug 2026, 13:59 UTC≈1,700 viewsread 6 August 2026
Photo

📡 Детектор SPV: перехват на 1120 МГц — пример работы в реальных условиях Коллеги, новое видео работы детектора SPV. Перехват видео на частоте 1120 МГц с дальней дистанции. Цитата коллеги: «Огромное спасибо разработчикам и проекту SPV. Данный прибор спасает жизнь в тяжёлых условиях современной спецоперации. Пример на видео — перехват крыла противника на 1-ваттном видеопередатчике, дистанция 7 км.» Что важно отмети

27 Jul 2026, 09:55 UTC≈2,150 views3 reactionsread 6 August 2026
Video

Коллеги, наш товарищ Туман продолжает с пристрастием испытывать детектор SPV. Очередное видео — перехват прямо из окна, на частоте 1160 МГц с инверсией, что доступно не каждому детектору. Немного эмоциональных цитат: «бетон стройка и 1 км перехват ...ох....ь» «Ну и высота крыла так-то 1.2 км...» Вполне достойный результат работы детектора. Обратите внимание: это носимый детектор, который крепится на амуниции и им

2👍1

25 Jul 2026, 09:03 UTC407 viewsread 6 August 2026
Photo

📡 «Это больше чем прибор — это карманный РЭР» Коллеги, получили отзыв бойцов. Без лишних слов — просто факт. Тот случай, когда нечего добавить. Благодарим коллег за то, что по достоинству оценили наш титанический труд. Берегите себя... Заказать детектор: @maxVcube_bot

21 Jul 2026, 11:46 UTC≈1,180 views0 reactionsread 6 August 2026

Вопрос: сколько должна держать батарея на SPV? (дополнение к посту) Зависит от версии. • Ранние версии (без частоты 7 ГГц) — АКБ 5000 мА·ч. • Версии с 7 ГГц — АКБ 10500 мА·ч. По паспорту для версий с 7 ГГц — время работы в режиме ожидания до 8 часов. Время работы, это работа до отключения детектора. Но тут важно понимать: в каком именно режиме. Аналогия - телефон. Смотришь видео — час. Просто лежит в кармане —

20 Jul 2026, 16:31 UTC≈3,160 views3 reactionsread 6 August 2026

📡 Мысли. А существует ли альтернатива внешним антеннам? Часто приходят вопросы: «Можно ли использовать SPV в бункере или подвале?», «Можно ли сделать выносные антенны на детекторе?» Мы делали детектор как автономный носимый прибор. Про антенны писали не раз — почему остановились на внутренних. Но есть одна идея, один способ, который может решить задачу. Ответ: Если собрать репитер, все может получиться. Это как

🤔21

20 Jul 2026, 07:18 UTC≈1,490 views6 reactionsread 6 August 2026

Мысли В сети много рассуждений на тему обеспечения безопасности, разработки систем противодействия дронам. Но любой системе нужен фундамент. Дом без фундамента не построишь. Почему бы не использовать детекторы как основу такой системы? На данном этапе это вполне посильная задача. Главное — не применять жизненное кредо «можно, а зачем?». Затем, что это и есть фундамент. Начать стоит с малого, вполне реализуемого, а

3👍2🤔1

20 Jul 2026, 07:06 UTC≈2,220 viewsread 6 August 2026
Video

📡 SPV в гражданском использовании. Коллеги, мы привыкли рассматривать детектор SPV как специализированный инструмент. Но видео от пользователей всё чаще наталкивают на мысль о более широком применении. На одном видео — работа в автомобиле на трассе. На другом — с лавочки у подъезда дома. Без выносных антенн, без спецподготовки. Просто включил — и видишь обстановку. Где это может пригодиться гражданским: • Контрол

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

Citation-graph rank — 420,931 of 1,480,944entries 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.

Forward network

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.

Mentions

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.

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.

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

“Детектор SPV” (@detektor_spv), 363 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/detektor_spv.

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.