Channel
@novie_recepti2021
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
17,484subscribers
-136 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001455773425 |
|---|---|
| Type | Channel |
| Username | @novie_recepti2021 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/novie_recepti2021 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 26 Sept 2026, 13:58 | 17,484 | -18 |
| 19 Sept 2026, 15:59 | 17,502 | -8 |
| 17 Sept 2026, 06:38 | 17,510 | -6 |
| 15 Sept 2026, 07:56 | 17,516 | -6 |
| 13 Sept 2026, 13:57 | 17,522 | -7 |
| 11 Sept 2026, 14:56 | 17,529 | -7 |
| 8 Sept 2026, 22:58 | 17,536 | -9 |
| 5 Sept 2026, 18:38 | 17,545 | -3 |
| 3 Sept 2026, 15:38 | 17,548 | -5 |
| 2 Sept 2026, 05:13 | 17,553 | -1 |
| 1 Sept 2026, 05:25 | 17,554 | -9 |
| 30 Aug 2026, 10:47 | 17,563 | +1 |
| 28 Aug 2026, 11:44 | 17,562 | -4 |
| 27 Aug 2026, 10:58 | 17,566 | -4 |
| 26 Aug 2026, 08:28 | 17,570 | -1 |
| 25 Aug 2026, 06:12 | 17,571 | -3 |
| 24 Aug 2026, 07:25 | 17,574 | -5 |
| 22 Aug 2026, 14:23 | 17,579 | -8 |
| 21 Aug 2026, 01:58 | 17,587 | +4 |
| 20 Aug 2026, 02:28 | 17,583 | first reading |
20 posts held, back to 22 December 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 55 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 20 posts for this entry, the most recent from 15 January 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 20 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.
378 reactions across 20 posts, in 11 distinct kinds. The most used accounts for 47.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 179 | 47.4% | |
| ❤ | 155 | 41.0% | |
| 🔥 | 17 | 4.50% | |
| 🥰 | 11 | 2.91% | |
| 👏 | 5 | 1.32% | |
| 😍 | 5 | 1.32% | |
| 👎 | 2 | 0.529% | |
| 🎃 | 1 | 0.265% | |
| 👀 | 1 | 0.265% | |
| 🤡 | 1 | 0.265% | |
| 🤣 | 1 | 0.265% |
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 20 of the 20 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 378 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 22 December 2025 to 15 January 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 шт. ▫️ветчина – 100 г. ▫️сыр – 100 г. ▫️майонез – 1 ст. л. ▫️соль, специи ▫️растительное масло
👍26❤13👏3🥰1
Булочки с сыром и беконом 🥓 #закуска #перекус #выпечка 📝 Ингредиенты: ▫️слоеное тесто – 500 г. ▫️зелень ▫️сыр – 50 г. ▫️бекон – 1 пачка
❤11👍11
Тайский куриный салат 🍗 #салат #обед #ужин 📝 Ингредиенты: ▫️куриное филе – 500 г. ▫️кокосовое молоко – 400 мл. ▫️лемонграс – 10 г. ▫️чеснок – 10 г. ▫️имбирь/галангал – 10 г. ▫️острый перец – 5 г. ▫️лайм – 1/2 шт. ▫️рыбный соус – 1 ч.л. ▫️груша/айва – 200 г. ▫️кинза ▫️сахар – 1/2 ч.л. ▫️соль
❤5👍5🔥2🤡1
Котлеты куриные 🍗 #обед #ужин 📝 Ингредиенты: ▫️филе бедра – 800 г. ▫️филе грудки – 800 г. ▫️перец красный – 1 шт. ▫️перец жёлтый – 1 шт. ▫️лук репчатый – 6 шт. ▫️специи
❤16👍1
Взбитый сыр бри 🧀 #закуска #наНовыйГод 📝 Ингредиенты: ▫️сыр бри – 300 г. ▫️багет – 1 шт. ▫️клюква замороженная – 125 г. ▫️вода – 50 мл. ▫️сахар – 4 ст. л. ▫️фисташки измельченные ▫️мёд ▫️розмарин
❤7👍6🔥2👎1
Закуска с беконом 🥓 #закуска ⠀ 📝 Ингредиенты: ▫️черный хлеб ▫️бекон сырокопченый ▫️чеснок ▫️сулугуни ⠀
👍12❤8😍5👏2🔥2
Чесночный хлеб 🥖 #обед #ужин #закуска 📝 Ингредиенты: ▫️чиабатта – 1 шт. ▫️петрушка – 10 г. ▫️чеснок – 6 зубчиков ▫️молоко – 50 мл. ▫️сливочное масло – 100 г. ▫️сыр – 100 г.
❤13🥰9👍7🔥3
Смузи для красивой кожи 🍐 #завтрак #напитки 📝 Ингредиенты: ▫️ груша – 1 шт. ▫️ банан – 1 шт. ▫️ киви – 1 шт. ▫️ шпинат/руккола ▫️ сок лайма ▫️ кокосовая вода – 250 мл. ▫️ конопляные семена очищенные – 1 ст. л.
❤10👍2🎃1
Маринованные шампиньоны 🍄🟫 #закуска 📝 Ингредиенты: ▫️ шампиньоны – 500 г. ▫️ вода – 300 мл. ▫️ соль – 2 ст. л. ▫️ сахар – 1 ст. л. ▫️ лавровый лист – 2 шт. ▫️ перец горошком – 5 шт. ▫️ чеснок – 2 зубчика. ▫️ уксус 9% –4 ст. л.
❤9👍4🔥4
Фрикадельки в кокосовом соусе 🍛 #обед #ужин 📝 Ингредиенты: ▫️фарш куриный – 400 г. ▫️кабачок – 1/2 шт. ▫️морковь – 1 шт. ▫️петрушка ▫️яйцо – 1 шт. ▫️соевый соус – 1 ст. л. ▫️имбирь ▫️кориандр – 1/3 ч. л. ▫️соль Соус: ▫️сладкий перец – 1 шт. ▫️имбирь ▫️вода горячая – 3 ст. л. ▫️соевый соус – 1 ст. л. ▫️кокосовые сливки – 200 г. ▫️кориандр – 1/2 ч. л. ▫️карри – 1/2 ч. л. ▫️кунжут ▫️петрушка
👍9❤4
Апельсиновый кекс 🍊 #выпечка 📝 Ингредиенты: ▫️апельсин – 1,5 шт. ▫️яйцо – 3 шт. ▫️сахар – 150 г. ▫️масло растительное – 120 мл. ▫️мука – 290 г. ▫️разрыхлитель – 10 г. ▫️ванильный сахар – 1 ч. л. ▫️соль – щепотка
👍16❤8🔥2
Мандариновый десерт с меренгой 🍊 #десерт #напитки 📝 Ингредиенты: Курд: ▫️мандарины – 5 шт. ▫️сахар – 30 г. ▫️кукурузный крахмал – 20 г. ▫️желток – 2 шт. Меренга: ▫️яичный белок – 200 г. ▫️сахар – 400 г. ▫️соль – щепотка Крем: ▫️творожный сыр – 440 г. ▫️сливки 33% – 200 г. ▫️сахарная пудра – 70 г.
👍10❤3🔥2
Showing the 12 most recent of 20 posts we hold for @novie_recepti2021. 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.
Named by 5 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.
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 7 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Рецептонок | видео рецепты | лучшие рецепты | простые рецепты | вкусные рецепты” (@novie_recepti2021), 17,484 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/novie_recepti2021.
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.