Telegram RegisterThe public register of Telegram
Telegram profile photo for Шеф-поVAR

Channel

Шеф-поVAR

@chefVAR

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

2,054subscribers

+42 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001234452843
TypeChannel
Username@chefVAR
Created23 February 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live8 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/chefVAR

Growth

2,01013,3227,6666 August 2026 — 2,012 subscribers7 August 2026 — 2,012 subscribers10 August 2026 — 2,013 subscribers16 August 2026 — 2,010 subscribers19 August 2026 — 2,020 subscribers23 August 2026 — 13,322 subscribers24 August 2026 — 3,470 subscribers27 August 2026 — 2,290 subscribers30 August 2026 — 2,058 subscribers8 September 2026 — 2,054 subscribers2,0546 August 20268 September 2026
10 measurements spanning 33 days, net +42. 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 313–15,019 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 12:172,054-4
30 Aug 2026, 21:452,058-232
27 Aug 2026, 16:372,290-1,180
24 Aug 2026, 21:063,470-9,852
23 Aug 2026, 09:2713,322+11,302
19 Aug 2026, 17:222,020+10
16 Aug 2026, 06:472,010-3
10 Aug 2026, 12:312,013+1
7 Aug 2026, 17:122,012no change
6 Aug 2026, 17:332,012first reading

Engagement

28 posts held, back to 22 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
54.8%
avg views ÷ 2,054 subscribers
Avg views / post
1,130
7 posts measured
Reaction rate
31.2%
reactions ÷ views · ER floor
Posts in window
7
of 28 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 August 2026
Posts held28 (22 March 202623 August 2026)
Views total7,885
Reactions total2,458
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Aug 2026, 09:43 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.

Reaction mix

3,977 reactions across 27 posts, in 5 distinct kinds. The most used accounts for 82.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎3,26682.1%
👍41410.4%
🤣1904.78%
1062.67%
🙏10.025%

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 27 of the 28 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 3,977 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 28 most recent posts we hold, published 22 March 2026 to 23 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 28 we hold a reading for · 11%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @chefVAR. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 28 most recent posts we hold for this entry, published 22 March 2026 to 23 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

23 Aug 2026, 19:01 UTC626 views475 reactionsread 24 August 2026

На одном дыхании посмотрели прекрасный матч. Танашев справился — хорошая работа. Да и вообще, судьи неплохо вошли в сезон. К слову, у нас без одной игры завершился пятый тур, и процент вмешательств VAR по сравнению с двумя прошлыми годами снизился более чем на 30%. А если добавить сюда тот факт, что мы видим новые судейские лица, которые явно не портят погоду на футбольном поле, то положительная динамика становитс

👎462👍102🙏1

19 Aug 2026, 12:04 UTC≈1,260 views366 reactionsread 24 August 2026

Главный матч выходных между Спартаком и Зенитом доверено судить арбитру из Нальчика – Иналу Танашеву. Помогать ему будут Рустам Мухтаров и Дмитрий Сафьян. @chefVAR

👎341👍212🤣2

18 Aug 2026, 17:55 UTC≈1,310 views421 reactionsread 24 August 2026

Этот кубковый матч ЦСКА - Акрон — худший для судей в новом сезоне. Два опытных видеоарбитра реально вляпались. Отменить вторую жёлтую карточку Хосонову — это, прямо скажем, надо было постараться. Очевидный срыв перспективной атаки, но они решили иначе. Жалко, что Плиско не справился. Не хватило ему стойкости отстоять своё изначально правильное решение. Ещё один антигерой — второй ассистент Туркин. Как можно было с

👎405👍12🤣4

16 Aug 2026, 18:18 UTC≈1,210 views29 reactionsread 24 August 2026
Photo

Балтика - Спартак Если оценивать только стоп-кадр с наступом на голеностоп — это пенальти. Однако, если посмотреть повтор, видно, что наступ никак не влияет на игрока Балтики, который сыграл в мяч, как хотел, и только после этого упал на газон. P.S. Упал бы атакующий сразу после наступа, не сыграв в мяч, — одиннадцатиметровый. Было бы влияние на игровую ситуацию. @chefVAR

👍11🤣11👎7

15 Aug 2026, 17:46 UTC≈1,240 views370 reactionsread 24 August 2026
Photo

Ростов - Рубин Очень похож на момент, который был в матче Краснодар - Факел. Выставил руку вперёд, в соперника. Попал в голову в безрассудной манере – пенальти. @chefVAR

👎362👍8

15 Aug 2026, 16:39 UTC≈1,260 views383 reactionsread 24 August 2026

Думаю, нужно сравнить две ситуации: неназначение пенальти в кубковом матче Краснодар - Ахмат и назначение пенальти в сегодняшнем матче ЦСКА - Факел. Не знаю, что решат в королевстве, сравнивая два этих момента, скажу своё мнение. Мне импонирует неназначение пенальти в Краснодаре – контакт вскользь, он мимолётный, и от этого его сила действительно незначительная. Другое дело – сегодня в Москве. Хоть контакт на камер

👎369👍8🤣42

15 Aug 2026, 14:00 UTC979 views414 reactionsread 24 August 2026
Photo

ЦСКА - Факел Почему VAR пригласил Танашева к монитору, а не принял фактическое решение? Бардачёв не касался мяча, а лишь вступил в единоборство с защитником ЦСКА. В данном случае момент не фактический, а относится к трактовке, следовательно, нужно пригласить судью к монитору. @chefVAR

👎401👍121

8 Aug 2026, 10:56 UTC≈1,590 views538 reactionsread 24 August 2026

Решение ЭСК – понятное. Яркий пример изменения в правилах. Но возникает резонный вопрос: теперь что, вратарь не может отдать мяч ногой партнеру? Передача ногой или касание ногой равны вводу мяча в игру?! Очень тонкая грань, согласитесь. Чтобы не быть палачами, судьям были даны инструкции следующего рода: В случае, подобном этому, когда вратарь (или полевой игрок!) наносит удар по мячу, который неподвижен или почти

👎519👍10🤣63

3 Aug 2026, 12:19 UTC≈4,810 views30 reactions1 Starread 24 August 2026

С удивлением прочитал о том, что VAR не может вмешиваться в ситуации, когда игрок или игроки находятся ближе одного метра к образованной стенке. Нет, это не так. По новым трактовкам VAR может оценить такой момент, и если, по его мнению, это нарушение оказало на игровой эпизод непосредственное влияние, он приглашает арбитра к монитору на предмет нарушения правил атакующим игроком перед голом. В данном случае игроки

👍13👎8🤣72

2 Aug 2026, 17:47 UTC≈8,140 views128 reactions1 Starread 24 August 2026

Нелепый пенальти в ворота Спартака Всё чётко по правилам! По новым правилам! Мяч катится – да. Но по новым правилам атакующая команда получает преимущество в случае, когда мяч введён в игру неправильным образом, как в данном случае – по движущемуся мячу! @chefVAR

👎83👍27🤣153

31 Jul 2026, 10:22 UTC≈2,820 views29 reactions1 Starread 24 August 2026

Опровергаю. По моей информации судьи в Чемпионате России будут действовать следующим образом: В случае симуляции, когда отсутствует контакт между игроками, и судья принимает неправильное решение (например: наказывает защитника жёлтой карточкой, который не коснулся нападающего за пределами штрафной) – VAR вмешиваться не должен. Другой момент, когда есть единоборство и контакт между игроками, и судья наказывает одног

🤣13👍75👎4

25 Jul 2026, 06:52 UTC≈3,110 views63 reactionsread 24 August 2026

ЦСКА - Балтика. Старт нового сезона. https://t.me/aloref/10379 Давайте сразу начнём с ключевого решения судьи Абросимова – просмотра комплексного момента с двумя руками в штрафной гостей. Первое. ВАР правильно показал последовательность повторов. По протоколу он сначала показывает тот инцидент, который является ключевым, в данном случае наказуемое положение руки Гассама – неназначение пенальти. А затем показывает

👎30👍16🤣116

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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.

Mentions

Named by 3 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Алё, рэф!
@aloref · 35,330
Telegram ranks this channel #55 of 100 here — alongside 99 others — read 2 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Шеф-поVAR” (@chefVAR), 2,054 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/chefVAR.

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.