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 9 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 the other topics.
Growth
61 measurements spanning 92 days, net +5,247. 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 35,944–61,059 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)
Subscribers
Change
6 Nov 2026, 16:31
56,891
-923
5 Nov 2026, 19:15
57,814
-42
4 Nov 2026, 15:56
57,856
-36
3 Nov 2026, 13:00
57,892
-5
2 Nov 2026, 15:16
57,897
-13
1 Nov 2026, 17:31
57,910
-69
31 Oct 2026, 15:36
57,979
-22
30 Oct 2026, 13:08
58,001
-32
29 Oct 2026, 10:30
58,033
-32
28 Oct 2026, 09:57
58,065
-74
27 Oct 2026, 06:44
58,139
-22
26 Oct 2026, 05:27
58,161
+9,338
25 Oct 2026, 05:38
48,823
+8,569
24 Oct 2026, 04:15
40,254
-17
23 Oct 2026, 06:38
40,271
-119
22 Oct 2026, 03:37
40,390
-223
21 Oct 2026, 00:26
40,613
-28
19 Oct 2026, 21:39
40,641
-17
18 Oct 2026, 20:56
40,658
-15
17 Oct 2026, 19:10
40,673
first reading
Engagement
76 posts held, back to 29 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 177 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
21.4%
avg views ÷ 56,891 subscribers
Avg views / post
12,200
16 posts measured
Reaction rate
0.127%
reactions ÷ views · ER floor
Posts in window
17
of 76 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
Window
Rolling 30 days · latest post in window 6 November 2026
Posts held
76 (29 June 2026 – 6 November 2026)
Views total
194,754
Reactions total
247
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Nov 2026, 07:27 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.
What this channel posts
Photos
473
Videos
89
Links
292
Lifetime counters from Telegram’s own channel header, read 7 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
1m 47s
Average length
36s
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
1,182 reactions across 72 posts, in 11 distinct kinds. The most used accounts for 22.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🎉
267
22.6%
🔥
246
20.8%
👍
227
19.2%
❤
222
18.8%
👏
204
17.3%
💯
5
0.423%
🥰
4
0.338%
😍
3
0.254%
😁
2
0.169%
🤬
1
0.085%
🤯
1
0.085%
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 72 of the 76 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 1,182 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 76 most recent posts we hold, published 29 June 2026 to 6 November 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.
Advertising
Ad load
10.5%
8 of 76 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
10,600
over 8 measured posts
Median views · rest
10,900
over 64 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Measured over the 76 most recent posts we hold, published 29 June 2026 to 6 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 17 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Зумер умер после курения вейпа в Забайкальском крае
19-летний парень затянулся фруктовой одноразкой, и ему резко стало плохо — он начал задыхаться и быстро вызвал скорую, его увезли в реанимацию с острой дыхательной недостаточностью
После обследования в местном онкоцентре врачи выявили у него злокачественную опухоль с метастазами в мозге
Врачи боролись за его жизнь несколько дней, но спасти так и не смогли
_______…
⚡️Ночью и утром 3 ноября в Ульяновске прогнозируют туман и гололедицу
Согласно прогнозу «Ульяновского центра по гидрометеорологии и мониторингу окружающей среды», ночью и утром 03 ноября местами по области и в г. Ульяновске ожидается туман с ухудшением видимости 500 м и менее, на дорогах гололедица.
🔥С 0 до 15 градусов: 1 ноября в Ульяновске резко изменится температура
В первый день ноября в области прогнозируется переменная облачность без значительных осадков. Ветер будет слабым и нестабильным, со скоростью 2–7 м/с.
Температурные показатели колеблются от -2 до +13 градусов. В Ульяновске утром ожидается мороз от -7 до -5 градусов, а днем воздух прогреется до +9...+11 градусов.
🔥В пятницу, 31 октября, в Ульяновске прогнозируется ясная и сухая погода. Днем температура поднимется до +11...+13 °C.
По утру кое-где может появиться туман. Ветер будет дуть с юга со скоростью 3–8 м/с.
🔥В Ульяновск спешит волшебный поезд: 17 декабря прибудет Дед Мороз!
РЖД представили путь следования праздничного состава на сезон 2026–2027 годов. Местным жителям подготовят бесплатное развлекательное шоу прямо на сцене поезда. Конкретное время приезда и расписание станут известны позже.
🔥В Цильнинском районе задержали браконьера, который вырубил 11 дубов
Житель Ульяновской области с судимостью решил заготавливать дрова и срубил 11 дубов в лесном массиве возле села Верхние Тимерсяны
Ущерб, причинённый Майнскому лесничеству, превысил 1 миллион рублей. По данному факту начато уголовное расследование из-за незаконной вырубки деревьев.
В Ульяновске ТЭЦ-1 работает круглосуточно, издавая постоянный гул: когда же это прекратится
Жители Засвияжья, центра и северных районов города уже несколько недель страдают от непрекращающегося шума, исходящего от местной ТЭЦ-1, который слышен даже на севере города. По их словам, звук похож на рев взлетающего самолёта, из-за чего у многих болит голова, и невозможно сосредоточиться.
В мэрии и компании «Т Плюс» поясн…
🔥Пенсионерам Ульяновска выплатят пенсии досрочно в пятницу
Тем, кто обычно получает пенсию 25 октября, деньги перечислят на два дня раньше — в пятницу, 23 октября.
Это связано с тем, что обычная дата приходится на воскресенье. Средства будут зачислены на карты в течение всего рабочего дня.
В Ульяновске 32-летняя женщина похитила алкоголь и сразу же реализовала его прохожим
В Железнодорожном районе города задержали 32-летнюю местную жительницу с судимостью. Она вынесла из супермаркета две бутылки спиртного, не оплатив их на кассе.
Похищенный товар женщина незамедлительно продала случайным прохожим на улице, а полученные деньги потратила на собственные нужды. Ущерб магазину составил свыше двух тысяч ру…
ДРУГИЕ КАНАЛЫ И ГОРОДА
⬇️⬇️⬇️
Ставрополь Пятигорск Кисловодск
Телеблог Владивосток
Владивосток Уссурийск Арсеньев
Уссурийск
Телеблог Алтай ( Live )
Алтай Барнаул Бийск
Саратов Энгельс Балаково
Донецк Луганск Мариуполь
Ульяновск - Ульяновская область
Ульяновск Димитровград Саранск
Телеблог Ижевск
Телеблог Удмуртия Live
Удмуртия Ижевск Воткинск
Хабаровск - Хабаровский край
Телеблог Башкортостан ( Live )
Телеблог Стерли…
🗣👂Нужна надёжная реклама на проверенных ресурсах? Обращайтесь, поможем! Множество каналов с актуальными интересными новостями и обширной аудиторией 👍:📱
МОСКОВСКАЯ ОБЛАСТЬ
ТЕЛЕБЛОГ МОСКВА
МОСКВА БАЛАШИХА ПОДОЛЬСК - LIVE
Люберцы Королев Красногорск
Долгопрудный Реутов
Химки Сходня
Домодедово Видное
Ногинск Электросталь Павловский
Королев Мытищи Раменское
Подольск Домодедово Шереметьево
Мытищи
Районы Москвы ЦАО
Мещанс…
❤8👏3🎉2👍1🔥1
Showing the 12 most recent of 76 posts we hold for @ulyanovsxq. 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.
Mentions
Named by 113 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
2
we ourselves saw one of these resolve, at some point
Never seen alive
0
vacant every time we have ever looked
@ulyanovsxq named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@tyumen_2 named in 26 posts, 8 August 2026 – 28 October 2026 · confirmed gone 9 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@perm0 named in 15 posts, 24 September 2026 – 28 October 2026 · confirmed gone 6 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“Ульяновск Димитровград ( Ульяновская область )” (@ulyanovsxq), 56,891 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/ulyanovsxq.
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.