Продовжуємо притягати до відповідальності прихильників швидкісної їзди Щодня ми фіксуємо перевищення дозволеної швидкості за допомогою приладу TruCam на тих ділянках дороги, де найчастіше трапляються автопригоди. До прикладу, керманичі, які перевищили допустиму швидкість більше ніж на 50 км/год. Нагадаємо, що за перевищення швидкості передбачена відповідальність: ▪️за ч. 1 ст. 122 (Перевищення встановлених обмежен…

Channel
Патрульна поліція Чернівецької області
@patrolpolice_cv
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
1,450subscribers
+19 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001409501337 |
|---|---|
| Type | Channel |
| Username | @patrolpolice_cv |
| Created | 20 October 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/patrolpolice_cv |
Topic
Local community — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 18 Sept 2026, 21:18 | 1,450 | -3 |
| 14 Sept 2026, 06:18 | 1,453 | -7 |
| 11 Sept 2026, 00:18 | 1,460 | +3 |
| 5 Sept 2026, 23:19 | 1,457 | +4 |
| 1 Sept 2026, 12:58 | 1,453 | -3 |
| 29 Aug 2026, 16:03 | 1,456 | +2 |
| 26 Aug 2026, 08:48 | 1,454 | +5 |
| 23 Aug 2026, 09:34 | 1,449 | +6 |
| 20 Aug 2026, 00:11 | 1,443 | +4 |
| 16 Aug 2026, 18:12 | 1,439 | +6 |
| 13 Aug 2026, 00:27 | 1,433 | +1 |
| 9 Aug 2026, 22:21 | 1,432 | +2 |
| 7 Aug 2026, 07:32 | 1,430 | -1 |
| 6 Aug 2026, 20:31 | 1,431 | no change |
| 6 Aug 2026, 20:22 | 1,431 | first reading |
Engagement
17 posts held, back to 4 August 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 17 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
10 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 60.0% | |
| 🔥 | 2 | 20.0% | |
| ⚡ | 1 | 10.0% | |
| 🥰 | 1 | 10.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 4 of the 17 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 4 August 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
Пам’ятайте: нетверезий водій — це загроза для життя та здоров’я всіх учасників дорожнього руху❗️ Учора, близько 21-ї, ми отримали повідомлення про ДТП, що сталося неподалік від перехрестя вулиці Сергія Скальда та вулиці Небесної Сотні. Прибувши на місце події, ми з’ясували, що водій транспортного засобу Mercedes-Benz не обрав безпечної швидкості руху та не дотримався безпечного інтервалу, внаслідок чого допустив …
Втрати ворога станом на 06.08.2026
Оновлено: рух відновлено ✅
До уваги водіїв ❗️❗️❗️ На вулиці Скальда, сталася ДТП. На місці події працюють патрульні поліцейські. Рух ускладнений❗️Розʼїзд авто здійснюється реверсом. Плануйте маршрут своєї поїздки з урахуванням цієї інформації. Кермуйте відповідально, неухильно дотримуйтесь правил дорожнього руху та не перевищуйте швидкісний режим. #patrolpolice_cv
Ми зупинили водія вміст алкоголю в крові якого перевищував норму більше ніж в 10 разів Учора, близько 13-ї години, на вулиці Буковинській, за порушення ПДР поліцейські зупинили транспортний засіб Hyundai. Під час спілкування з керманичем інспектори помітили, що у нього присутні характерні ознаки алкогольного сп'яніння. Водій погодився пройти огляд на місці зупинки. Результат позитивний — 2,16 проміле. На 33-річн…
🚦Міжнародний день світлофора Сьогодні світлофор — один із найважливіших елементів організації дорожнього руху. Щодня він допомагає уникати аварій, впорядковує рух транспорту й пішоходів та нагадує, що безпека на дорозі починається з дотримання простих правил. Закликаємо всіх учасників дорожнього руху: 🔴зупинятися на червоний сигнал; 🟠бути уважними на жовтий; 🟢починати рух лише на зелений, переконавшись у безпеці. …
З якою максимальною швидкістю дозволено рух транспортних засобів, якими керують водії зі стажем до двох років, на всіх дорогах за межами населених пунктів?
- 60 км/год26%
- 70 км/год53%
- 80 км/год11%
- 90 км/год11%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Якою має бути швидкість під час руху в темну пору доби або в умовах недостатньої видимості?
- Не більше 50 км/год22%
- Не більше 70 км/год5%
- Такою, щоб водій мав змогу зупинити транспортний засіб у межах видимості дороги.53%
- Такою, щоб не створювати перешкод іншим учасникам дорожнього руху.5%
- Такою, щоб відповідати максимально дозволеній швидкості на цій ділянці дороги.15%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🤔
- Знак 11%
- Знак 21%
- Знак 34%
- Знак 41%
- Знак 592%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Який із зображених дорожніх знаків забороняє рух з більшою швидкістю, ніж зазначено на знакові?
❤1
У житлових і пішохідних зонах швидкість руху не повинна перевищувати
- 20 км/год70%
- 30 км/год17%
- 40 км/год6%
- 50 км/год7%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
❤1
Showing the 12 most recent of 17 posts we hold for @patrolpolice_cv. 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.
Polls
The 5 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
З якою максимальною швидкістю дозволено рух транспортних засобів, якими керують водії зі стажем до двох років, на всіх дорогах за межами населених пунктів?
- 60 км/год26%
- 70 км/год53%
- 80 км/год11%
- 90 км/год11%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Якою має бути швидкість під час руху в темну пору доби або в умовах недостатньої видимості?
- Не більше 50 км/год22%
- Не більше 70 км/год5%
- Такою, щоб водій мав змогу зупинити транспортний засіб у межах видимості дороги.53%
- Такою, щоб не створювати перешкод іншим учасникам дорожнього руху.5%
- Такою, щоб відповідати максимально дозволеній швидкості на цій ділянці дороги.15%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🤔
- Знак 11%
- Знак 21%
- Знак 34%
- Знак 41%
- Знак 592%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
У житлових і пішохідних зонах швидкість руху не повинна перевищувати
- 20 км/год70%
- 30 км/год17%
- 40 км/год6%
- 50 км/год7%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
У населених пунктах рух транспортних засобів дозволяється зі швидкістю не більше
- 40 км/год10%
- 50 км/год81%
- 60 км/год7%
- 70 км/год1%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 17 most recent posts we hold, published 4 August 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 4 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.
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.
@ChernivtsiCityCouncil · 28,060
Telegram ranks this channel #14 of 79 here — alongside 78 others — read 10 September 2026
@chernivetskaODA · 29,409
Telegram ranks this channel #26 of 89 here — alongside 88 others — read 8 September 2026
@chernivtsigram · 28,555
Telegram ranks this channel #27 of 82 here — alongside 81 others — read 9 September 2026
@pereval_media · 44,921
Telegram ranks this channel #30 of 84 here — alongside 83 others — read 27 August 2026
@chernivcitruexa · 97,893
Telegram ranks this channel #37 of 83 here — alongside 82 others — read 16 August 2026
@chernivtsigram_chernivtsi24 · 22,592
Telegram ranks this channel #41 of 78 here — alongside 77 others — read 20 September 2026
@GrozaNewsUA · 21,462
Telegram ranks this channel #63 of 86 here — alongside 85 others — read 23 September 2026
@fainemisto_tv · 25,837
Telegram ranks this channel #63 of 84 here — alongside 83 others — read 13 September 2026
This channel appears in 8 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Патрульна поліція Чернівецької області” (@patrolpolice_cv), 1,450 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/patrolpolice_cv.
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.