Telegram RegisterThe public register of Telegram
Telegram profile photo for АвтоДром

Channel

АвтоДром

@why_avtodrom

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

10,818subscribers

-40 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001547486320
TypeChannel
Username@why_avtodrom
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live29 August 2026
Measurements held21
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/why_avtodrom

Growth

10,81610,85810,8377 August 2026 — 10,858 subscribers7 August 2026 — 10,858 subscribers8 August 2026 — 10,856 subscribers9 August 2026 — 10,851 subscribers10 August 2026 — 10,850 subscribers11 August 2026 — 10,852 subscribers12 August 2026 — 10,849 subscribers14 August 2026 — 10,850 subscribers15 August 2026 — 10,847 subscribers17 August 2026 — 10,844 subscribers18 August 2026 — 10,841 subscribers19 August 2026 — 10,840 subscribers20 August 2026 — 10,838 subscribers21 August 2026 — 10,836 subscribers22 August 2026 — 10,832 subscribers24 August 2026 — 10,824 subscribers25 August 2026 — 10,818 subscribers26 August 2026 — 10,816 subscribers27 August 2026 — 10,817 subscribers28 August 2026 — 10,820 subscribers29 August 2026 — 10,818 subscribers10,8187 August 202629 August 2026
21 measurements spanning 23 days, net -40. 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 10,810–10,864 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
29 Aug 2026, 20:2810,818-2
28 Aug 2026, 16:5510,820+3
27 Aug 2026, 16:2810,817+1
26 Aug 2026, 16:5310,816-2
25 Aug 2026, 15:5310,818-6
24 Aug 2026, 13:0910,824-8
22 Aug 2026, 19:3810,832-4
21 Aug 2026, 11:1510,836-2
20 Aug 2026, 09:4710,838-2
19 Aug 2026, 09:2710,840-1
18 Aug 2026, 06:2310,841-3
17 Aug 2026, 09:4610,844-3
15 Aug 2026, 20:4310,847-3
14 Aug 2026, 09:4810,850+1
12 Aug 2026, 05:2710,849-3
11 Aug 2026, 08:3210,852+2
10 Aug 2026, 05:2210,850-1
9 Aug 2026, 04:1110,851-5
8 Aug 2026, 02:2610,856-2
7 Aug 2026, 05:0410,858first reading

Engagement

65 posts held, back to 28 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 38 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.09%
avg views ÷ 10,818 subscribers
Avg views / post
226
58 posts measured
Reaction rate
0.168%
reactions ÷ views · ER floor
Posts in window
58
of 65 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 5 of 58 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 29 August 2026
Posts held65 (28 July 202629 August 2026)
Views total13,094
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 12:25 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.

Reaction mix

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.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 65 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

29 Aug 2026, 09:06 UTC36 viewsread 29 August 2026
Photo

Какое авто имеет приоритет ? 1 Красное авто 2 Синее авто

28 Aug 2026, 17:06 UTC87 viewsread 29 August 2026
Photo

На каком рисунке разворот будет без нарушения ПДД ? 1 А 2 Б 3 В

28 Aug 2026, 09:06 UTC127 viewsread 29 August 2026
Photo

Запрещена ли водителю грузового автомобиля остановка в этом месте? 1 Запрещена 2 Запрещена, если расстояние между автомобилем и линией разметки менее 3 м 3 Разрешена

27 Aug 2026, 17:06 UTC154 viewsread 29 August 2026
Photo

Можно ли Вам после опережения грузового автомобиля продолжить движение по левой полосе вне населенных пунктов? 1 Можно 2 Можно, если Вы управляете междугородним автобусом 3 Нельзя

27 Aug 2026, 09:06 UTC162 viewsread 29 August 2026
Photo

По какой траектории разворот будет без нарушения ПДД ? 1 А 2 Б 3 В

26 Aug 2026, 17:06 UTC164 viewsread 29 August 2026
Photo

Будет нарушением ПДД поворот красным авто по предложенной траектории? 1. Да 2. Нет

26 Aug 2026, 09:06 UTC168 viewsread 29 August 2026
Photo

По какой траектории Вам разрешается продолжить движение? 1 Только по А 2 Только по Б 3 По любой из указанных

25 Aug 2026, 17:06 UTC168 viewsread 29 August 2026
Photo

Разрешено ли Вам выполнить разворот в этом месте? 1 Разрешено 2 Разрешено, если при этом не будут созданы помехи движению маршрутных транспортных средств 3 Запрещено

25 Aug 2026, 09:06 UTC163 viewsread 29 August 2026
Photo

Какое авто будет виновато в ДТП? 1. Красное 2. Синее

24 Aug 2026, 17:06 UTC173 viewsread 29 August 2026
Photo

К нам поступил интересный вопрос от подписчика: Как следует двигаться транспортному средству, которое не способно развивать скорость более 30 км/ч, чтобы не нарушить ПДД РФ на перекрестке? 1. По красной траектории. 2. По синей траектории. 3. По зелёной траектории. 4. Движение через перекресток запрещено. 5. Напишите свой вариант ответа!

24 Aug 2026, 09:06 UTC161 viewsread 29 August 2026
Photo

Нарушил ли Водитель Автопоезда требования пункта 8.6 ПДД РФ? 1. Нарушил. 2. Не Нарушил. 3. Свой вариант ответа в комментариях.

23 Aug 2026, 17:05 UTC158 viewsread 29 August 2026
Photo

Разрешено ли Вам после опережения первого автомобиля продолжить движение по левой полосе вне населенных пунктов? 1 Разрешено 2 Разрешено, если Вы намерены опередить второй автомобиль 3 Запрещено

Showing the 12 most recent of 65 posts we hold for @why_avtodrom. 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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“АвтоДром” (@why_avtodrom), 10,818 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/why_avtodrom.

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.