Telegram RegisterThe public register of Telegram
Telegram profile photo for Ресторанный Бэкстейдж

Channel

Ресторанный Бэкстейдж

@waiterdiary

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

6,227subscribers

-10 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001575909358
TypeChannel
Username@waiterdiary
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/waiterdiary

Growth

6,2206,2536,236.56 August 2026 — 6,237 subscribers6 August 2026 — 6,240 subscribers10 August 2026 — 6,234 subscribers13 August 2026 — 6,228 subscribers17 August 2026 — 6,220 subscribers20 August 2026 — 6,247 subscribers23 August 2026 — 6,253 subscribers26 August 2026 — 6,244 subscribers29 August 2026 — 6,252 subscribers2 September 2026 — 6,241 subscribers6 September 2026 — 6,227 subscribers6,2276 August 20266 September 2026
11 measurements spanning 31 days, net -10. 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 6,215–6,258 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 05:226,227-14
2 Sept 2026, 03:456,241-11
29 Aug 2026, 18:386,252+8
26 Aug 2026, 14:376,244-9
23 Aug 2026, 23:266,253+6
20 Aug 2026, 16:136,247+27
17 Aug 2026, 10:236,220-8
13 Aug 2026, 09:566,228-6
10 Aug 2026, 04:456,234-6
6 Aug 2026, 23:306,240+3
6 Aug 2026, 09:056,237first reading

Engagement

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

ERR · 30 days
8.36%
avg views ÷ 6,227 subscribers
Avg views / post
521
3 posts measured
Reaction rate
1.73%
reactions ÷ views · ER floor
Posts in window
3
of 23 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 11 August 2026
Posts held23 (10 July 202611 August 2026)
Views total1,562
Reactions total27
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:33 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

278 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 45.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12645.3%
❤‍🔥5921.2%
💯3111.2%
👍227.91%
👌186.47%
🔥93.24%
😁51.80%
👻41.44%
🥰31.08%
🍓10.36%

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

Measured over the 23 most recent posts we hold, published 10 July 2026 to 11 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.

Recent posts

11 Aug 2026, 11:59 UTC382 views15 reactionsread 12 August 2026

Есть официанты, которых гости запоминают не потому, что они были супер-яркими. А потому что рядом с ними было спокойно и понятно. И это, если честно, очень сильная штука. Потому что хороший сервис, это когда у гостя не остается поводов нервничать. 🙂

10❤‍🔥5

9 Aug 2026, 11:59 UTC556 views12 reactionsread 12 August 2026

Каждое воскресенье немного про одно и то же... То плотный поток, то форс-мажоры, то смешные ситуации, которые уже не смешные в моменте, но потом точно войдут в истории. И где-то между всем этим еще умудряешься держать качество, настроение и рабочий ритм. Это, кстати, уже немало. Не каждая неделя проходит красиво, но далеко не каждая и должна. Хорошего всем воскресенья. Отдыхайте, вы это заслужили.🤎

❤‍🔥111

6 Aug 2026, 11:59 UTC738 views21 reactionsread 12 August 2026

Если бармен держит стойку спокойно, то и весь зал как будто начинает дышать ровнее. Странно, но это работает почти всегда. В нашем заведении ситуация была именно такой, достаточно было взглянуть на него, чтобы испытать чувство успокоения. 😌

💯137🍓1

5 Aug 2026, 11:59 UTC795 views20 reactionsread 12 August 2026

Иногда в смене не нужен герой. Нужен человек, который просто сделал все вовремя, без лишнего шума и с уверенным лицом. Вот и весь секрет. Что думаете?🙂

16💯4

2 Aug 2026, 11:59 UTC895 views11 reactionsread 12 August 2026

Воскресенье, 2 августа На календаре 2 августа. Для кого-то сегодня праздник и выходной, а для общепита, очередное августовское воскресенье с полной посадкой и открытыми верандами. Всех причастных, с праздником! А всей рабочей команде сегодня, спокойного потока чеков, нормального темпа на отдаче и адекватных гостей. Тем, кто уже отработал или сегодня отдыхает, хорошего вечера и перезагрузки! Делитесь в комментариях

5❤‍🔥4🔥2

1 Aug 2026, 11:59 UTC958 views22 reactionsread 12 August 2026

Первая чашка кофе за 10 минут до открытия ☕️ В этом коротком моменте есть своя магия. На кухне тишина, все в заготовках, плиты греются, а заведение еще закрыто. Чистый дзен перед тем, как вылетит первый чек и начнётся суета. Есть у вас свои личные ритуалы перед стартом смены, чтобы настроиться? Делитесь!

22

31 Jul 2026, 14:04 UTC871 views1 reactionsread 12 August 2026
Forwarded from @restobiz_stbovPoll

НАСКОЛЬКО У ВАС АВТОМАТИЗИРОВАНА АНАЛИТИКА В РЕСТОРАНЕ?

  1. Всё в тетрадке или Excel (считаем вручную раз в месяц)14%
  2. Базовые отчеты из POS (смотрим только общую выручку и фудкост)27%
  3. Собран полный дашборд (P&L, ФОТ, запасы и чек в реальном времени)28%
  4. Аналитику ведет управляющий45%

The shares total 114%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

🔥1

31 Jul 2026, 14:04 UTC848 views1 reactionsread 12 August 2026

Все привет! В моем втором канале опрос небольшой вышел, кто заинтересован, может поучаствовать 🙂

🔥1

30 Jul 2026, 11:59 UTC943 views13 reactionsread 12 August 2026

Где, как вы думаете, незаметно улетают деньги ресторана? Самая частая дыра в бюджете кухни, это вовсе не воровство, а банальный хаос в маркировке и несоблюдение правила FIFO (первым пришел — первым ушел). Когда на заготовку не ставят дату и время, половина продукта тихо уезжает в ведро просто потому, что перестраховались и выкинули «сомнительное». Порядок в маркировках и стикерах, это не бюрократия, а живые деньги

👌11❤‍🔥2

28 Jul 2026, 11:59 UTC980 views23 reactionsread 12 August 2026

«Ну вы скоро там? Гость торопится!» ⏱️ Я думаю, у каждого повара после такого, начинает тихо дергаться глаз. На самом деле половина конфликтов между залом и кухней лечится элементарно, официант предупреждает о заезде большой компании до того, как выбьет 10 чеков подряд, а кухня не орёт, а даёт реальное время отдачи. Налаженный контакт между залом и плитой, это минус 50% сожженных нервов за смену. Проверено годами.

👍22🔥1

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

Polls

The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

31 Jul 2026, 14:04 UTCAnonymous Poll71 voters

НАСКОЛЬКО У ВАС АВТОМАТИЗИРОВАНА АНАЛИТИКА В РЕСТОРАНЕ?

  1. Всё в тетрадке или Excel (считаем вручную раз в месяц)14%
  2. Базовые отчеты из POS (смотрим только общую выручку и фудкост)27%
  3. Собран полный дашборд (P&L, ФОТ, запасы и чек в реальном времени)28%
  4. Аналитику ведет управляющий45%

The shares total 114%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

23 Jul 2026, 11:59 UTCAnonymous Quiz324 voters

Горячее, долго томится. Соус густой, на основе вина. В составе: говядина, бекон, грибы, лук.

  1. Гуляш19%
  2. Бёф бургиньон49%
  3. Оссобуко21%
  4. Рагу11%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

15 Jul 2026, 11:59 UTCAnonymous Quiz337 voters

Холодное, жидкое, красное. В составе: помидоры, перец, лук, чеснок, оливковое масло, уксус. Подаётся с кубиками хлеба и иногда с морепродуктами сверху.

  1. Италия46%
  2. Испания37%
  3. Грузия12%
  4. Япония4%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 23 most recent posts we hold, published 10 July 2026 to 11 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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 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.

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.

Работа в Restor Horeca.ru
@RestorHoreca · 31,608
Telegram ranks this channel #46 of 79 here — alongside 78 others — read 6 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“Ресторанный Бэкстейдж” (@waiterdiary), 6,227 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/waiterdiary.

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.