https://t.me/dpscontrol_vladivostok мы запустили новый чат
🥰1

Channel
@dpscontrol125rus
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
149subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001960332288 |
|---|---|
| Type | Channel |
| Username | @dpscontrol125rus |
| Description | Сливаем информацию о постах ДПС, пробках, авариях, помогаем друг другу на дорогах Владивостока уже больше 10 лет Главный канал https://t.me/dpscontrol125rus КУПИТЬ 💎PREMIUM @Dpscontrol125rus_bot По всем вопросам @Help_dpscontol125rus |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dpscontrol125rus |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 20:15 | 149 | no change |
| 7 Aug 2026, 14:14 | 149 | first reading |
10 posts held, back to 22 February 2024 — 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 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 10 posts for this entry, the most recent from 28 November 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
6 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 66.7% | |
| ❤ | 1 | 16.7% | |
| 🥰 | 1 | 16.7% |
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 3 of the 10 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 22 February 2024 to 28 November 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://t.me/dpscontrol_vladivostok мы запустили новый чат
🥰1
https://chat.whatsapp.com/FVmqAYJ6hlC42iOu0wvcbV
https://chat.whatsapp.com/JdAfras9PyAAMFfs1JjGse
❗️ ДТП в районе ул. Кирова, 23 в Артеме. Версии участников разнятся. Водитель на Toyota Cresta заявляет, что Toyota Aqua при выезде со второстепенной дороги не пропустил Toyota Cresta. Но рулевой Aqua утверждает, что Cresta до перекрестка проехал пешеходный переход на запрещающий сигнал светофора. Сам перекресток регулируется знаками приоритета, светофор регулирует пешеходный переход 🚀 Подписаться @dpscontrol125ru
👍3❤1
💥Топовые Кроссы💥 🔝Новые дизайны 2023-2024. 👍🏻Люксовые Качество. Адрес: ТЦ Луговая ⬇️ 1-2 Этаж Бутик-108 и 259📍 С 10:00 До 20:00 Магазин Работает ✔️
По факту смерти ребёнка на тренировке в Тавричанке возбуждено уголовное дело. Свою проверку проводит и минздрав. Как рассказали следователи, во время тренировки по рукопашному бою 6-летний мальчик почувствовал сильное недомогание, его состояние ухудшилось. Несмотря на комплекс проведенных медицинскими сотрудниками реанимационных мероприятий, ребёнок скончался. Возбуждено дело по ч. 1 ст. 109 УК РФ (причинение смерти…
👍1
Демонтаж «Дворца связи» на Семёновской продолжается.
Сегодня утром на Олега Кошевого в районе Реми произошло ДТП с участием Toyota Ractis, BMW X5 и тягача Sitrak. Момент аварии попал в объектив видеокамеры. Видео: @svodka255
Во Владивостоке охранники ТРК Луговая поймали дерзкую воровку шапок. Хотела бы поблагодарить охрану ТРК Луговая, что помогли поймать женщину воровку. Просмотрели все камеры и нашли её и сами привели в магазин. Большое спасибо. — рассказала владелица бутика. Нажми, чтобы подписаться на DPS VL
❗️ Момент столкновения на ул. Олега Кошевого 🚀 Подписаться @dpscontrol125rus
Showing the 10 most recent of 10 posts we hold for @dpscontrol125rus. 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.
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.
@dpscontrol125rus named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“DPSCONTROL125RUS” (@dpscontrol125rus), 149 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/dpscontrol125rus.
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.