Channel
@gastrohubber
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
5,593subscribers
-89 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001218309642 |
|---|---|
| Type | Channel |
| Username | @gastrohubber |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/gastrohubber |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 14 Sept 2026, 21:58 | 5,593 | -3 |
| 11 Sept 2026, 17:40 | 5,596 | -2 |
| 7 Sept 2026, 12:41 | 5,598 | -19 |
| 2 Sept 2026, 06:13 | 5,617 | -7 |
| 30 Aug 2026, 05:33 | 5,624 | -8 |
| 26 Aug 2026, 22:56 | 5,632 | -3 |
| 24 Aug 2026, 04:22 | 5,635 | -9 |
| 20 Aug 2026, 16:12 | 5,644 | -13 |
| 17 Aug 2026, 12:08 | 5,657 | -17 |
| 14 Aug 2026, 06:13 | 5,674 | -3 |
| 10 Aug 2026, 14:21 | 5,677 | -6 |
| 7 Aug 2026, 18:51 | 5,683 | +1 |
| 7 Aug 2026, 14:01 | 5,682 | no change |
| 7 Aug 2026, 13:55 | 5,682 | first reading |
6 posts held, back to 2 August 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 7 pages 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 6 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
117 reactions across 6 posts, in 10 distinct kinds. The most used accounts for 62.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 73 | 62.4% | |
| 👌 | 11 | 9.40% | |
| 💘 | 8 | 6.84% | |
| 🍓 | 6 | 5.13% | |
| ❤🔥 | 5 | 4.27% | |
| ⚡ | 4 | 3.42% | |
| 🔥 | 4 | 3.42% | |
| 👍 | 3 | 2.56% | |
| 🌭 | 2 | 1.71% | |
| 💔 | 1 | 0.855% |
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 6 of the 6 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 117 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 2 August 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.
Ло-ли-та: кончик языка совершает путь в три шажка вниз по нёбу, чтобы на третьем толкнуться о зубы. Ло. Ли. Та. Когда нам хочется эстетики и киношного вайба, мы идем в «Лолиту», расположенную в отреставрированной исторической усадьбе на Яузе. Недавно шеф-повар Артем Сипугин обновил меню, и теперь здесь можно попробовать бриошь с маслом бер-нуазет и красной икрой (950₽), улетный тартар из тунца с соусом тоннато (950…
❤10🍓6💘4
Миконос есть у нас дома Наш любимый 🇬🇷 ресторан города — это 💯 Meraki (Novikov Group). С греч. слово μεράκι не имеет точного перевода: оно означает делать что-либо с душой, большой любовью, творчеством и полной самоотдачей, вкладывая в работу частичку самого себя. Нам такой подход очень нравится! Интерьер у таверны — в лучших традициях греческого побережья, но лучше занимайте столик на веранде у фонтана — особое уд…
❤12❤🔥5👌3
Не забываем, что осталось всего лишь четыре летних уикенда, и не смеем сидеть дома! 🌊🌊🌊🌊🌊🌊🌊 ❤️🔥Добираемся до долгожданного фестиваля «КРУТО» 🥊 Заказываем ПП-блюда в SUBSTANCE Kebab и забираем сертификат на персональную тренировку в Brothers Boxing Club 🥳 Поздравляем с ДР гастробар «Дневник» и ресторан «НОА» 🍺 Отмечаем День пива в «Бибирево» и «Восходе» 🫶🏽 Собираемся со своими амигос на фиесте в «Проливе» на Таганке…
❤14⚡4👍3💔1
Sound of freedom На днях мы проветривали голову, неспешно скитаясь по центру, и оказались рядом со «Свободой» — легендарной рюмочной, про настойки которой буквально слагают легенды. Проект существует с далекого 2018 года, что по меркам Москвы само по себе заслуживает уважения 💯 Вечером у нас была запланирована очередная рабочая встреча, поэтому алкогольный трип нам не светил, но с каким же кайфом мы объелись 🤤 Как …
❤11🔥4👌1
Voyage Voyage Летом петербургский шеф Александр Богданов («Гельвеция») стал бренд-шефом всех проектов Kuznyahouse, в том числе, наших любимых речных вояжей — Cruise II. Что есть в обновленном меню 🛳️ ? Начали мы с салата с бурратой, томатами, маракуйей и соусом из трав (990₽), затем был паштет из печени индейки с финиками и булочкой бриошь (720₽), хрустящие крокеты с креветкой, угрем и соусом лечо (950₽) и гребешок…
❤9👌3🌭2
Мы едем в Саппоро, оттуда в Осаку, оттуда в Токио В моих карманах иены, они длинные — Пиноккио Лето было создано для двориков, и один из наших 🤍 — это японский татиноми-бар «Тебураси». Повод заглянуть туда мы всегда найдем, будь то отличные коктейли в банках (наш фаворит — #1 с ромом, бананом, маракуйей и саке за 690₽) или обновленное меню от бренд-шефа Макса Кулешова. Среди новеньких закусок, которые удобно шерить…
❤17👌4💘4
Showing the 6 most recent of 6 posts we hold for @gastrohubber. 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.
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 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.
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 8 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“GastroHub” (@gastrohubber), 5,593 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/gastrohubber.
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.