Channel
@ves_ulan
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
2,090subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002285500913 |
|---|---|
| Type | Channel |
| Username | @ves_ulan |
| Description | Все новости нашего города. С нами вы будете в курсе всех событий. |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ves_ulan |
National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 75% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @novosti_bur/62773 Aug 2026, 02:07 UTC | @ves_ulan/6288 · this entry3 Aug 2026, 02:09 UTC | 1.00 | 72 seconds |
| @ves_ulan/6293 · this entry5 Aug 2026, 08:55 UTC | @novosti_bur/62825 Aug 2026, 08:56 UTC | 1.00 | under a minute |
| @ves_ulan/6294 · this entry5 Aug 2026, 08:55 UTC | @novosti_bur/62835 Aug 2026, 08:56 UTC | 1.00 | under a minute |
| @ves_ulan/6297 · this entry5 Aug 2026, 08:55 UTC | @novosti_bur/62865 Aug 2026, 08:56 UTC | 1.00 | under a minute |
| @ves_ulan/6299 · this entry6 Aug 2026, 04:32 UTC | @novosti_bur/62886 Aug 2026, 04:33 UTC | 1.00 | under a minute |
| @ves_ulan/6300 · this entry6 Aug 2026, 04:32 UTC | @novosti_bur/62896 Aug 2026, 04:33 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @novosti_bur | 16 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (12–4) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 1 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @novosti_bur. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 14:48 | 2,090 | no change |
| 7 Aug 2026, 14:31 | 2,090 | first reading |
20 posts held, back to 1 August 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 1 pageof Telegram’s post history, 20 posts per page.
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 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (1 August 2026 – 7 August 2026) |
| Views total | 732 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 14:48 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.
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 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 1reactions 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 1 August 2026 to 7 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.
🌾 58 нарушений при ввозе продукции в Бурятии С начала августа инспекторы Россельхознадзора выявили 58 нарушений при ввозе подкарантинной продукции в Бурятии. Хозяйствующие субъекты не погасили карантинные сертификаты в установленный срок после доставки 972 тонн и 5,3 кубометра продукции. Среди поступивших грузов — фуражная пшеница, пшеничная мука, смесь зерновых и кормовых культур, а также деревянные крепежные мате…
⛽️ Топливо в Бурятии: ситуация стабилизировалась Запасы топлива в республике соответствуют норме. Правительство региона переходит от ежедневного мониторинга к адресной работе, уделяя особое внимание труднодоступным территориям, таким как Окинский и Муйский районы. Логистика туда отрабатывается в «ручном режиме» для обеспечения стабильных поставок.
☀️ 7 августа: приметы и традиции В этот день, известный как Анна Летняя или Анна Холодная, наши предки определяли, какой будет предстоящая зима. Считалось, что с этого дня лето начинает уступать свои позиции, а ночи становятся прохладнее. Праведная Анна почиталась как покровительница беременных и матерей. В этот день не рекомендовалось торговаться, лениться, ссориться и одалживать деньги, чтобы не навлечь финансовы…
🚗 Дорожники Бурятии борются с последствиями дождей В Баунтовском и Еравнинском районах Бурятии дорожные службы работают над поддержанием транспортного сообщения на региональных трассах. На участке Романовка — Багдарин ежедневно отсыпают грунтом проблемные зоны, где из-за дождей и грузовиков образуются колеи и размывы. В Еравнинском районе ликвидированы последствия подтопления на трассе Романовка — Чита. Ранее участ…
🔥 Два новых лесных пожара в Бурятии В Заиграевском районе Бурятии возникли два новых очага возгорания. Один пожар площадью 0,1 гектара зафиксирован в 5 км от поселка Онохой, второй площадью 0,02 гектара — в Хандагатайском лесничестве. На тушение привлечены спасатели, лесники, спецтехника и трактор. Работы продолжаются.
✝️ День Святой Христины 6 августа отмечают день Святой мученицы Христины, пострадавшей за веру в III веке. В народе её почитали как покровительницу девушек и хранительницу домашнего очага. На Руси к этому дню заканчивали уборку ранних зерновых и начинали готовиться к осени. Считалось, что с этого дня ночи становятся холоднее, а утренние туманы предвещают скорое приближение осени. В этот день не рекомендовалось начи…
🏅 Спортсмены из Бурятии победили на чемпионате в Монголии Шесть легкоатлетов из Бурятии завоевали 26 медалей на открытом международном чемпионате по лёгкой атлетике среди ветеранов «Мастерс». Соревнования проходили 1–2 августа в Монголии. В чемпионате приняли участие более 350 спортсменов из Монголии, Казахстана и России.
🇷🇺 Школьник из Бурятии встретился с Путиным Вячеслав Казекин, финалист конкурса «Большая перемена» из Улан-Удэ, встретился с президентом России Владимиром Путиным в Красноярске. Школьник рассказал главе государства о красоте Бурятии, озере Байкал и пригласил его в гости. Президент отметил, что тоже начинал заниматься дзюдо, когда услышал о спортивных достижениях Вячеслава.
🇷🇺 Приглашение Президенту Ученик 8 класса школы №25 Слава Казекин пригласил Владимира Путина посетить Бурятию. Диалог состоялся на финале конкурса «Большая перемена» в Красноярске. Школьник рассказал главе государства о своих спортивных увлечениях и задал вопрос о значении победы. Президент ответил, что самая большая победа — это преодоление самого себя. На предложение посетить Бурятию Владимир Путин ответил, что п…
🚧 В Улан-Удэ засыпали ямы после дождя Коммунальщики использовали 800 тонн щебня для ремонта дорог в микрорайонах Стеклозавод, Дивизионная, Светлый, Радужный и Зверосовхоз. Большинство размывов ликвидировано. Работы на главных магистралях планируют завершить к концу недели. С начала сезона специалисты Комбината благоустройства провели грейдерование на 203 улицах города.
🚨 Камеры "Безопасного города" оказались нерабочими В Еравнинском районе Бурятии прокуроры выявили неисправность камер видеонаблюдения системы «Безопасный город». В селе Телемба изображение с четырех камер не передавалось в участковый пункт полиции. В райцентре Сосново-Озерское пять камер находились в нерабочем состоянии. Нарушения устранены, проведен ремонт.
🏡 Во дворе дома № 25 на улице Партизанской в Улан-Удэ появится новая спортивная площадка. Работы ведутся по программе «Благоустройство дальневосточных дворов». На территории уже обустроили тротуары, установили ограждение, лавочки и урны. Сейчас завершается монтаж освещения и установка игрового оборудования. В 2026 году по этой программе в Улан-Удэ планируется благоустроить пять дворов.
Showing the 12 most recent of 20 posts we hold for @ves_ulan. 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“️️ ️ Весь Улан-удэ ️️️” (@ves_ulan), 2,090 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/ves_ulan.
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.