Telegram RegisterThe public register of Telegram
Telegram profile photo for ДПС Тверь, Аварии, Правила, ГИБДД. ПДД Авто, мото.

Channel

ДПС Тверь, Аварии, Правила, ГИБДД. ПДД Авто, мото.

@tverdps

Has discussion group

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

9,256subscribers

+404 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002548370766
TypeChannel
Username@tverdps
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 August 2026
Last confirmed live19 October 2026
Measurements held18
Confirmed unchanged1 time, most recently 19 October 2026
On Telegramt.me/tverdps

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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,8529,2569,0547 August 2026 — 8,852 subscribers11 August 2026 — 8,877 subscribers14 August 2026 — 8,867 subscribers17 August 2026 — 8,876 subscribers20 August 2026 — 8,895 subscribers24 August 2026 — 8,895 subscribers24 August 2026 — 8,878 subscribers27 August 2026 — 8,893 subscribers30 August 2026 — 8,909 subscribers2 September 2026 — 8,928 subscribers7 September 2026 — 8,957 subscribers11 September 2026 — 9,011 subscribers14 September 2026 — 9,035 subscribers19 September 2026 — 9,067 subscribers29 September 2026 — 9,138 subscribers13 October 2026 — 9,196 subscribers16 October 2026 — 9,233 subscribers19 October 2026 — 9,256 subscribers7 August 202619 October 2026
18 measurements spanning 73 days, net +404. 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,791–9,317 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Oct 2026, 12:029,256+23
16 Oct 2026, 01:379,233+37
13 Oct 2026, 03:109,196+58
29 Sept 2026, 20:569,138+71
19 Sept 2026, 13:379,067+32
14 Sept 2026, 20:209,035+24
11 Sept 2026, 14:369,011+54
7 Sept 2026, 05:368,957+29
2 Sept 2026, 02:528,928+19
30 Aug 2026, 07:378,909+16
27 Aug 2026, 16:478,893+15
24 Aug 2026, 20:358,878-17
24 Aug 2026, 11:218,895no change
20 Aug 2026, 21:178,895+19
17 Aug 2026, 13:178,876+9
14 Aug 2026, 07:358,867-10
11 Aug 2026, 08:538,877+25
7 Aug 2026, 19:418,852first reading

Engagement

No public post preview. We read this entry on 24 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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

“ДПС Тверь, Аварии, Правила, ГИБДД. ПДД Авто, мото.” (@tverdps), 9,256 subscribers as measured 19 October 2026. Telegram Register, tgregister.com/channel/tverdps.

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.