Освежающий кофе☕️ Просто🔥 Да-да, тот самый) У кого ещё жара?🥵 Вам он точно поможет☕️🧊👍 ❇️Ингредиенты: ☕️2 ч л растворимого кофе 🍫2 ч л сахара 💦50 мл воды 🥛100 мл молока 🧊лёд Всем приятного кофепития😄☕️
❤17🔥10👍1

Channel
@chef_orunbai
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Telegram's recommendations · Cite this entry
11,751subscribers
-109 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001500059654 |
|---|---|
| Type | Channel |
| Username | @chef_orunbai |
| Created | Between 1 January 2021 and 31 August 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/chef_orunbai |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 86% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 02:56 | 11,751 | -13 |
| 15 Sept 2026, 19:55 | 11,764 | -6 |
| 14 Sept 2026, 03:15 | 11,770 | -1 |
| 12 Sept 2026, 12:55 | 11,771 | -4 |
| 10 Sept 2026, 07:36 | 11,775 | -8 |
| 7 Sept 2026, 00:39 | 11,783 | -2 |
| 4 Sept 2026, 12:17 | 11,785 | -6 |
| 2 Sept 2026, 23:56 | 11,791 | -2 |
| 31 Aug 2026, 18:56 | 11,793 | -4 |
| 30 Aug 2026, 19:27 | 11,797 | -10 |
| 29 Aug 2026, 19:39 | 11,807 | -8 |
| 28 Aug 2026, 16:02 | 11,815 | -2 |
| 27 Aug 2026, 12:42 | 11,817 | -8 |
| 26 Aug 2026, 16:12 | 11,825 | +1 |
| 25 Aug 2026, 14:24 | 11,824 | -5 |
| 24 Aug 2026, 17:18 | 11,829 | +3 |
| 23 Aug 2026, 04:48 | 11,826 | -2 |
| 21 Aug 2026, 17:57 | 11,828 | -1 |
| 20 Aug 2026, 18:38 | 11,829 | -5 |
| 19 Aug 2026, 15:04 | 11,834 | first reading |
27 posts held, back to 4 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 46 pages of 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 31 August 2026 |
|---|---|
| Posts held | 27 (4 July 2026 – 31 August 2026) |
| Views total | 10,967 |
| Reactions total | 350 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 23:38 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 25 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.
1,609 reactions across 27 posts, in 10 distinct kinds. The most used accounts for 54.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 874 | 54.3% | |
| ❤ | 346 | 21.5% | |
| 👍 | 335 | 20.8% | |
| 💯 | 30 | 1.86% | |
| 👏 | 9 | 0.559% | |
| 🥰 | 6 | 0.373% | |
| 😁 | 5 | 0.311% | |
| 😍 | 2 | 0.124% | |
| 🆒 | 1 | 0.062% | |
| 🤝 | 1 | 0.062% |
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 27 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 1,609 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 4 July 2026 to 31 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.
Освежающий кофе☕️ Просто🔥 Да-да, тот самый) У кого ещё жара?🥵 Вам он точно поможет☕️🧊👍 ❇️Ингредиенты: ☕️2 ч л растворимого кофе 🍫2 ч л сахара 💦50 мл воды 🥛100 мл молока 🧊лёд Всем приятного кофепития😄☕️
❤17🔥10👍1
Купили бы мой авторский чай?☺️
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
🔥16❤2
Привет, Ребята👋 Как проходят ваши выходные?) У нас отличная погодка, последние деньки лета🥹 Поснимали немного, правда, один рецепт не получился, будем переснимать😄 Тут мне ребята чай на пробу прислали, мы попробовали, чай отличный, ароматный такой и вкус насыщенный👍 Они брошюру интересную вложили в коробку с чаем Оказывается, они делают «чайные» коллаборации с разными блогерами😎 И мне предложили🤝 Как думаете, стоит п…
❤17👍12🔥4💯3
Отпадные квашенные помидорчики🍅 ❇️Ингредиенты: Для рассола: 💦2 л воды 🧂Соль 4 ст ложки 🧂Сахар 2 ст ложки 🍎Помидоры 2.5 кг 🌱Листья хрена 🌱Листья вишни 🌱Укроп 🧄Чеснок 3 зубчика 🌶️Острый перец 1 шт 🧂Черный перец горошек 10-12 шт 🌱Лавровый лист 2 шт 🍶Уксус 6 ст ложек 🧂Горчичный порошок 2 ст ложки ❇️Приготовление: -Готовим рассол, на 1 л воды 2 столовых ложки соли, 1 столовая ложка сахара, у меня было 2 литра воды знач…
🔥31❤5
Форель на гриле в исполнении младшего🔥 Ребята, рецепта тут по сути никакого нет, все жарят рыбу, как им нравится☺️ Мы просто посолили, поперчили, добавили паприку, полили маслом и отправили жариться минут на 15-20👌 Главное переворачивайте почаще☝🏻 Надеюсь, смогли поднять вам настроение хоть немного☺️ Всем приятного аппетита😋 👉ПОСМОТРЕТЬ В МАХ
🔥45👍12❤4💯3
И снова я на выезде😎 И снова новый рекорд🔥 158 человек💪
🔥46❤4👍3🆒1
Казан кебаб из говяжьих хвостов🔥 Деликатес подъехал😋 ❇️Ингредиенты: 🥩1,5 говяжьих хвостов 🥔8 картошек 🧅2 лука 🧂По 1 ч л соли и зиры 🍃2 лавровых листа 🍶1 л растительного масла 💦0,5 л воды ❇️Приготовление: -Обжариваем картофель до золотистой корочки и солим его -Затем обжариваем хвосты, также до золотистой корочки -Убираем лишнее масло -Отправляем в казан хвосты, солим их, затем отправляем лук, картошку, наливаем вод…
👍28🔥17❤4💯1
Хашлама🔥 Просто тает во рту🤤 ❇️Ингредиенты: - 5 кг говядины - 4 лука - 1,5 кг картошки - 1 большая головка чеснока - 5 средних болгарских перцев - 2 острых перца - 6 помидор - 100 г сливового масла - щепотка базилика - по 1 ч л чёрного перца и хмели-сунели - соль по вкусу ❇️Приготовление: - Нарезаем мясо на небольшие кусочки, отправляем их в казан, заливаем водой и начинаем варить - Примерно через 30 минут отправля…
🔥44👍16❤3💯1
Ребята, всем привет!👋 После рецепта этих помидоров, поступали сообщения с просьбой оставить рецепт в текстовом формате✏️ Пожалуйста, оставляю😊 Ну а помидоры просто шикарные🔥 От них тяжело оторваться🤪 - 100 г чеснока взбиваем в блендере К нему отправляем 1 острый и 1 болгарский перец и всё это взбиваем Туда же отправляем мелко нарезанный пучок кинзы и пучок укропа Добавляем 1 ч л соли, чёрного перца, паприки и острог…
❤27🔥17👍5💯1
Ребята, всем привет!✊ Готовил тут недавно помидоры-трёхдневки🍅🍅🍅 Это просто отвал бошки🤪 Такие они вкуснячие🤤 Очень рекомендую такие сделать☺️ На видео всё рассказал, показал😜 Всем хорошего дня!☀️ 👉ПОСМОТРЕТЬ В МАХ
❤31🔥18👍6💯1
Несколько фоток с мероприятия☺️ И 1 видео👌🏻 На видео слюни не пускать😄 Рецепт окрошки: - Рыба(сазан)на гриле - Лук маринованный: нарезать лук тоненько на кружочки пол в пол литровую банку, туда же одна чайная ложка соли,сахара и уксуса(9%), заливаем водой и оставляем на пару часов в холодильник - Огурцы из нашего салата к плову - Далее по классике: яйцо,картофель лук зелёный и заливаем квасом Всем хорошего дня!☀️ …
❤20🔥9👍4💯1
Друзья, всем привет👋 Как прошли ваши выходные?) У нас солнечно☀️ и вкусно🤤😋 Показываю, как съездили на фестиваль окрошки☺️ Приготовили вместе с шеф-поваром Дмитрием Выродовым просто сумасшедшую окрошку🤪👍и угостили гостей☺️ Вообщем, было весело😊 Спасибо всем, кто пришел и Дмитрию за приглашение🤝 Надеюсь будем чаще собираться на подобные мероприятия и радовать вас разными вкусняшками😜 Всем хорошей рабочей недели!💪 👉П…
🔥21❤6👍2💯2
Showing the 12 most recent of 27 posts we hold for @chef_orunbai. 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.
@chef_orunbai edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Купили бы мой авторский чай?☺️
Shares as published, totalling 101%. 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 27 most recent posts we hold, published 4 July 2026 to 31 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.
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.
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Кухня Орунбая” (@chef_orunbai), 11,751 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/chef_orunbai.
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.