Channel
@Belarus_My
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
75subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001252691928 |
|---|---|
| Type | Channel |
| Username | @Belarus_My |
| Description | 🇧🇾🇧🇾🇧🇾Мы за МИРНУЮ, СИЛЬНУЮ и ПРОЦВЕТАЮЩУЮ Беларусь!!!🇧🇾🇧🇾🇧🇾 |
| Created | 1 September 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Belarus_My |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 21:15 | 75 | no change |
| 6 Aug 2026, 09:49 | 75 | first reading |
10 posts held, back to 2 August 2024 — 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.
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 29 August 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
19 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 31.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6 | 31.6% | |
| ❤ | 5 | 26.3% | |
| 👎 | 4 | 21.1% | |
| 🔥 | 2 | 10.5% | |
| 👏 | 1 | 5.26% | |
| 🤔 | 1 | 5.26% |
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 8 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 19reactions 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 2 August 2024 to 29 August 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
75 лет назад, 29 августа 1949, на Семипалатинском полигоне были проведены первые испытания советской атомной бомбы РДС-1. Разработана она была в Лаборатории №2 (ныне Курчатовский институт) под руководством И. В. Курчатова и КБ-11 (ныне Всероссийский научно-исследовательский институт экспериментальной физики) под руководством Ю. Б. Харитона. Обозначение РДС-1 расшифровывалось как "Реактивный двигатель С" в варианте с …
👎2❤1👏1
78 лет назад, 26 августа 1946 года, приказом министра вооружения СССР Д. Ф. Устинова в составе НИИ-88 был создан отдел №3 Специального Конструкторского Бюро. Возглавил отдел С. П. Королёв. Его задачей было создание баллистических ракет. Первая из них, Р-1, полетела осенью 1948 года. Она разрабатывалась на базе немецкой Фау-1, но постепенно на свет стали появляться собственные оригинальные конструкции. 21 августа 1957…
❤2👎1
Обратный отсчет 85 лет назад в Третьем Рейхе уже, если можно так выразиться, нажали "шнеллер" спускового крючка (штука такая, позволяющая уменьшить усилие спуска) мирового конфликта. Оставалось уже мягонько нажать на спуск. Утром 25 августа старый додредноут "Шлезвиг-Гольштейн" вошел в Данциг и встал на якорь рядом с Вестерплятте. На борту у него был морской штурмовой отряд (225 человек). К 25 августа 1939 г. из 58…
❤1👍1👎1
Обратный отсчет 85 лет назад Европа доживала последние мирные дни перед колоссальных масштабов конфликтом, который будет ее сотрясать в течение почти шести лет. Решения были уже приняты. Главнокомандующему сухопутных войск Вальтеру фон Браухичу и Начальнику Генерального штаба Францу Гальдеру Гитлер заявил: «Время будет в целом работать против нас, если мы не сумеем всемерно использовать его. Экономические средства…
👍1
Завтра предстоит очистка ВЛД (верхней лобовой детали) от земли, поиск серийного номера, чтобы пробить по документам закрепление героев-танкистов.
👍1🤔1
Предположительно эта же машина в 1941-м году.
❤1👍1
Photo, posted without a caption
И опять же, только для подписчиков группы!
👍2
Photo, posted without a caption
Cимволично, что 2 августа новый поиск Т-34 образца 1940 года.
🔥2
Showing the 10 most recent of 10 posts we hold for @Belarus_My. 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 — 1,158,734 of 1,481,217entries 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“V Беларусь Z Сильная 🇧🇾🇧🇾🇧🇾🇧🇾🇧🇾🇧🇾🇧🇾🇧🇾” (@Belarus_My), 75 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Belarus_My.
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.