Telegram RegisterThe public register of Telegram
Telegram profile photo for Госавтоинспекция СПб и ЛО

Channel

Госавтоинспекция СПб и ЛО

@ugibdd78

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

8,154subscribers

-247 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001525299694
TypeChannel
Username@ugibdd78
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/ugibdd78

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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

8,1548,4018,277.56 August 2026 — 8,401 subscribers7 August 2026 — 8,399 subscribers10 August 2026 — 8,296 subscribers12 August 2026 — 8,292 subscribers16 August 2026 — 8,287 subscribers19 August 2026 — 8,283 subscribers22 August 2026 — 8,260 subscribers25 August 2026 — 8,249 subscribers28 August 2026 — 8,247 subscribers31 August 2026 — 8,237 subscribers4 September 2026 — 8,230 subscribers9 September 2026 — 8,180 subscribers13 September 2026 — 8,160 subscribers16 September 2026 — 8,154 subscribers6 August 202616 September 2026
14 measurements spanning 41 days, net -247. 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 8,117–8,438 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 20:158,154-6
13 Sept 2026, 03:408,160-20
9 Sept 2026, 02:198,180-50
4 Sept 2026, 00:198,230-7
31 Aug 2026, 10:568,237-10
28 Aug 2026, 02:138,247-2
25 Aug 2026, 12:288,249-11
22 Aug 2026, 11:248,260-23
19 Aug 2026, 10:038,283-4
16 Aug 2026, 01:568,287-5
12 Aug 2026, 18:468,292-4
10 Aug 2026, 05:108,296-103
7 Aug 2026, 11:168,399-2
6 Aug 2026, 21:488,401first reading

Engagement

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

ERR · 30 days
17.2%
avg views ÷ 8,154 subscribers
Avg views / post
1,400
11 posts measured
Reaction rate
0.462%
reactions ÷ views · ER floor
Posts in window
11
of 66 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 9 of 11 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 28 August 2026
Posts held66 (27 July 202628 August 2026)
Views total15,399
Reactions total54
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 18:10 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
40m 50s
Average length
1m 01s

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

313 reactions across 51 posts, in 17 distinct kinds. The most used accounts for 29.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍9229.4%
6922.0%
🤔4213.4%
😢4012.8%
😱185.75%
😭165.11%
🔥154.79%
🥰41.28%
👏30.958%
💯30.958%
🤩30.958%
👌20.639%
🫡20.639%
10.319%
👀10.319%
🕊10.319%
🤝10.319%

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 53 of the 66 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 313 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 66 most recent posts we hold, published 27 July 2026 to 28 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

28 Aug 2026, 07:04 UTC≈1,350 views2 reactionsread 28 August 2026
Photo

Photo, posted without a caption

1😢1

27 Aug 2026, 16:33 UTC899 views2 reactionsread 28 August 2026
Forwarded from @spb_police78Video

⚡️Полиция проводит проверку по факту ДТП с пострадавшими на Софийской улице ⚡️ Как сообщалось ранее, сегодня в 12:40 на пересечении Софийской улицы с Усть-Ижорским шоссе произошло дорожно транспортное происшествие с двумя пассажирскими автобусами. Водитель управляющий автобусом "Маз" совершил наезд на другой пассажирский автобус - "Волгобас", остановившийся по причине технической неисправности. ◾️В результате столкн

1😢1

27 Aug 2026, 16:24 UTC≈1,030 views9 reactionsread 28 August 2026
Video

🚓Госавтоинспекция Санкт-Петербурга поймала водителя "пролетевшего" на "красный" 25 августа в 21:47 в Красносельском районе водитель "Шкода Октавиа" совершил сразу несколько опасных нарушений Правил дорожного движения. ⚡️Водитель Шкоды выехал на полосу встречного движения,проехал на запрещающий сигнал светофора, не уступив дорогу пешеходам, переходившим проезжую часть по регулируемому переходу. За каждое из этих на

👍81

26 Aug 2026, 09:33 UTC≈1,240 views17 reactionsread 28 August 2026
Forwarded from @spb_police78Video

⚡️Сотрудники ДПС Главка оказали помощь в сопровождении до больницы 🚔 23 августа около 01:24 в Новосаратовке к экипажу ОСБ ДПС №2 обратилась девушка, сообщив, что её ребёнку стало резко плохо: начались судороги, он терял сознание. 👮‍♂️ Сотрудники — старший инспектор ДПС старший лейтенант полиции Сергей Минкевич и прапорщик полиции Михаил Пальмовский — на служебном автомобиле доставили маму с ребёнком до Детской клини

10👍6🔥1

24 Aug 2026, 13:24 UTC≈1,590 views6 reactionsread 28 August 2026
Video

🚓🚨Сотрудники Госавтоинспекции Красногвардейского района помогли пешеходу, сбитому на пешеходном переходе 21 августа на проспекте Наставников водитель автомобиля «Рено Сандеро», двигаясь со стороны проспекта Энтузиастов к улице Косыгина, сбил пешехода прямо в зоне регулируемого пешеходного перехода. Как отмечают очевидцы, водитель выехал на перекрёсток на запрещающий сигнал светофора. Прибывшие на место происшеств

5🔥1

24 Aug 2026, 07:45 UTC≈1,370 viewsread 28 August 2026
Forwarded from @spb_police78Video

🎥 Комментарий: Заместитель начальника отдела Госавтоинспекции УМВД России по Выборгскому району Ленинградской области майор полиции Ванин Алексей Сергеевич

24 Aug 2026, 07:45 UTC≈1,350 views4 reactionsread 28 August 2026
Forwarded from @spb_police78Video

⚡️В ходе рейда полиция выявила грубые нарушения Правил дорожного движения на территории Выборгского района Ленинградской области 👮‍♂️ Сотрудниками Госавтоинспекции Выборгского района Ленинградской области совместно с ОБ и ОСБ Управления Госавтоинспекции ГУ МВД проводились рейдовые мероприятия, нацеленные на выявление нарушений Правил дорожного движения на аварийно-опасном участке автодороги «Скандинавия» и на подъез

👍21🤔1

23 Aug 2026, 14:38 UTC≈1,510 views6 reactionsread 28 August 2026
Video

🚑Сотрудники Госавтоинспекции Тосненского района оказали первую помощь пострадавшему в ДТП В Тосненском районе Ленинградской области инспекторы ДПС оперативно оказали помощь водителю электровелосипеда, который не справился с управлением, в результате чего получил серьезную травму головы. Прибыв на место ДТП, сотрудники Госавтоинспекции оценили состояние пострадавшего и использовали штатную медицинскую укладку для ок

5🔥1

23 Aug 2026, 08:12 UTC≈1,430 views7 reactionsread 28 August 2026
Forwarded from @spb_police78Video

⚡️В Волхове полицейским пришлось стрелять по колесам, чтобы остановить пьяного водителя 👮‍♂️ 19 августа около часа ночи инспекторы Госавтоинспекции, патрулируя район Мурманского шоссе, обратили внимание на автомобиль «Киа Х3», водитель которого опасно вилял и в какой-то момент вылетел на «встречку». 👿 Увидев полицейский автомобиль, нарушитель прибавил газ и решил скрыться. 🚓 Стражами порядка было организовано пресле

👍7

22 Aug 2026, 10:15 UTC≈1,450 views6 reactionsread 28 August 2026
Forwarded from @spb_police78Video

⚡️Сотрудники Госавтоинспекции задержали нетрезвого водителя 👮‍♂️ 21 августа в 22:00 на Комендантском проспекте нарядом Госавтоинспекции была предпринята попытка остановки автомобиля «Санг Енг» однако, водитель, увидев полицейских, увеличил скорость и попытался скрыться. 🚓 Экипажем ДПС было организовано преследование нарушителя, и у дома 26 по улице Плесецкой автомобиль был остановлен. 👿 42-летний мужчина, управлявши

👍4👏1😢1

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

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.

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.

Госавтоинспекция России
@guobddrus · 35,167
Telegram ranks this channel #23 of 95 here — alongside 94 others — read 2 September 2026
Объединённая пресс-служба судов Санкт-Петербурга
@SPbGS · 26,905
Telegram ranks this channel #48 of 87 here — alongside 86 others — read 11 September 2026
Аэропорт Пулково
@pulkovo_led · 49,486
Telegram ranks this channel #66 of 83 here — alongside 82 others — read 25 August 2026
47news
@allnews47 · 45,093
Telegram ranks this channel #72 of 89 here — alongside 88 others — read 28 August 2026
Вестник Киберполиции России
@cyberpolice_rus · 83,750
Telegram ranks this channel #82 of 92 here — alongside 91 others — read 18 August 2026
Александр ДроZденко
@drozdenko_au_lo · 80,651
Telegram ranks this channel #85 of 91 here — alongside 90 others — read 18 August 2026
Эрмитаж
@hermitage_museum · 39,023
Telegram ranks this channel #92 of 97 here — alongside 96 others — read 31 August 2026

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

“Госавтоинспекция СПб и ЛО” (@ugibdd78), 8,154 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/ugibdd78.

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.