Telegram RegisterThe public register of Telegram
Telegram profile photo for Ищу видео или свидетелей ДТП

Channel

Ищу видео или свидетелей ДТП

@poisk_video_dtp

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

581subscribers

+38 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002854072262
TypeChannel
Username@poisk_video_dtp
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/poisk_video_dtp

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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

541584562.56 August 2026 — 543 subscribers6 August 2026 — 542 subscribers6 August 2026 — 542 subscribers12 August 2026 — 541 subscribers19 August 2026 — 571 subscribers25 August 2026 — 572 subscribers31 August 2026 — 584 subscribers16 September 2026 — 581 subscribers5816 August 202616 September 2026
8 measurements spanning 41 days, net +38. 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 535–590 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 10:38581-3
31 Aug 2026, 20:28584+12
25 Aug 2026, 09:42572+1
19 Aug 2026, 00:22571+30
12 Aug 2026, 05:42541-1
6 Aug 2026, 18:18542no change
6 Aug 2026, 06:15542-1
6 Aug 2026, 04:32543first reading

Engagement

19 posts held, back to 5 May 2026the 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 19 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 6 posts, in 7 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥220.0%
🤡220.0%
🤯220.0%
110.0%
👍110.0%
😱110.0%
🤣110.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 8 of the 19 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 19 most recent posts we hold, published 5 May 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

6 Aug 2026, 17:41 UTC43 viewsread 6 August 2026
Video

И снова ДТП на этом же месте. https://t.me/stop_cityracing/11631 #Гвардейская #Даурская @poisk_video_dtp - телеграм-канал помощи в поиске свидетелей и видео с ДТП.

4 Jun 2026, 21:54 UTC472 views2 reactionsread 6 August 2026
Forwarded from @stop_cityracingVideo

Момент #ДТП у стен #Кремля 4 июня 2026 года. Судя по видео — водитель #BMW не справился с управлением. @stop_cityracing - телеграм-канал о ПДД. @poisk_video_dtp - телеграм-канал помощи в поиске свидетелей и видео с ДТП. Телеграм-каналы и СМИ, которые оставляют активные ссылки на источники могут расчитывать на оригинал видео без водяных знаков и прочего. Для связи — @official_stopcityracing #ПДД #StopCityRacing #К

🤡2

3 Jun 2026, 08:49 UTC≈3,840 viewsread 6 August 2026
Video

#Н255СК716 #ДТП Разыскиваются свидетели #ПДД #StopCityRacing #Казань ⚡️ Отправить видео: @stopcityracing_bot

25 May 2026, 11:18 UTC558 views3 reactionsread 6 August 2026
Forwarded from @stop_cityracingVideo

Момент #ДТП с уличной камеры. Водителю стало плохо или отвлекся на телефон? #ПДД #StopCityRacing #Казань ⚡️ Отправить видео: @stopcityracing_bot

🤯2😱1

21 May 2026, 07:48 UTC≈3,870 viewsread 6 August 2026
Photo

Для установления обстоятельств ДТП разыскиваем доступ к камерам на Х.Мавлютова, 39 @stopcityracing - для связи

20 May 2026, 05:01 UTC567 views0 reactionsread 6 August 2026
Photo

Здравствуйте. Ищем свидетелей и записи камер ДТП между такси (Jetta VA3) и мотоциклом Honda на ул. Тихомирного, возле дома 19, произошедшее 17 мая 2026 года примерно в 20.30 Также ищем свидетелей и видео дтп между этим же мотоциклом и автомобилем мерседес, произошедшее в этом же месте в 20.40 (мерс гонялся с бмв и врезался в стоящий мотоцикл). Спасибо. Тел. 89872759530

19 May 2026, 21:11 UTC≈4,280 viewsread 6 August 2026
Video

Момент смертельного #ДТП в Салмачах. Осуществляем помощь в поиске видео момента #ДТП бесплатно! @poisk_video_dtp Проект @stop_cityracing

18 May 2026, 08:06 UTC543 viewsread 6 August 2026
Photo

Здравствуйте. Разыскиваю свидетелей дтп на ул. Истомина д. 88, возле военной поликлинике произошло 18.05.2026 г. с 8:30 до 10:30 утра, неизвестный весь бок протаранил на припаркованном хонда фит, 89118588666 очень признателен.

18 May 2026, 08:01 UTC484 viewsread 6 August 2026

Ищу видео ДТП 08.05.2026 на перекрестке Восстания и Тунакова время 16:25-16:30, самокатчик въехал в машину, буду очень благодарен если у кого есть @stopcityracing

17 May 2026, 16:42 UTC≈3,730 views1 reactionsread 6 August 2026
Video

Момент #ДТП на #Магистральной Осуществляем помощь в поиске момента #ДТП бесплатно! @poisk_video_dtp

🔥1

14 May 2026, 10:39 UTC≈3,550 views1 reactionsread 6 August 2026
Video

Момент #ДТП на перекрестке Чистопольская и Меридианная. Проект "Ищу видео или свидетелей ДТП" является некоммерческим и не преследует целей заработать. Поиск и публикация объявления осуществляется исключительно бесплатно! Проект @stop_cityracing P.S. Спасибо подписчикам за то, что делитесь доступом к камерам — это позволяет оперативно и своевременно находить и реагировать на обращения!

🔥1

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

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 1 registered channel — 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.

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.

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

“Ищу видео или свидетелей ДТП” (@poisk_video_dtp), 581 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/poisk_video_dtp.

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.