Относительная разница в размерах на 17 и 21 дБи рупорных антенн двойной круговой поляризации. Такое относительное соотношение сохраняется от 4.8 и до 15 ГГц, диапазон в котором можно заказать партию антенн
Channel
LR FPV
@LRFPV73
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
1,292subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001752165084 |
|---|---|
| Type | Channel |
| Username | @LRFPV73 |
| Created | 6 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/LRFPV73 |
Topic
Technology — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 15 Sept 2026, 07:15 | 1,292 | +2 |
| 7 Sept 2026, 23:37 | 1,290 | +4 |
| 2 Sept 2026, 12:04 | 1,286 | -2 |
| 30 Aug 2026, 09:54 | 1,288 | +3 |
| 27 Aug 2026, 05:48 | 1,285 | -2 |
| 24 Aug 2026, 11:16 | 1,287 | -1 |
| 20 Aug 2026, 18:15 | 1,288 | +1 |
| 17 Aug 2026, 11:12 | 1,287 | +1 |
| 14 Aug 2026, 02:38 | 1,286 | +1 |
| 11 Aug 2026, 05:15 | 1,285 | +3 |
| 7 Aug 2026, 22:46 | 1,282 | no change |
| 7 Aug 2026, 12:15 | 1,282 | first reading |
Engagement
13 posts held, back to 7 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 13 posts for this entry, the most recent from 1 April 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
17 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 41.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 7 | 41.2% | |
| ⚡ | 5 | 29.4% | |
| 👍 | 4 | 23.5% | |
| ❤ | 1 | 5.88% |
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 6 of the 13 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 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 7 January 2026 to 1 April 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
Антенна широкополосная 800-6400 МГц, двойной линейной поляризации. Тип Вивальди с диэлектрической линзой. Особенности подавление заднего и боковых лепестков. Низ 10 дБи, начиная с 1300МГц 14 и далее около 16 дБи
⚡3
Photo, posted without a caption
⚡2
Вторая ревизия двух портовых антенн круговой поляризации MIMO левая и правая поляризация. Вариант 21 дБи, рекомендуемый диапазон 4.7-7.5 ГГц, но может быть использована в расширенном диапазоне 3.8-7.6 ГГц. Вес 1.5 кг, разъемы N . На графиках представлен разброс значений S11-S12 по партии антенн, и развязка портов S12. Примерные размеры на фото. Из новинок аналогичные антенны двойной круговой поляризации на 10-14.6 …
🔥3
File, posted without a caption
Эта же антенна. Просто поставлен сменный рупор (побольше). ДН на 6 ГГц вход правой круговой поляризации (для левой картинка будет аналогичной) - боковые лепестки незначительны. Эллиптичность и все остальные параметры не изменяются и остаются в пределах допуска. Мне задавали вопрос если через делитель подать синфазный на оба входа, то будет ли одновременно две круговых поляризации. Ответ нет, получится линейная. Если …
👍2❤1
File, posted without a caption
Photo, posted without a caption
File, posted without a caption
Появился еще один дополнительные плагин к X-Vivaldi добавляется к существующей конструкции и позволяет поднять КУ на верхах. Плагин съемный, можно ставить можно снимать, по необходимости. Ниже картинки ДН с плагином, выше в канале без плагина. Аналогичный плагин разработан и для рупорных антенн
File, posted without a caption
Новая серия рупорных антенн большой мощности (200-500 Ватт) двойной круговой поляризации (один вход левая, другой вход правая, развязка около 22-30 дБ по диапазону). Полоса 22-25%, эллиптичность по рабочему диапазону менее 1.5. Варианты исполнения ~13-14 дБи ~19 дБи. Центральная частоты от 2200 МГц до 6.5 ГГц. Разъем только N-type. Материал алюминий. Если партия большая возможны варианты кастомизации
🔥1
Showing the 12 most recent of 13 posts we hold for @LRFPV73. 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.
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.
@csp_voron · 24,477
Telegram ranks this channel #60 of 63 here — alongside 62 others — read 16 September 2026
@texotdelBPLA · 23,524
Telegram ranks this channel #63 of 64 here — alongside 63 others — read 18 September 2026
@FPV_vyZOV · 67,842
Telegram ranks this channel #71 of 71 here — alongside 70 others — read 21 August 2026
@my_el_lab · 44,085
Telegram ranks this channel #74 of 76 here — alongside 75 others — read 29 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“LR FPV” (@LRFPV73), 1,292 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/LRFPV73.
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.