Лисички вышли в сезон, а мы пустили их в дело 🦊 Вы знаете, что делать) до встречи в Цехе!
❤6🔥6😍5

Channel
@GC_TMN72
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Declared links · Cite this entry
280subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003505960384 |
|---|---|
| Type | Channel |
| Username | @GC_TMN72 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/GC_TMN72 |
Ecommerce storefront — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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, 00:59 | 280 | -2 |
| 10 Sept 2026, 01:00 | 282 | +4 |
| 24 Aug 2026, 17:25 | 278 | -3 |
| 17 Aug 2026, 09:23 | 281 | -1 |
| 9 Aug 2026, 03:53 | 282 | no change |
| 8 Aug 2026, 11:49 | 282 | first reading |
14 posts held, back to 14 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
188 reactions across 14 posts, in 13 distinct kinds. The most used accounts for 31.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 60 | 31.9% | |
| ❤ | 29 | 15.4% | |
| ❤🔥 | 27 | 14.4% | |
| 👍 | 12 | 6.38% | |
| 💯 | 12 | 6.38% | |
| 😍 | 10 | 5.32% | |
| 🥰 | 9 | 4.79% | |
| 💔 | 7 | 3.72% | |
| 🤩 | 7 | 3.72% | |
| 💘 | 6 | 3.19% | |
| 😁 | 5 | 2.66% | |
| 👏 | 2 | 1.06% | |
| 😭 | 2 | 1.06% |
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 14 of the 14 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 188 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 14 July 2026 to 7 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.
Лисички вышли в сезон, а мы пустили их в дело 🦊 Вы знаете, что делать) до встречи в Цехе!
❤6🔥6😍5
Если ваш обед это кофе и бутерброд на бегу, нам нужно серьезно поговорить.. Новые обеды от шефа уже ждут вас в Горячем Цехе!🔥
👍5💯3🔥3
В Горячем Цехе появилось горячее место🔥 И нет, не за столиком Мы ищем менеджера, который станет частью нашей команды Что ждёт: 🔥зарплата от 90 000 ₽ 🔥график 2/2 🔥сильная команда Резюме отправляйте на почту: [email protected] или нам в сообщения Опыт работы в аналогичной сфере от года
🔥5❤2
Технологии открытого огня и дух дикой природы: в Горячем Цехе стартовал сезон лисичек! В специальном меню от бренд-шефа сразу три позиции с сезонными грибами: 🔥лепешка из дровяной печи с мятым картофелем и горгонзолой 🔥паста в нежном сливочном соусе из белых грибов 🔥теплый салат с молодым картофелем, зеленью с сырно-имбирным соусом. Сезон лисичек короткий, успейте попробовать в Горячем Цехе❤️🔥
🔥5🥰3💔2
В Тюмени сейчас настоящий квест.. Найти воду. Найти бензин. Поймать связь. С двумя первыми не поможем А вот со связью легко! Возле Горячего Цеха для вас работает бесплатный Wi-Fi❤️🔥 Подключайтесь по QR-коду ниже и оставайтесь на связи
❤🔥4🥰4🔥3
Мы любим огонь А вот с водой предпочитаем не рисковать Видим, что сейчас многих волнует ситуация с водой в городе, поэтому отвечаем сразу на самый частый вопрос Да, мы тоже столкнулись с этой ситуацией. Именно поэтому вся кухня Горячего Цеха работает на бутилированной питьевой воде На ней мы: 🔥моем зелень; 🔥 готовим соусы; 🔥 варим бульоны; 🔥 готовим все блюда нашего меню. Водопроводная вода для приготовления еды …
👍7🔥7❤🔥4
Сегодня последний день акции! Ждём тех кто умеет брать все от этой жизни 🔥
❤🔥5🔥5😁5
24 и 25 июля отмечаем День города в Горячем Цехе🔥 Два вечера вкусной кухни, любимых напитков и атмосферы, в которую хочется возвращаться снова А 25 июля готовим для вас насыщенную программу: 20:00 — Birthday Party 20:30 — Бармен-шоу с огнём и настоящим вау-эффектом 21:10 — Brisket Time Если отмечать День города то красиво! Забронировать стол
❤🔥3🔥2🥰2
Вы сделали невозможное🔥 Мы увидели рекордный интерес к акции, и каждый день ресторан встречал полную посадку Для нас всегда было важно не просто накормить, а сохранить качество блюд и тот уровень сервиса, за которым вы приходите Поэтому мы приняли решение завершить акцию раньше запланированного срока Последний день действия акции 23 июля ❤️🔥 Спасибо каждому, кто стал частью этой истории. Это было по-настоящему …
❤🔥5🔥4💯3😭2
Выбор очевиден! До встречи в Цехе🔥
❤9🔥8👏2
Пока вы думаете, кто-то уже ест любимые блюда со скидкой 50%..
❤7
Video message, posted without a caption
🤩7💘6🔥6
Showing the 12 most recent of 14 posts we hold for @GC_TMN72. 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.
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.
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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. 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.
“ГОРЯЧИЙ ЦЕХ” (@GC_TMN72), 280 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/GC_TMN72.
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.