Telegram RegisterThe public register of Telegram
Telegram profile photo for Рубеж «Булат»

Channel

Рубеж «Булат»

@rubezhbulat

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

41subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001949754389
TypeChannel
Username@rubezhbulat
Created16 August 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/rubezhbulat

Growth

417 August 2026 — 41 subscribers10 August 2026 — 41 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. 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 40–42 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 18:3041no change
7 Aug 2026, 19:5841first reading

Engagement

19 posts held, back to 16 August 2023the 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 19 posts for this entry, the most recent from 17 July 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
5
Videos
9
Links
2

Lifetime counters from Telegram’s own channel header, read 10 August 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
8m 15s
Average length
1m 11s

Measured directly from 7 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

245 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 44.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥10944.5%
👍6426.1%
🤯249.80%
🤩166.53%
🕊114.49%
🫡93.67%
83.27%
🥰31.22%
👏10.408%

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

Measured over the 19 most recent posts we hold, published 16 August 2023 to 17 July 2025, 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

17 Jul 2025, 15:41 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

19 Aug 2023, 09:17 UTC537 views22 reactionsread 10 August 2026

Бой окончен! Победа за нами ! Броня наша крепка и танки наши быстрые ⚔️🇷🇺

👍17🔥5

19 Aug 2023, 07:19 UTC723 views24 reactionsread 10 August 2026
Video

⚡️Группа ДРГ похитила гражданских кураторов Со всеми подразделениями мы объединились в объединенную группировку войск и идем в бой! ДРГ выдвинули свои условия , мы на них не согласились. Враг будет разбит! Победа будет за нами !

👍17🔥7

19 Aug 2023, 03:51 UTC483 views11 reactionsread 10 August 2026
Forwarded from @nikvanta_nikvantaVideo

Сегодня на форуме «Рубеж» встретился с Юрием Подолякой У нас была встреча в формате разговора на равных, задал ему несколько вопросов: 1. Где должна закончиться СВО ? В Одессе ? Во Львове ? В Берлине ? 2. Сейчас по всему миру есть вооруженные конфликты, какая вероятность в ближайшие 20 лет начала 3 мировой войны. Ответы на эти вопросы вы увидите в видео. Также я задал вопросы без видео, на счет Запорожского напр

🔥11

19 Aug 2023, 03:30 UTC547 views7 reactionsread 10 August 2026
Photo

‼️Срочно‼️ ❌Сегодня в 6 часов утра прозвучала боевая тревога, по информации были похищены гражданские кураторы. ⚡️Подразделение «Булат» оперативно явилось в точку построения, и готово к выполнению боевого задания!

🔥7

18 Aug 2023, 19:18 UTC426 views14 reactionsread 10 August 2026
Video message

Video message, posted without a caption

🔥13👍1

18 Aug 2023, 09:39 UTC592 views17 reactionsread 10 August 2026
Video

Боец ОТБ «Булат» с позывным «Внук» рассказал нам о батальоне,чьё название наше подразделение носит на Рубеже. В составе батальона два Героя ДНР... посмертно🙏 🕊️Эти истории вызывают неподдельные эмоции и гордость за наших Защитников Донбасса

🕊115👍1

18 Aug 2023, 09:23 UTC405 views15 reactionsread 10 August 2026
Video

🤔Научиться управлять БПЛА или накладывать жгут? Нашим бойцам под силу любые задачи. 💪 Сегодня ребята занимаются на различных локациях тактической подготовки: БПЛА,тактическая медицина, пехота Давайте вместе посмотрим как проходит наш день☺️

👍83🔥2🥰2

18 Aug 2023, 02:54 UTC389 views9 reactionsread 10 August 2026
Video message

Video message, posted without a caption

🤯9

18 Aug 2023, 02:54 UTC365 views8 reactionsread 10 August 2026
Video message

Video message, posted without a caption

🤯8

18 Aug 2023, 02:54 UTC355 views7 reactionsread 10 August 2026
Video message

Video message, posted without a caption

🤯7

17 Aug 2023, 21:15 UTC296 views13 reactionsread 10 August 2026
Photo

Всем спокойной ночи 🌙 На страже бойцы танкового подразделения «Булат»

🔥13

Showing the 12 most recent of 19 posts we hold for @rubezhbulat. 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 — 1,439,309 of 1,548,671entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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.

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

“Рубеж «Булат»” (@rubezhbulat), 41 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/rubezhbulat.

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.