Channel
@luckygrouprest
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
8,504subscribers
+5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001591107576 |
|---|---|
| Type | Channel |
| Username | @luckygrouprest |
| Description | Lucky Group — ресторанная группа, основанная в 2017 году. Внимание к деталям, чистый вкус и индивидуальность — главные ценности команды. https://lucky-group.rest |
| Created | 11 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/luckygrouprest |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:08 | 8,504 | +8 |
| 9 Aug 2026, 18:12 | 8,496 | -1 |
| 7 Aug 2026, 03:23 | 8,497 | -2 |
| 6 Aug 2026, 10:18 | 8,499 | no change |
| 6 Aug 2026, 10:01 | 8,499 | first reading |
12 posts held, back to 29 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 12 pagesof 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 12 August 2026 |
|---|---|
| Posts held | 12 (29 July 2026 – 12 August 2026) |
| Views total | 16,641 |
| Reactions total | 320 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 16:16 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video 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.
320 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 45.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 147 | 45.9% | |
| custom 5312329187384658078 | 109 | 34.1% | |
| 👍 | 55 | 17.2% | |
| 💔 | 9 | 2.81% |
Custom emoji. One 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 count beside it isTelegram’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 12 of the 12 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 320reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 29 July 2026 to 12 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.
Для бренд-шефа Василия Зайцева утка — больше, чем просто продукт. Любовь к ней давно стала частью истории Koji: от коллекции фигурок, которую годами пополняют гости и друзья ресторана, до главного блюда меню — утки по-пекински. Каждый месяц для гостей готовят почти тысячу килограммов утки. Секрет успеха — тонкая хрустящая кожа и сочное мясо, за которыми возвращаются снова и снова.
❤7👍4custom 53123291873846580784
EVA в прайме! Четвертый ресторан EVA в Москве открылся в жилом квартале Prime Park. Меню от бренд-шефа Бахтияра Шамсиева продолжает гастрономическую историю проекта и объединяет самые узнаваемые блюда. В барной карте — вермуты, хересы и джины, авторские коктейли с травами, специями и цитрусовыми акцентами, в винной подборке — избранные позиции от шеф-сомелье Егора Орлова. А интерьер от Евгении Ужеговой — новый взгля…
❤29custom 531232918738465807814👍6
На этой неделе пробуем новые блюда из сезонных овощей, фруктов и редких морепродуктов в проектах Lucky Group. Неделя «Колхоза номер 1» в Mamie Во французском бистро с 11 по 16 августа пройдет совместный проект с органической фермой «Колхоз номер 1». В течение недели в ресторане будет действовать специальное меню, а 15 августа состоится дачный ужин, во время которого гости смогут попробовать блюда из сезонных продукт…
custom 53123291873846580787❤5👍3
Кроме ножа у хорошего повара есть еще один инструмент — книжная полка. Решили посмотреть, что на ней стоит у шефов Lucky Group. Начинаем с Артемия Лопатина, бренд-шефа Jun, Kiyomi, BUS hand roll bar. В его коллекции — всё, что нужно знать об азиатской кухне: от классики до редких изданий.
custom 531232918738465807810❤9💔2
Мясной Meet me at the market! Последний месяц лета мы посвящаем мясу. Специальный гость предстоящей встречи 16 августа — Виктор Вовчик, сооснователь, управляющий партнёр и идейный вдохновитель кооператива «Старая Корова». Вместе с Иваном Глушковым («Соль»), Евгением Александровым (Bruno и Lucky Place) и Виктором Вовчиком мы отправимся на Преображенский рынок, а затем приготовим обед из выбранных сезонных продуктов …
❤11👍6custom 53123291873846580786
LUCKY DVOR — 8.08 в 22:00!
custom 531232918738465807817❤13
Даже знакомые вкусы могут звучать по-новому — команда Lucky Group запустила серию авторских напитков. Первым стал Lucky Negroni. Вместе с шеф-барменом Максимом Гореликом рассказываем, почему мы выбрали именно этот коктейль и какой получилась его Lucky интерпретация.
custom 531232918738465807818❤15👍7
Врываемся в последний месяц лета. Успеваем прожить эти теплые дни c проектами Lucky Group. Хайбольная среда №7 в BUS hand roll bar 5 августа за баром гостей ждёт Сергей Хохлов из Osso с хайболом Nintendo. Он посвятил напиток одной из самых культовых игр на японской приставке — Super Mario. В этот вечер за виниловый сет отвечает Илья Медведев. Сезонные новинки в Mamie Шеф-повар Тарас Кириенко предлагает попробовать …
❤5👍5custom 53123291873846580783
Дизайнеры и основатели студии Design Aid Татьяна Харченко и Сердар Яников, админы телеграм-канала Tanya&Serdar, — авторы интерьера ресторана Kiyomi. «Зачем буквально воспроизводить чужую культуру — как и чужой интерьер? Гораздо интереснее осмыслить её через призму собственного или близкого нам культурного опыта», — рассказывают Татьяна и Сердар и делятся подробностями, как создавался японский проект Lucky Group.
❤9custom 53123291873846580786👍4
В проектах Lucky Group готовы исполнить самые заветные желания наших гостей. Об одном из таких случаев сегодня рассказывает официант Bruno Дмитрий Бордя. В ресторане «345» была постоянная гостья — Наталья. В одну из пятниц она хотела сесть на веранде. Это был вечер с полной посадкой, на улице уже собралась живая очередь. Гостья заранее написала мне, но в этой суете я не успел посмотреть телефон, а когда она пришла, …
❤35custom 531232918738465807813💔7👍6
Video message, posted without a caption
👍12custom 53123291873846580788❤1
#прямоевключение из ресторана Kiyomi — сегодня вечером здесь пройдет ужин «День мяса». Вместе с бренд-шефом Артемием Лопатиным готовить будет Алексей Каневский, бренд-шеф Dreamteam. В меню — азиатский маринованный ростбиф, нигири с вагю и морским ежом Хоккайдо, вагю стриплойн и другие блюда, в которых мясо играет главную роль.
❤8custom 53123291873846580783👍2
Showing the 12 most recent of 12 posts we hold for @luckygrouprest. 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 — 74,831 of 1,345,403entries 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 4 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.
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 2 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Lucky Group” (@luckygrouprest), 8,504 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/luckygrouprest.
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.