Telegram RegisterThe public register of Telegram

Channel

Миноблавтотранс

@moat_t

On this record: Growth · Engagement · Reactions · Posts · Citations · Referenced elsewhere · Cite this entry

900subscribers

+3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001777080753
TypeChannel
Username@moat_t
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/moat_t

Growth

897900898.56 August 2026 — 897 subscribers6 August 2026 — 897 subscribers12 August 2026 — 900 subscribers6 August 202612 August 2026
3 measurements spanning 6 days, net +3. 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 897–900 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 20:44900+3
6 Aug 2026, 14:18897no change
6 Aug 2026, 10:45897first reading

Engagement

20 posts held, back to 20 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
97.1%
avg views ÷ 900 subscribers
Avg views / post
874
20 posts measured
Reaction rate
0.249%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 20 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 6 August 2026
Posts held20 (20 July 20266 August 2026)
Views total17,478
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 14:18 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

19 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 47.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
947.4%
👍421.1%
😢421.1%
🔥210.5%

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

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

6 Aug 2026, 08:16 UTC298 views2 reactionsread 6 August 2026

С 10.08.2026 на междугородном маршруте № 500Э Минск – Борисов учреждается выполнение дополнительного промежуточного остановочного пункта "Магистральная" в прямом и обратном направлениях. Расписание движения указанного маршрута будет доступно на сайтах ticketbus.by, infobus.by, transport-by.app или в мобильном приложении "Транспорт BY". Учитывайте указанную информацию при планировании своих поездок.

👍2

5 Aug 2026, 07:26 UTC435 viewsread 6 August 2026

09.08.2026 в связи с проведением в г. Вилейка "Уха-фест" организуется выполнение городских рейсов по маршрутам № 15 Центральная площадь - Маковье временем отправления от о.п. "Центральная площадь" в 00:50 , № 1в Маковье - Водохранилище - Веры Хоружей временем отправления от о.п. "Маковье" в 01:05, № 1 Веры Хоружей - Маковье (старое) временем отправления от о.п. "Веры Хоружей" в 01:45, № 16 Центральная площадь - Оранж

4 Aug 2026, 14:07 UTC407 views1 reactionsread 6 August 2026

🚌 В целях улучшения транспортного обслуживания жителей Мядельского района с 10.08.2026 на рейсах по маршрутам №№ 316аС/300бС Мядель - Будслав отправлением от АВ Мядель в 14:05 и отправлением из Будслава в 07:20 по вторникам организуется заезд на остановочные пункты "Мацки", "Новики", "Пильковщина". Расписание движения указанного маршрута будет доступно на сайтах ticketbus.by, infobus.by, transport-by.app или в мобиль

👍1

4 Aug 2026, 11:50 UTC≈3,010 viewsread 6 August 2026

С 21:00 04.08.2026 по 05:20 05.08.2026 на разворотном кольце на ул. Славинского (АС Славинского) будут проводиться работы по устройству верхнего слоя асфальтобетонного покрытия. В период проведения работ для пригородных маршрутов №№ 310 Минск - Дубровка, 353 Минск - Прудище, 362 Минск - Липовая Колода, 386б Минск - Дачи Городище, 402 Минск - Нелидовичи, 412 Минск - Жуковка, 451 Минск - Логойск, 465С Минск - Мочаны, 8

3 Aug 2026, 08:50 UTC≈1,350 views2 reactionsread 6 August 2026

С 07.08.2026 на пригородном маршруте №202С Марьина Горка - Веркалы через Руденск учреждается выполнение дополнительного промежуточного остановочного пункта "Вендеж" в прямом и обратном направлениях. Расписание движения указанного маршрута будет доступно на сайтах ticketbus.by, infobus.by, transport-by.app или в мобильном приложении "Транспорт BY". Учитывайте указанную информацию при планировании своих поездок.

🔥2

31 Jul 2026, 11:53 UTC684 views1 reactionsread 6 August 2026

🚌В целях улучшения транспортного обслуживания г. Борисов с 01.08.2026 в экспериментальном порядке сроком на 2 месяца в работу городских автобусных маршрутов вносятся следующие изменения: - отменяется выполнение рейсов по маршруту № 27 Вокзал - Лядище через Чаловской временем отправления в 19:34, 21:10, 22:20, 23:10 от о.п. «Вокзал» и в 20:04, 21:40, 22:45, 23:40 от о.п. «Лядище» по будним дням; - организуется выполн

1

31 Jul 2026, 08:31 UTC662 viewsread 6 August 2026

🚌В целях улучшения транспортного обслуживания г. Борисов с 01.08.2026 в экспериментальном порядке сроком на 2 месяца организуется выполнение дополнительных рейсов по маршруту № 8 Лядище – Рынок : - в 19:30 от остановочного пункта «Рынок», в 19:50 от остановочного пункта «Лядище» по будним дням; - в 16:05, 16:47, 17:35 от остановочного пункта «Рынок», в 16:26, 17:08, 17:52 от остановочного пункта «Лядище» по выходным

31 Jul 2026, 07:43 UTC638 viewsread 6 August 2026

С целью изучения спроса населения на перевозку пассажиров с 17.08.2026 по 16.10.2026 организуется выполнение рейсов по пригородному маршруту № 235С Дзержинск - Сосновый Бор через Безодницу временем отправления от АК Дзержинск в 06:30, 17:20, и от остановочного пункта "Сосновый Бор" в 07:05, 17:55 по будним дням Расписание движения указанного маршрута будет доступно на сайтах ticketbus.by, infobus.by, transport-by.app

31 Jul 2026, 06:40 UTC590 viewsread 6 August 2026

С 01.08.2026 вместо рейсов по пригородному маршруту № 221С Молодечно - Радошковичи через Граничи временем отправления от АВ Молодечно в 10:50, и от остановочного пункта "Радошковичи" в 15:00 организуется выполнение рейсов по маршруту № 221аС Молодечно - Радошковичи через Раевщину, Чисть, Граничи временем отправления от АВ Молодечно в 10:45, и от остановочного пункта "Радошковичи" в 15:00 по будним дням. Расписание д

31 Jul 2026, 06:36 UTC520 viewsread 6 August 2026

С 01.08.2026 на пригородном маршруте № 247С Молодечно - Радошковичи через Сычевичи учреждаются дополнительные промежуточные остановочные пункты "Раевщина", "Куромшичи", Выверы" в обоих направлениях. Расписание движения указанного маршрута будет доступно на сайтах ticketbus.by, infobus.by, transport-by.app или в мобильном приложении "Транспорт BY". Учитывайте указанную информацию при планировании своих поездок.

30 Jul 2026, 11:47 UTC642 views4 reactionsread 6 August 2026

🚌В целях улучшения транспортного обслуживания г. Борисов с 01.08.2026 в экспериментальном порядке сроком на 2 месяца в работу городского автобусного маршрута № 7 Вокзал – Дымки вносятся следующие изменения: – отменяется выполнение рейсов временем отправления в 18:20 от остановочного пункта (далее – о.п.) «Вокзал», в 18:35 от о.п. «Дымки» ежедневно; – организуется выполнение рейсов временем отправления в 07:18, 08:10,

4

29 Jul 2026, 11:25 UTC≈1,600 views1 reactionsread 6 August 2026

С 01.08.2026 на пригородном маршруте №224Э Марьина Горка - Дружный учреждается выполнение дополнительного промежуточного остановочного пункта "Скобровка" в прямом и обратном направлениях. Расписание движения указанного маршрута будет доступно на сайтах ticketbus.by, infobus.by, transport-by.app или в мобильном приложении "Транспорт BY". Учитывайте указанную информацию при планировании своих поездок.

👍1

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

Citation-graph rank

Citation-graph rank — 733,269 of 1,480,688entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel — 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.

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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Жодино (ru.wikipedia.org)
“…ccess-date=2024-04-02|url-status=live}}{{Cite web|url=https://t.me/moat_t/283|title=Первый рейс выполнен!|lang=ru|website=Telegram|access-d…”
read 9 August 2026

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

“Миноблавтотранс” (@moat_t), 900 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/moat_t.

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.