Telegram RegisterThe public register of Telegram
Telegram profile photo for БРИФ КАЛМЫКИЯ

Channel

БРИФ КАЛМЫКИЯ

@briefkalm

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

191subscribers

-2 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-1001966005151
TypeChannel
Username@briefkalm
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/briefkalm

Topic

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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.

Growth

191194192.56 August 2026 — 193 subscribers7 August 2026 — 193 subscribers14 August 2026 — 194 subscribers21 August 2026 — 193 subscribers28 August 2026 — 194 subscribers5 September 2026 — 193 subscribers14 September 2026 — 191 subscribers6 August 202614 September 2026
7 measurements spanning 39 days, net -2. 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 191–194 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 03:55191-2
5 Sept 2026, 17:56193-1
28 Aug 2026, 10:24194+1
21 Aug 2026, 23:55193-1
14 Aug 2026, 04:18194+1
7 Aug 2026, 06:02193no change
6 Aug 2026, 06:23193first reading

Engagement

10 posts held, back to 23 July 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 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

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

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

5 Aug 2026, 13:42 UTC250 viewsread 7 August 2026
Video

5 августа в 12:26 поступило сообщение о возгорании сухой растительности в Элисте между 9-м микрорайоном и Сити-Чессом. По прибытии пожарных наблюдалось горение сухой травы на площади 1 тыс. кв. м. Тушение осложнялось сильным ветром. Для подвоза воды в помощь огнеборцам администрация города направила один водовоз ГЗХ. Возгорание ликвидировано, распространение огня не допущено. Причина пожара и виновные лица устанавл…

5 Aug 2026, 09:38 UTC245 views1 reactionsread 7 August 2026
Photo

5 августа в районе улицы Губкина в Лагани водитель легкового автомобиля не справился с управлением и опрокинулся в кювет. Оказана помощь одному пострадавшему (госпитализирован в Лаганскую районную больницу). @briefkalm

❤1

1 Aug 2026, 09:23 UTC350 viewsread 7 August 2026
Photo

1 августа в 09:08 поступило сообщение о ДТП в 2 км к северу от села Ульдючины. По прибытии спасателей было установлено, что произошло столкновение двух грузовых автомобилей. Огнеборцы произвели отключение аккумуляторной батареи на одном из грузовых автомобилей, а также смыв ГСМ с проезжей части. В результате ДТП пострадал один человек, который был госпитализирован в медицинское учреждение. @briefkalm

31 Jul 2026, 16:56 UTC335 viewsread 7 August 2026
Photo

31 июля в 12:02 поступило сообщение о возгорании сухой растительности в балке Салын. По прибытии огнеборцами наблюдалось горение сухой растительности и покрышек на общей площади 130 кв. м. Возгорание ликвидировано. Причина пожара и виновные лица устанавливаются. @briefkalm

30 Jul 2026, 16:36 UTC372 viewsread 7 August 2026
Photo

В Элисте по ул. Кирова произошло ДТП. @briefkalm

30 Jul 2026, 08:12 UTC349 viewsread 7 August 2026
Video

В Элисте 30 июля в 06:51 произошло возгорание квартиры в жилом доме по ул. Ипподромная. Сотрудники МЧС ликвидировали возгорание на площади 24 кв. м. В результате пожара спасены три человека, двое из них госпитализированы. Кроме того, из дома были эвакуированы 12 жильцов. @briefkalm

26 Jul 2026, 10:38 UTC394 viewsread 7 August 2026
Video

В Элисте 25 июля в районе Астраханского поста сгорела сухая растительность на общей площади 3500 кв. м. Возгорание ликвидировали. Причина пожара и виновные лица устанавливаются. @briefkalm

25 Jul 2026, 07:57 UTC386 viewsread 7 August 2026
Photo

25 июня в 8:12 поступило сообщение о возгорании сухой растительности во 2-м микрорайоне Городовиковска. Пожар был оперативно ликвидирован на площади 70 кв. м. Благодаря своевременным действиям распространения огня удалось избежать. Причина возгорания и виновные лица устанавливаются. @briefkalm

24 Jul 2026, 07:53 UTC330 viewsread 7 August 2026
Photo

23 июля примерно 16:50 на автодороге Р-22 «Каспий» (подъезд к Элисте) 24-летний водитель автомобиля Ford Focus выехал на встречную полосу и столкнулся с грузовым автомобилем Volvo. Водитель Ford погиб на месте. Двое пассажиров легкового автомобиля доставлены в больницу. @briefkalm

23 Jul 2026, 14:04 UTC370 viewsread 7 August 2026
Photo

23 июля в 14:42 поступило сообщение о возгорании камыша в пер. Родниковый в Элисте. К месту вызова незамедлительно были направлены подразделения пожарно-спасательных частей. По прибытии огнеборцы установили, что горит камыш на площади 100 кв. м. Возгорание было оперативно ликвидировано. Причина пожара и виновные лица устанавливаются. @briefkalm

Showing the 10 most recent of 10 posts we hold for @briefkalm. 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.

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.

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

“БРИФ КАЛМЫКИЯ” (@briefkalm), 191 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/briefkalm.

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.