Channel
@httpsorange_food_blog_laif
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
3,225subscribers
-6 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001923436543 |
|---|---|
| Type | Channel |
| Username | @httpsorange_food_blog_laif |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/httpsorange_food_blog_laif |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 17 Sept 2026, 21:00 | 3,225 | -6 |
| 13 Sept 2026, 18:21 | 3,231 | -4 |
| 10 Sept 2026, 10:39 | 3,235 | -5 |
| 5 Sept 2026, 05:57 | 3,240 | +3 |
| 1 Sept 2026, 15:16 | 3,237 | -1 |
| 30 Aug 2026, 01:29 | 3,238 | +6 |
| 26 Aug 2026, 18:13 | 3,232 | +1 |
| 25 Aug 2026, 21:00 | 3,231 | no change |
| 25 Aug 2026, 20:45 | 3,231 | first reading |
10 posts held, back to 21 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 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 10 posts for this entry, the most recent from 25 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 6 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.
169 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 42.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 72 | 42.6% | |
| 🔥 | 32 | 18.9% | |
| 👏 | 31 | 18.3% | |
| 👍 | 30 | 17.8% | |
| 💋 | 1 | 0.592% | |
| 💘 | 1 | 0.592% | |
| 🕊 | 1 | 0.592% | |
| 🙏 | 1 | 0.592% |
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 10 of the 10 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 169 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 21 August 2026 to 25 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 шт Сметана 2 ст л Сыр 50 гр Соль, паприка Мука 3 ст л - Кабачки нарезать фигурным ножом, так они лучше прожариваются и кляр держится намного лучше. Для кляра смешать яйца, сметану, сыр на мелкой тёрке, соль, паприку и муку. Окунаем каждый кусочек и обжариваем с двух сторон до золотистой корочки. Готовьте с удовольствием 🤗🌿
👍4❤2
Утра доброго 😘🌿☀️ Завтрак сегодня приготовился быстро, так как вчера наготовила 🥰 люблю когда так. Сырники, кабачки в кляре, салат и кофе ☕️ Ну и конечно советские мультики, потому что день нужно начинать с хорошего ❤️ На море сегодня не пошла, вчера устала, выходной же был, стирка, уборка, готовка. Как ваше утро, что на завтрак 🤗?
❤15🕊1🙏1
Девочки, вот рецепт мороженого 🤗🥑
👏3
Наготовила 🤗
👏14👍4🔥2
Самого доброго летнего утра 🤗🌿☀️ и замечательного дня и начала недели 🌿 У меня сегодня выходной, поэтому у нас сегодня завтрак выходного дня, это когда душевно, медленно 🌿 На завтрак ленивый хачапури, смузи, арбуз, чай и кофе ☕️ Уже чувствуется осень, листья желтеют и опадают 🍂 вчера захотелось достать осенний декор 🍁 Как думаете, еще рано или уже можно🤔? А еще сегодня прилетели наши ласточки, в этом году они редко б…
❤12🔥4👏2💋1💘1
Рулет из кабачков 🤤🌿 Самый нежный и вкусный 🤌 - Ингредиенты: Кабачки 2 шт Яйца 2 шт Сметана 3 ст л Соль, паприка Зелень Мука 3 ст л - Кабачки натереть на крупной терке, посолить, дать постоять и отжать. Добавить яйца, зелень, сметану, соль, паприку и муку. Выложить на противень тонким слоем. Отправляем в духовку на 200 градусов, на 20-25 минут. А пока приготовим намазку из майонеза, паприки и чеснока. Помидоры нареза…
👍11👏2
Самого доброго утра и замечательного воскресного дня 🤗🌿☀️ Сегодня на завтрак были наивкуснейшие кабачки в кляре 🤤🌿 Рецепт нужен🙋♀️? Кусочек пиццы, готовила позавчера, остался один кусочек 🍕 Ну и конечно кофе ☕️ и мультики 🥰 Как ваше утро 🤗
❤20👍3👏2
Идея для вашего ужина 🤗🌿
🔥12❤5👏1
🤗🦋🌿
🔥14👏3❤1
Утра доброго и доброго дня 🤗🌿☕️ Сегодня утро было на море, вода замечательная 🌊 А на завтрак были яйца, салат и кофе, а на работу взяла смузи 🍹 Последние дни, наслаждаемся 🥰🌿☀️
❤17👍8👏4
Showing the 10 most recent of 10 posts we hold for @httpsorange_food_blog_laif. 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 1 seed channel's Telegram-generated recommendation list 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“orange_food_blog” (@httpsorange_food_blog_laif), 3,225 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/httpsorange_food_blog_laif.
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.