Telegram RegisterThe public register of Telegram

Channel

GedzTech

@GedzTech

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

29subscribers

+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-1002347917763
TypeChannel
Username@GedzTech
DescriptionКанал українського виробника gedz.tech🇺🇦 більше інфо: https://bio.site/GedzTech Звʼязок: @GedzBot
CreatedBetween 1 September 2024 and 29 October 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/GedzTech

Growth

297 August 2026 — 29 subscribers11 August 2026 — 29 subscribers7 August 202611 August 2026
2 measurements spanning 4 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 28–30 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:1529no change
7 Aug 2026, 14:0929first reading

Engagement

13 posts held, back to 29 October 2024the 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 13 posts for this entry, the most recent from 23 May 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
25
Videos
4
Links
7

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
12m 09s
Average length
3m 02s

Measured directly from 4 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

5 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍480.0%
🔥120.0%

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 5 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 5reactions 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 29 October 2024 to 23 May 2025, 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

23 May 2025, 08:56 UTC743 viewsread 11 August 2026
Photo

📡CellMapper — це безкоштовна краудсорсингова платформа (як додаток для смартфонів, так і вебсайт), яка збирає та візуалізує дані про покриття та характеристики стільникових мереж по всьому світу. Основні функції та можливості: ❇️ Картування базових станцій: Користувачі з встановленим додатком CellMapper (доступний для Android) збирають дані про рівень сигналу, ідентифікатори базових станцій (Cell ID), частоти, тип м

4 Apr 2025, 19:27 UTC71 views1 reactionsread 11 August 2026
Photo

Оновили інструкцію для Minion BOB

👍1

26 Mar 2025, 09:11 UTC78 viewsread 11 August 2026
Forwarded from @serhii_flash

Я уже писал про прибор для диагностики РЕБ. Производитель тогда отправил сто приборов бесплатно тем, кому я оправлял наборы для создания точки РЕР. Ребята выпустили версию 2 - теперь на 100-1500 МГц. Добавили стандартный разъем SMA и компактную антенну в комплект. Прибор предназначен для: •⁠ ⁠Плановой и послебоевой диагностики парка техники с РЕБ для подтверждения исправности и надежности защиты. •⁠ ⁠Контроля ур

23 Mar 2025, 07:40 UTC135 viewsread 11 August 2026
Video

Огляд оновленої версії пристрою для тестування РЕБ Minion BOB v2

27 Dec 2024, 09:38 UTC111 views1 reactionsread 11 August 2026

Шановне козацтво! 🇺🇦💪 Дякуємо, що обрали Minion Bob для діагностики РЕБ та аналізу частот! Ваша довіра — наша найкраща нагорода! 🤝 🔥 Працюємо над розширенням діапазону частот, щоб Minion Bob став ще ефективнішим. ⚡️ Готуємо наступну партію. Відправлення розпочнемо з середини січня. Слава Україні! 🇺🇦

👍1

29 Nov 2024, 16:31 UTC193 viewsread 11 August 2026
Video

Детальніше про режими Діагностування та Скан приладу Minion BOB📡 Як налаштовуються, та як працюють від нашого колеги у відео-огляді🫡

29 Nov 2024, 11:42 UTC167 viewsread 11 August 2026
File

Додатково дублюємо інструкцію до пристрою діагностики РЕБ Minion BOB

21 Nov 2024, 07:21 UTC≈133,000 views2 reactionsread 11 August 2026
Video

Отримали ось такий огляд на MiNiON-Bob – прилад діагностування РЕБ в діапазоні частот 390-1040 МГц, включно з FPV та подібними БПЛА. Замовляйте на сайті за посиланням або пишіть нам в телеграм-бот @GedzBot, якщо виникли якісь питання.

👍2

14 Nov 2024, 13:06 UTC131 views1 reactionsread 11 August 2026
Forwarded from @serhii_flashVideo

Толковый прибор для проверки работы РЕБ. Сразу видны и частоты и уровни помехи от РЕБ на них. Достаточно иметь один такой на пидроздiл и проверять как можно чаще все РЕБ. Ни я, ни админы их не продаем!!! Вот сайт разработчиков https://gedz.tech/minion-bob

🔥1

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

Forward network

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.

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

“GedzTech” (@GedzTech), 29 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/GedzTech.

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.