Channel
@estpoestb
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
4,218subscribers
-51 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001891597085 |
|---|---|
| Type | Channel |
| Username | @estpoestb |
| Created | 12 October 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/estpoestb |
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 13 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 |
|---|---|---|
| 16 Sept 2026, 01:41 | 4,218 | -5 |
| 12 Sept 2026, 04:17 | 4,223 | -8 |
| 8 Sept 2026, 05:57 | 4,231 | -7 |
| 2 Sept 2026, 17:54 | 4,238 | -4 |
| 30 Aug 2026, 14:23 | 4,242 | -6 |
| 27 Aug 2026, 11:14 | 4,248 | -3 |
| 24 Aug 2026, 14:02 | 4,251 | -5 |
| 21 Aug 2026, 05:24 | 4,256 | -3 |
| 18 Aug 2026, 03:53 | 4,259 | -1 |
| 14 Aug 2026, 20:58 | 4,260 | -6 |
| 11 Aug 2026, 06:02 | 4,266 | -3 |
| 7 Aug 2026, 12:33 | 4,269 | no change |
| 7 Aug 2026, 12:23 | 4,269 | first reading |
5 posts held, back to 7 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 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 5 posts for this entry, the most recent from 25 April 2026. An engagement rate over an empty window would be a number about nothing.
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.
291 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 35.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 103 | 35.4% | |
| 👍 | 92 | 31.6% | |
| 🔥 | 45 | 15.5% | |
| 👏 | 29 | 9.97% | |
| 😁 | 10 | 3.44% | |
| 😍 | 8 | 2.75% | |
| 👎 | 4 | 1.37% |
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 5 of the 5 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 5 most recent posts we hold, published 7 October 2025 to 25 April 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.
Готовы к большому гастрономическому улову? В «PRO.Хинкали» пройдет серия гастроужинов, где весна раскрывается через вкус настоящей «грузинской рыбалки». Вода становится прозрачной, вкус — ярче, а рыба — особенно хороша. В меню входит 5 курсов: •Севиче из форели с соусом киндзмари и хрустящей кукурузой •Салат с кефалью, печеным перцем и копченым сулугуни •Люля-кебаб из креветок с соусом чкмерули •Форель в виноградн…
👍9
А много ли вы знаете грузинских рыбных блюд? Хачапури. Хинкали. Харчо. Сациви. Чахохбили. Пхали. Сулугуни… Список можно продолжать долго — но заметили? Рыбы в нём нет. И это не случайно. В стране, зажатой между Чёрным морем и горными реками, рыба веками оставалась в тени мяса и сыра. Её ели там, где ловили — и у каждой региональной рыбной истории оказалось своё лицо. Форель и парадокс «живой рыбы» В холодных горн…
👏17👍11❤8
Угадайте, блюд какой кухни больше всего в Ростове? Итальянской, грузинской или японской? Генацвале, конечно, нам намного ближе, чем самурай или пиццайоло. Если из всех съеденных мной суши-роллов можно построить небольшой грузовик, как в лего, то из съеденных хинкали можно слепить самолёт, в который можно поставить этот грузовик, а из аджарских лодочек сделать три «Титаника». Почему я начал именно с этого? Да потому…
❤52👏12😍5👍4👎2
Кутабы нечасто встретишь в Ростове — это вам не хачапури и не чебурек. Поэтому, когда видишь вывеску «Кутабочная», невольно останавливаешься. Когда-то кутабы были едой пастухов. В степи или в горах, у костра — мука, вода, зелень и камень, нагретый солнцем. Так родился первый кутаб: лёгкий, ароматный, с хрустом по краю и душой внутри. Потом пришёл садж — выпуклая железная пластина, на которой кутабы жарят и сегодня. …
👍54❤24🔥19👎1
Я уже был в “Di Pasta” в «Inside» — там было вкусно, и туда почти невозможно забронировать столик. А теперь на Семашко открылось новое место — в более спокойном, семейном формате. Направляясь туда, я уже знал, о чём расскажу, поэтому без колебаний заказал главного героя сегодняшнего поста — карбонару. И вот тут начинается история блюда, которое вызывает у итальянцев больше эмоций, чем футбол и политика вместе взятые…
🔥26❤19👍14😁10😍3👎1
Showing the 5 most recent of 5 posts we hold for @estpoestb. 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.
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 14 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Есть поесть?!” (@estpoestb), 4,218 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/estpoestb.
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.