Telegram RegisterThe public register of Telegram
Telegram profile photo for Минсктранс

Channel

Минсктранс

@minsktrans_official

On this record: Growth · Engagement · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

15,211subscribers

+25 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001159946842
TypeChannel
Username@minsktrans_official
Created31 August 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live18 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/minsktrans_official

Growth

15,18315,22115,2026 August 2026 — 15,186 subscribers6 August 2026 — 15,186 subscribers8 August 2026 — 15,184 subscribers9 August 2026 — 15,183 subscribers10 August 2026 — 15,186 subscribers11 August 2026 — 15,203 subscribers12 August 2026 — 15,206 subscribers14 August 2026 — 15,212 subscribers16 August 2026 — 15,221 subscribers17 August 2026 — 15,213 subscribers18 August 2026 — 15,211 subscribers15,2116 August 202618 August 2026
11 measurements spanning 12 days, net +25. 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 15,177–15,227 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 19:2715,211-2
17 Aug 2026, 18:0815,213-8
16 Aug 2026, 15:5815,221+9
14 Aug 2026, 22:0315,212+6
12 Aug 2026, 07:1715,206+3
11 Aug 2026, 03:5715,203+17
10 Aug 2026, 03:2115,186+3
9 Aug 2026, 02:5115,183-1
8 Aug 2026, 05:4415,184-2
6 Aug 2026, 10:0315,186no change
6 Aug 2026, 09:4915,186first reading

Engagement

147 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 25 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
20.0%
avg views ÷ 15,211 subscribers
Avg views / post
3,050
147 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
147
of 147 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 August 2026
Posts held147 (4 August 202618 August 2026)
Views total447,864
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 18:36 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.

Recent posts

18 Aug 2026, 16:31 UTC≈1,220 viewsread 18 August 2026

Уважаемые пассажиры! В связи со скоплением транспорта на ул. Сурганова движение общественного транспорта осуществляется с нарушением графика до -20 мин

18 Aug 2026, 15:27 UTC≈1,760 viewsread 18 August 2026

С 18.16 на ул. Рафиева, просп. Любимова из-за повреждения контактной сети произошла остановка движения троллейбусов маршрутов № 32,47,53,64 в обоих направлениях. Движение организовано по ул. Есенина, просп. Дзержинского.

18 Aug 2026, 15:22 UTC≈1,770 viewsread 18 August 2026

С 18.04 на ул. Козлова из-за ДТП произошла остановка движения трамваев маршрутов №3,6 в направлении просп. Независимости. Движение организовано по ул. Платонова, ул. З. Бядули.

18 Aug 2026, 14:44 UTC≈2,000 viewsread 18 August 2026

Уважаемые пассажиры! В связи со скоплением транспорта на просп. Машерова, ул. Куйбышева, ул. Киселёва, ул. Козлова движение общественного транспорта осуществляется с нарушением графика до -35 мин

18 Aug 2026, 13:05 UTC≈2,630 viewsread 18 August 2026

С 15.53 на ул. Шаранговича, ул. М. Горецкого из-за ДТП произошла остановка движения троллейбусов маршрутов №7,8,38 в направлении ул. Якубовского, автобусов 50с в направлении ул. Рафиева. Движение троллейбусов организовано по ул. Горецкого, ул. Лобанка, ул. Притыцкого, ул. Бельского, автобусов - по ул. Янковского.

18 Aug 2026, 12:50 UTC≈2,410 viewsread 18 August 2026

С 15.43 до 15.54 на ул. М. Богдановича, просп. Машерова из-за ДТП произошла остановка движения троллейбусов маршрутов №53 в направлении пл. Бангалор.

18 Aug 2026, 10:12 UTC≈2,760 viewsread 18 August 2026

С 13.05 на трассе Р58 перед о.п. "Якубовичи" из-за ДТП произошла остановка движения автобусов на маршрутах № 68,131,337,367,890с в направлении МКАД. Движение организовано по ул. Дзержинского.

18 Aug 2026, 09:16 UTC≈2,830 viewsread 18 August 2026

С 12.09 до 12.22 на ул. Радиальная из-за технически неисправного транспорта произошла остановка движения троллейбусов на маршруте №41 в направлении пл. Круглая.

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

Posts edited after publishing

@minsktrans_official edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
16 August 2026

Citation-graph rank

Citation-graph rank — 247,012 of 1,550,164entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 4 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.

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.

Минск. Главное!
@minsk_gl · 217,349
Telegram ranks this channel #6 of 68 here — alongside 67 others — read 14 August 2026
Мерзкий Кокобай
@koko_by · 111,785
Telegram ranks this channel #41 of 71 here — alongside 70 others — read 14 August 2026
Альфа-Банк (Беларусь)
@alfabankby · 84,100
Telegram ranks this channel #74 of 81 here — alongside 80 others — read 18 August 2026
Onliner
@onlinerby · 148,948
Telegram ranks this channel #80 of 89 here — alongside 88 others — read 12 August 2026

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

“Минсктранс” (@minsktrans_official), 15,211 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/minsktrans_official.

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.