Telegram RegisterThe public register of Telegram
Telegram profile photo for ДПС Екатеринбург

Channel

ДПС Екатеринбург

@ekb96dps

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

1,812subscribers

+1 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-1001258481835
TypeChannel
Username@ekb96dps
Created23 August 2018 — measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live12 October 2026
Measurements held14
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/ekb96dps

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

1,8071,8171,8126 August 2026 — 1,811 subscribers6 August 2026 — 1,811 subscribers10 August 2026 — 1,810 subscribers12 August 2026 — 1,812 subscribers26 August 2026 — 1,811 subscribers29 August 2026 — 1,817 subscribers1 September 2026 — 1,815 subscribers5 September 2026 — 1,812 subscribers10 September 2026 — 1,810 subscribers14 September 2026 — 1,809 subscribers19 September 2026 — 1,810 subscribers28 September 2026 — 1,808 subscribers6 October 2026 — 1,807 subscribers12 October 2026 — 1,812 subscribers6 August 202612 October 2026
14 measurements spanning 67 days, net +1. 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 1,806–1,819 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 11:261,812+5
6 Oct 2026, 01:351,807-1
28 Sept 2026, 15:561,808-2
19 Sept 2026, 07:401,810+1
14 Sept 2026, 12:561,809-1
10 Sept 2026, 14:571,810-2
5 Sept 2026, 14:571,812-3
1 Sept 2026, 11:071,815-2
29 Aug 2026, 16:011,817+6
26 Aug 2026, 17:031,811-1
12 Aug 2026, 21:281,812+2
10 Aug 2026, 03:111,810-1
6 Aug 2026, 20:311,811no change
6 Aug 2026, 20:241,811first reading

Engagement

20 posts held, back to 30 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 20 posts for this entry, the most recent from 2 June 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Jun 2025, 17:39 UTC≈4,400 viewsread 7 August 2026

Дублёр Сибирского тракта - Замечен экипаж. (Источная улица / Дублёр Сибирского тракта, ~19 м.)

2 Jun 2025, 16:44 UTC≈4,330 viewsread 7 August 2026

Улица Амундсена - Замечен экипаж. (Разливная улица / Улица Амундсена, ~25 м.)

2 Jun 2025, 16:05 UTC≈4,330 viewsread 7 August 2026

Улица Фурманова - Замечен экипаж. (Улица Цвиллинга / Улица Фурманова, ~3 м.)

1 Jun 2025, 14:44 UTC≈4,000 viewsread 7 August 2026

Проспект Ленина - Замечен экипаж. (Улица 8 Марта / Проспект Ленина, ~7 м.)

1 Jun 2025, 13:11 UTC≈3,730 viewsread 7 August 2026

Проспект Академика Сахарова - Замечен экипаж. (Улица Вильгельма де Геннина / Проспект Академика Сахарова, ~4 м.)

1 Jun 2025, 13:10 UTC≈2,830 viewsread 7 August 2026

Улица Вильгельма де Геннина - Замечен экипаж. (Улица Академика Тимофеева-Ресовского / Улица Вильгельма де Геннина, ~6 м.)

1 Jun 2025, 08:19 UTC≈2,260 viewsread 7 August 2026

Артельный переулок - Замечен экипаж. (Бобруйская улица / Артельный переулок, ~28 м.)

31 May 2025, 05:12 UTC≈1,970 viewsread 7 August 2026

Г. Екатеринбург — аэропорт «Кольцово» - Замечен экипаж. (Г. Екатеринбург — аэропорт «Кольцово» / Г. Екатеринбург — аэропорт «Кольцово», ~0 м.) «3 патруля»

31 May 2025, 03:51 UTC≈1,670 viewsread 7 August 2026

Екатеринбургская кольцевая автомобильная дорога - Замечен экипаж. (Екатеринбургская кольцевая автомобильная дорога / Екатеринбургская кольцевая автомобильная дорога, ~0 м.)

30 May 2025, 19:34 UTC≈1,370 viewsread 7 August 2026

Снова замечены ДПС - Базовый переулок / Базовый переулок, ~0 м.

30 May 2025, 19:33 UTC≈1,290 viewsread 7 August 2026

Улица Вильгельма де Геннина - Замечен экипаж. (Улица Вильгельма де Геннина / Улица Вильгельма де Геннина, ~0 м.)

30 May 2025, 19:07 UTC≈1,130 viewsread 7 August 2026

Базовый переулок - Замечен экипаж. (Базовый переулок / Базовый переулок, ~0 м.)

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

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

“ДПС Екатеринбург” (@ekb96dps), 1,812 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/ekb96dps.

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.