Channel
@barbarboiler
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
542subscribers
+47 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001422545630 |
|---|---|
| Type | Channel |
| Username | @barbarboiler |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/barbarboiler |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 14:38 | 542 | +47 |
| 7 Aug 2026, 09:35 | 495 | no change |
| 6 Aug 2026, 22:32 | 495 | first reading |
19 posts held, back to 3 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 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 6 August 2026 |
|---|---|
| Posts held | 19 (3 July 2026 – 6 August 2026) |
| Views total | 3,288 |
| Reactions total | 98 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 22:32 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.
165 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 30.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5224460534534916102 | 51 | 30.9% | |
| custom 5373355432800693886 | 44 | 26.7% | |
| custom 5197267593345385327 | 28 | 17.0% | |
| custom 5352784961814405440 | 22 | 13.3% | |
| custom 5206659381151680254 | 18 | 10.9% | |
| custom 5389006967937184376 | 2 | 1.21% |
Custom emoji. Every 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 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 19 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 165reactions 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 3 July 2026 to 6 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.
Приветики! Напомним, что сегодня в Бойлере пройдёт презентация пивоварни Let ME brew! Ребята расскажут вам о себе, о котиках и о вкусном пиве. А также сооснователь пивоварни Михаил дополнительно привезёт на шеринг новенький стаут ❤️ Стартуем в 20:00
custom 53733554328006938863custom 51972675933453853271custom 52244605345349161021
Ну что ж! Уже завтра состоится презентация Let ME brew. Расклад на завтра такой: на краник прыгает Дай мне вишневое и Мятная рыбка. В баночках будем вкушать Хэби, Интриги больше нет, Тангал и Искусство сауэра. Готовьте свои антаппы и хорошее настроение) Старт в 20:00
custom 52244605345349161025custom 53733554328006938863custom 52066593811516802541
Привет, Бойлеровец! В мире существует знаменитое пиво с рыбками, но также существует и не менее прекрасная молодая пивоварня с котиками. И уже в этот четверг ждём этих котиков в Бойлере! В нашем уютном барчике остоится презентация пивоварни Let ME brew: будем пить два сорта с крана и вкушать четыре баночные позиции. Подробнее о трек-листе расскажем на неделе! Когда – 6 августа Во скока – в 20:00 Где – у нас
custom 53733554328006938866custom 52244605345349161022custom 51972675933453853271
Этот день настал!
custom 53733554328006938864custom 51972675933453853271
Ну шо, добро пожаловать в пятницу – потницу. На улице жестокое солнышко, а в баре есть Малиновый Чарли от Пивотеки Брю. Льётся с краника, вкууусный пипец. Так что заходите вкушать, чекинить в тапке и кайфовать)
custom 51972675933453853274custom 53527849618144054404custom 52244605345349161022
Все как обычно, ничего не меняется. Сегодня лагерок за ноль пять – двести пятьдесят рублс)
custom 52244605345349161025custom 53527849618144054401
Сегодня в Бойлере открыты аж две дверки, так что забегайте с двух ног! На кранике льётся Фердинанд 10, потом на замену ему встанет сухой сидр Как с Куста aka Токсовская Сидрерия. Также от Плэйга прыгнул крепыш – Доом Метал, сочный 14% допельбок. Отдаем по 0,3, но и 0,5 можем оформить) С пятницей, Бойлеровчанин!
custom 52244605345349161027custom 51972675933453853271custom 53733554328006938861
Привет! Мы тут ищем бармена поработать/подработать. Все подробности тут @DenisUgl Отправь товарищам, если есть желающие)
custom 51972675933453853278
Бойлеровчане, сегодня вкушаем ГОЗЕШКИ! Дегустация стартует в 20:00! На кону четыре пивоварни (не четыре пивовара), разный уровень кислотности и вкустности. Ждем тебя и еще всех)
custom 52066593811516802544custom 53733554328006938863custom 52244605345349161022
Солевые процедуры! Завтра в баре будет дегустэйшен различных гозешек. Заготовили для вас 5 позиций базовых солененьких элей от разных пивоварен. Будем пробовать, сравнивать и кайфовать. Денег за дегустацию не нужно, просто приходи) Стартуем в 20:00 по Ленинградскому времени!
custom 53733554328006938868custom 51972675933453853272custom 52244605345349161022
Ну чи шо?! Сегодня будет финал ЧМ, мы обычно показываем футбол на полувялом, но сегодня футбик пропустить нельзя! Ну и самое важное, что случается в воскресенье на планете Земля – лагерок по 250₽ в Бойлере!
custom 53527849618144054406custom 53733554328006938863
Хэлоуп! Набрали тут импорта всякого, набрали много. Сидрики от Заповедника в бутылочках приплыли. Также напомним, что под всё вышеперечисленное предлагается божественная кукуруза на гриле, маслицем смазана да в специях обволочена! Креслица на улице вас будут ждать до 20:00, но есть вероятность превратиться на них в яичницу. Го в пятницу!
custom 52066593811516802546custom 51972675933453853271
Showing the 12 most recent of 19 posts we hold for @barbarboiler. 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 — 188,340 of 1,340,412entries 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.
Named by 2 registered channels — 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Канал какого-то Бара” (@barbarboiler), 542 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/barbarboiler.
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.