Telegram RegisterThe public register of Telegram
Telegram profile photo for Вишгород оперативний

Channel

Вишгород оперативний

@Vyshorod_Operative

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

42,428subscribers

+715 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001571267102
TypeChannel
Username@Vyshorod_Operative
Created26 February 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live3 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/Vyshorod_Operative

Growth

41,71342,51242,112.57 August 2026 — 41,713 subscribers7 August 2026 — 41,713 subscribers7 August 2026 — 41,740 subscribers8 August 2026 — 41,768 subscribers9 August 2026 — 41,765 subscribers10 August 2026 — 41,814 subscribers11 August 2026 — 41,930 subscribers12 August 2026 — 42,061 subscribers14 August 2026 — 42,148 subscribers15 August 2026 — 42,177 subscribers16 August 2026 — 42,240 subscribers17 August 2026 — 42,311 subscribers18 August 2026 — 42,388 subscribers19 August 2026 — 42,390 subscribers20 August 2026 — 42,510 subscribers22 August 2026 — 42,512 subscribers23 August 2026 — 42,491 subscribers25 August 2026 — 42,427 subscribers26 August 2026 — 42,436 subscribers27 August 2026 — 42,452 subscribers28 August 2026 — 42,469 subscribers28 August 2026 — 42,458 subscribers30 August 2026 — 42,461 subscribers31 August 2026 — 42,474 subscribers1 September 2026 — 42,463 subscribers2 September 2026 — 42,439 subscribers3 September 2026 — 42,428 subscribers42,4287 August 20263 September 2026
27 measurements spanning 27 days, net +715. 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 41,593–42,632 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
3 Sept 2026, 11:5942,428-11
2 Sept 2026, 07:3342,439-24
1 Sept 2026, 05:2642,463-11
31 Aug 2026, 02:1642,474+13
30 Aug 2026, 02:3442,461+3
28 Aug 2026, 23:3842,458-11
28 Aug 2026, 02:5442,469+17
27 Aug 2026, 01:4542,452+16
26 Aug 2026, 04:2442,436+9
25 Aug 2026, 02:4742,427-64
23 Aug 2026, 16:2342,491-21
22 Aug 2026, 04:2742,512+2
20 Aug 2026, 20:5442,510+120
19 Aug 2026, 20:0442,390+2
18 Aug 2026, 21:0842,388+77
17 Aug 2026, 18:3642,311+71
16 Aug 2026, 17:5742,240+63
15 Aug 2026, 06:5242,177+29
14 Aug 2026, 00:2742,148+87
12 Aug 2026, 20:2542,061first reading

Engagement

861 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 58 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.5%
avg views ÷ 42,428 subscribers
Avg views / post
5,710
861 posts measured
Reaction rate
0.907%
reactions ÷ views · ER floor
Posts in window
861
of 861 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 859 of 861 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 3 September 2026
Posts held861 (6 August 20263 September 2026)
Views total4,913,968
Reactions total44,570
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 07:30 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.

What this channel posts

Video runtime
59m 02s
Average length
56s

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

44,570 reactions across 859 posts, in 22 distinct kinds. The most used accounts for 45.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏20,20445.3%
🤬8,31818.7%
6,48814.6%
😢2,5405.70%
👍2,0384.57%
🔥1,2452.79%
😭1,2002.69%
😁7381.66%
😱4340.974%
🤯3900.875%
🤔2700.606%
🫡1390.312%
🤨1210.271%
😐1160.26%
💔750.168%
👏600.135%
👌450.101%
😍370.083%
🎉340.076%
🤝330.074%
2 further kinds450.101%

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

Measured over the 861 most recent posts we hold, published 6 August 2026 to 3 September 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

3 Sept 2026, 07:26 UTC334 views3 reactionsread 3 September 2026
Photo

👀Увага рекламодавцям та підписникам каналу🗣 Нагадуємо що у нас є бот, в який ви можете надіслати новину, або пропозицію про рекламну співпрацю❗️👇 @VyshorodOperativ_bot (посилання на бот ви завжди можете знайти в описі каналу) Для місцевого бізнесу, готові запропонувати найкращі умови співпраці ✔️ З повагою, адміністрація каналу Вишгород оперативний🖤

1🤝1🙏1

3 Sept 2026, 06:40 UTC≈3,490 views60 reactionsread 3 September 2026
Photo

🔴Рятувальники ліквідовували пожежі в Обухівському та Бориспільському районах Під ворожим ударом опинилися житлові будинки, споруди, об’єкти торгівлі, відпочинку та інфраструктури. Від вечора, упродовж ночі та до ранку рятувальники Київщини безперервно працюють на місцях російських ударів — ліквідовують пожежі та допомагають людям. ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

😢31🙏236

3 Sept 2026, 06:32 UTC≈3,520 views19 reactionsread 3 September 2026
Video

✅Відбій повітряної тривоги у Вишгородському районі Підписатись 👉 Вишгород оперативний

🙏134👍1😢1

3 Sept 2026, 06:32 UTC≈3,430 views21 reactionsread 3 September 2026

🔴Ще одна людина постраждала внаслідок ворожої атаки сьогодні вранці. В Обухівському районі жінка отримала гостру реакцію на стрес. Вся необхідна медична допомога була надана їй на місці. Також у районі виникла пожежа приватного будинку, пошкоджено автомобіль. ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

😢18🙏2👍1

3 Sept 2026, 06:20 UTC≈3,950 views24 reactionsread 3 September 2026

✅Дорозвідка ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

🙏18👍41🤔1

3 Sept 2026, 06:20 UTC≈3,980 views18 reactionsread 3 September 2026

🔴Мінус ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

🙏12👍51

3 Sept 2026, 06:18 UTC≈4,030 views16 reactionsread 3 September 2026

🔴Вишневе ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

🙏11🤬5

3 Sept 2026, 06:18 UTC≈3,990 views12 reactionsread 3 September 2026

🔴Один лишився Буча, Ірпінь ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

🙏7🤬5

3 Sept 2026, 06:12 UTC≈4,260 views14 reactionsread 3 September 2026

🔴 БпЛА на Катюжанку ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

🤬8🙏6

3 Sept 2026, 06:12 UTC≈4,340 views16 reactionsread 3 September 2026

🔴Йде в бік Гостомеля/Бучі. ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

🙏9🤬61

3 Sept 2026, 06:09 UTC≈4,430 views18 reactionsread 3 September 2026

🔴Другий на Димер курсом попереднього ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

🙏13🤬41

3 Sept 2026, 06:08 UTC≈4,500 views24 reactionsread 3 September 2026

🔴Йде в бік Гостомеля/Бучі. ✈️ Вишгород оперативний 🗣 Звʼязок з нами | ⚫️ Наш чат

🙏18🤬51

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

Mentions

Named by 2 registered channels — 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.

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

“Вишгород оперативний” (@Vyshorod_Operative), 42,428 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/Vyshorod_Operative.

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.