Channel
@olyalya_olyalya
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
696subscribers
-7 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001879822408 |
|---|---|
| Type | Channel |
| Username | @olyalya_olyalya |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/olyalya_olyalya |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 |
|---|---|---|
| 19 Sept 2026, 02:58 | 696 | -1 |
| 10 Sept 2026, 04:20 | 697 | -6 |
| 1 Sept 2026, 10:47 | 703 | no change |
| 1 Sept 2026, 07:31 | 703 | first reading |
6 posts held, back to 4 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 6 posts for this entry, the most recent from 20 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.
135 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 51.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 70 | 51.9% | |
| 🔥 | 45 | 33.3% | |
| ❤🔥 | 16 | 11.9% | |
| 👍 | 3 | 2.22% | |
| 🥰 | 1 | 0.741% |
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 135 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 4 August 2026 to 20 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.
Я очень люблю овощи и летом всегда готовлю из них разные виды икры. Сегодня из баклажанов, перца и помидоров! Ингредиенты: 🦊 баклажаны 🦊 помидоры 🦊 болгарский перец 🦊 оливковое масло 🦊 соль 🦊 много зелени 🦊 репчатый лук 🦊 чеснок 1. Пока сезон, я готовлю овощи на гриле. Можно также запечь их в духовке. 2. Пока овощи готовятся, нарезаю зелень и лук. 3. Овощи готовы. Очищаем их, крупно нарезаем, смешиваем с зеленью …
❤18❤🔥1🔥1
Ледяной летний Том Ям 🍤 Ингредиенты: 🦊 паста Том Ям 50 г (продается на любом маркетплейсе) 🦊 креветки 🦊 шампиньоны 🦊 лайм 🦊 кокосовое молоко и вода (жидкости нужен 1 литр) 🦊 кинза 🦊 салат чука 🦊 лед 🦊 чеснок 1. Смешиваем пасту с водой и кокосовым молоком, убираем в холодильник. 2. Готовим креветки и шампиньоны. Обжариваем их на кокосовом масле с чесноком до готовности (примерно 3-5 минут). Выкладываем на бумажное …
❤11❤🔥4🔥4👍2
День 7/7 Авторский пирог от Лисы с бататом и кедровыми орешками 🤌🏻 Ингредиенты: 🦊 батат 2 шт 🦊 слоеное бездрожжевое тесто 🦊 кедровые орешки 🦊 оливковое масло 🦊 чеснок 🦊 прованские травы 🦊 сливочное масло 🦊 петрушка 🦊 вяленые томаты в масле 🦊 соль 🦊 веточка тимьяна 1. Подготавливаем батат: Для этого моем и нарезаем его ровными слайсами, оставляя в кожуре (можно очистить). Выкладываем батат в сковороду, заливаем вод…
🔥14❤4❤🔥3
День 6/7 Пирог с помидорами, брынзой и рикоттой! Ингредиенты: 🍅 помидоры разных цветов 🫕 брынза ⚪️ рикотта 🫒 оливковое масло 🌿 любимая зелень (у меня кинза) 🥐 слоеное тесто 🧂 соль 1. Раскатываем тесто, укладываем его на противень и протыкаем вилкой. Отправляем в духовку на 10 минут. 2. Подготовка: Нарезаем помидоры круглыми слайсами. Смешиваем рикотту с брынзой. Нарезаем зелень, добавляем к ней масло, соль, переме…
❤18🔥7❤🔥1👍1
День 5/7 Пирог со спаржей и горгонзолой за 40 минут! Для этого нам потребуется: 🦊 1 упаковка слоеного теста 🦊 300 г спаржи 🦊 150 г сыра горгонзола 🦊 3-4 ст ложки рикотты 🦊 зеленый лук и укропп (или зелень по вашему вкусу) 🦊 2 ст. ложки оливкового масла 🦊 Соль по вкусу 1. Раскатываем тесто, делаем вилкой проколы и ставим в духовку на 10-15 минут при температуре 180°C, чтобы запеклось дно. 2. Спаржу нарезаем, в пир…
❤13🔥6❤🔥4
День 4/7 Летний пирог из ревеня и черешни! Ингредиенты: 🦊 Ревень ~ 3-4 стебля 🦊 Черешня ~ 150 г (по вкусу) 🦊 Сироп топинамбура 1 ст. ложка 🦊 Крахмал 1 ч. ложка 🦊 Тесто Фило 🦊 Яичный желток 🦊 Тертый пармезан 1. Очищаем и нарезаем ревень. Из черешни достаем косточку и разрезаем напополам. В миске смешиваем ревень, черешню, сироп топинамбура и крахмал. 2. Берем тесто Фило, разворачиваем и раскладываем на бумагу для з…
🔥13❤6❤🔥3🥰1
Showing the 6 most recent of 6 posts we hold for @olyalya_olyalya. 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“ОйЛяЛя” (@olyalya_olyalya), 696 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/olyalya_olyalya.
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.