Всем привет 🤝 Я жив, цел, дибил. Ко мне приезжал мой близкий человек «Группа Юг» Мы вместе по тусили, но пока что-то выкладывать нет ни ресурса, ни материала Но вы я смотрю ещё не отписались, больные ублюдки
🔥6❤4👍3

Channel
@Bardak_yg
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
47subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003433708996 |
|---|---|
| Type | Channel |
| Username | @Bardak_yg |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Bardak_yg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 18:36 | 47 | +1 |
| 10 Aug 2026, 14:30 | 46 | no change |
| 7 Aug 2026, 17:41 | 46 | first reading |
15 posts held, back to 14 April 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.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 15 (14 April 2026 – 27 July 2026) |
| Views total | 149 |
| Reactions total | 13 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 14:30 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.
Measured directly from 9 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.
227 reactions across 15 posts, in 11 distinct kinds. The most used accounts for 20.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5445205622867900689 | 47 | 20.7% | |
| custom 5442768246107293364 | 44 | 19.4% | |
| custom 5443087564040847705 | 31 | 13.7% | |
| custom 5427250967353525372 | 28 | 12.3% | |
| custom 5188228074461741333 | 23 | 10.1% | |
| custom 5188536186825612589 | 15 | 6.61% | |
| 🔥 | 13 | 5.73% | |
| ❤ | 10 | 4.41% | |
| custom 5188329757812464671 | 9 | 3.96% | |
| custom 5442970148224908991 | 4 | 1.76% | |
| 👍 | 3 | 1.32% |
Custom emoji. 8 of the rows above are 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 counts beside them areTelegram’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 15 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 227reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 14 April 2026 to 27 July 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.
Всем привет 🤝 Я жив, цел, дибил. Ко мне приезжал мой близкий человек «Группа Юг» Мы вместе по тусили, но пока что-то выкладывать нет ни ресурса, ни материала Но вы я смотрю ещё не отписались, больные ублюдки
🔥6❤4👍3
Video message, posted without a caption
custom 54272509673535253727custom 54430875640408477055custom 51885361868256125893
Ну что Съездили мы в Ростов… Изначально мысль была просто с потными мужичками в уединенном лесу шарами помериться, но мы решили приехать заранее и побесоебить в Ростове Ростов классный город, с классными людьми Очень понравился местный вайбик Ну и конечно от меня и ГРУППЫ ЮГ все чуть в ахуе были Таких долбаебов они наверное не видели И пивка попили, и груши поколотили, И ГРУППА ЮГ всосал мне в аэрохоккей И в би…
custom 54452056228679006897custom 51885361868256125893custom 54427682461072933643custom 51882280744617413331custom 54272509673535253721custom 54430875640408477051
Ой «случайно» обронил ШЕВРОН ОТ RTF!!! Извинитесь А так по поездке чуть позже будет обзорчик🫶 😂
custom 54452056228679006896custom 54427682461072933644custom 51885361868256125893
Именно так я добирался до дома. Но путь ещё не закончился😭 Теперь с дома после быстрого душа двигаюсь в другую локацию А по сему можно завтра расскажу про поездку? 😂
custom 54272509673535253726custom 54430875640408477055🔥3custom 51882280744617413331custom 54452056228679006891
Ростов сегодня в безопасности Спи спокойно 😂
custom 54452056228679006897custom 54427682461072933644🔥2custom 51882280744617413331custom 51885361868256125891
Короче ОН сказал, что мы тупые В принципе с чем я согласен И он заставил меня проснуться в 4 утра, чтобы мы поехали в Ростов просветляться в БИБЛИОТЕКУ!!!Ну и пострелять чуть-чуть 🤏 Когда мы зашли, нефоры и ботаны начали шипеть на нас и были в недоумении как нас вообще в библиотеку пустили А ещё у меня бабки на входе нож отобрали😭 😂
custom 54427682461072933648custom 54452056228679006898custom 54430875640408477054❤1custom 51885361868256125891
Ситуация… Все ОН виноват Скотина… 😂
custom 54430875640408477056custom 51885361868256125893custom 54427682461072933643custom 51882280744617413331custom 54272509673535253721
Я заебался и пытался Роскомнадзорнуться Но помимо того, что страйкбольной пидулкой тяжело за двухсотиться Так ещё Она не работает…. 😂
custom 54427682461072933647custom 54430875640408477054custom 54452056228679006893custom 51882280744617413332custom 54272509673535253721
Админ в запое Выйду, че нить напишу 😂
custom 54452056228679006897custom 54427682461072933645❤4
Почему нет постов? Объясню: Потому что я индефицирую себя, как боевой-ударный вертолет «КА-52» Почему не «Апач»? Потому что, импортозамещение Так вот тяжело писать посты, будучи боевым-ударным вертолетом 😂
custom 51882280744617413337custom 54272509673535253726custom 54430875640408477053
Ночь… Дождь… Спорт…. Увидимся ещё через пол года 😂
custom 54427682461072933645custom 54430875640408477053custom 54452056228679006893
Showing the 12 most recent of 15 posts we hold for @Bardak_yg. 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 — 967,247 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.
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.
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.
“Bardak🃏” (@Bardak_yg), 47 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Bardak_yg.
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.