Telegram RegisterThe public register of Telegram

Channel

🇷🇺ᗷᗩᖇᗪᗩK🇷🇺

@bardak34134

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

52subscribers

-1 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-1002289633013
TypeChannel
Username@bardak34134
CreatedBetween 1 September 2024 and 28 December 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/bardak34134

Growth

525352.57 August 2026 — 53 subscribers10 August 2026 — 53 subscribers14 August 2026 — 52 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net -1. 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 52–53 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 12:3852-1
10 Aug 2026, 09:4553no change
7 Aug 2026, 14:1453first reading

Engagement

19 posts held, back to 28 December 2024the 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 31 December 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
13m 29s
Average length
51s

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

25 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1040.0%
👍520.0%
312.0%
👏312.0%
custom 519537767459115025728.00%
👻14.00%
🕊14.00%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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 15 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 25reactions 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 28 December 2024 to 31 December 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.

Recent posts

31 Dec 2024, 07:51 UTC169 views3 reactionsread 10 August 2026
Photo

С наступающим Новым годом 🇷🇺

3

30 Dec 2024, 20:04 UTC163 viewsread 10 August 2026
Forwarded from @bratta17Photo

Официально мой магазин ещё не открыт, но я уже могу отдать чаек по предзаказу. 2 числа буду в Волжском. Кому что нужно - пишите. Прайс и описание в лс) с меня подарочки 🙈

30 Dec 2024, 17:42 UTC188 views0 reactionsread 10 August 2026
Video

Новая часть работы операторов FPV-дронов на оптоволокне в Курской области. 🔊На этот раз в поле зрения дроноводов попал украинский танк, который был немедленно аннигилирован.

30 Dec 2024, 08:58 UTC134 viewsread 10 August 2026
Video

Разгромленная колонна бронетехники украинских формирований на Часовоярском направлении. Лето 2024 года.

30 Dec 2024, 08:14 UTC105 views1 reactionsread 10 August 2026
Video

Бегунку-пешеходу порвали рейтузы Жаль только видеконтроля нет.

🔥1

29 Dec 2024, 15:11 UTC100 viewsread 10 August 2026
Video

Артиллеристы отработали «Градом» по вражеской позиции 📍 Красноармейское направление Расчёт РСЗО БМ-21 «Град» группировки войск «Центр» нанёс артиллерийский удар по пункту управления БпЛА, скоплению живой силы и боевой технике ВСУ.

29 Dec 2024, 14:57 UTC85 viewsread 10 August 2026
Video

Красивая размотка Бредли с десантом и результативные сбросы с Покровского направления

29 Dec 2024, 11:58 UTC76 views2 reactionsread 10 August 2026
Video

Один российский FPV-дрон сорвал ротацию ВСУ в Харьковской области, сообщили в МО.

👍1🔥1

29 Dec 2024, 09:07 UTC79 views2 reactionsread 10 August 2026
Video

Группа Варвара спецназа «Ахмат» разносит позиции вэсэушников в Черкасском Поречном Курской области. На 02:26 — мощный удар по противнику. Командир взвода БПЛА с позывным Ветер рассказал военкору RT Владу Андрице @vandrytsa, что на этом участке идёт работа по обнаружению подвалов, в которых прячется противник, путей подвоза припасов. На 01:26 Ветер показывает, где наши военные вычислили вражеский узел связи. Как т

👍1🔥1

29 Dec 2024, 09:05 UTC73 views3 reactionsread 10 August 2026
Video

Точное попадание – оператор из 132-й мотострелковой бригады 51 гвардейской армии ВС России с ювелирной точностью направил дрон прямо внутрь бронеавтомобиля ВСУ.

👍2🔥1

29 Dec 2024, 08:26 UTC71 views3 reactionsread 10 August 2026
Video

Уничтожение 3-х блиндажей противника силами 2 артиллерийской бригады в 2 км юго-западнее н.п. Белогоровка

🔥2custom 51953776745911502571

29 Dec 2024, 08:18 UTC69 views2 reactionsread 10 August 2026
Video

Мощное огневое воздействие «Гиацинта» Расчет орудия «Гиацинт-Б» группировки войск «Днепр» поразил замаскированную в лесополосе чехословацкую самоходную артиллерийскую установку «Дана» ВСУ на Ореховском направлении.

👏1🕊1

Showing the 12 most recent of 19 posts we hold for @bardak34134. 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

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

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

“🇷🇺ᗷᗩᖇᗪᗩK🇷🇺” (@bardak34134), 52 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/bardak34134.

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.