Channel
@zapiski_konditeta
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
5,059subscribers
-6 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001662751529 |
|---|---|
| Type | Channel |
| Username | @zapiski_konditeta |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/zapiski_konditeta |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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, 03:59 | 5,059 | -4 |
| 12 Sept 2026, 03:20 | 5,063 | +2 |
| 2 Sept 2026, 07:44 | 5,061 | -3 |
| 30 Aug 2026, 17:18 | 5,064 | -1 |
| 29 Aug 2026, 18:30 | 5,065 | first reading |
20 posts held, back to 14 June 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 20 posts for this entry, the most recent from 21 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 10 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.
34 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 82.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 28 | 82.4% | |
| 👍 | 4 | 11.8% | |
| ❤🔥 | 2 | 5.88% |
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 12 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 34 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 14 June 2026 to 21 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2Vtzqv2Y9to | 1 | 18 August 2026 | 18 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 20 most recent posts we hold, published 14 June 2026 to 21 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Рецепт Карамели, который для меня оказался самым удачным😊 Никакой кристаллизации сахара, горелого привкуса, перевода продуктов! 125г сахара 125 г сливок 33% 30 г глюкозного сиропа 40г воды 50г масла сливочного 82,5% Воду, сахар и сироп смешать, проварить до янтарного цвета, снять с огня, влить подогретые до горячего сливки и масло комнатной температуры, перемешать до однородности, перелить в тару, пробить блендеро…
❤3
🎁 Бесплатный рецепт Кукис «Чоко Бар»! Люксовый вкус! Хотите начать с десерта, который выглядит очень эффектно, но не требует сложной сборки, выравнивания и декора? 😍 Тогда Кукис «Чоко Бар» — отличный вариант для старта! Представьте это сочетание: 🍪 нежное печенье с кусочками шоколада 🍫 сверху ещё один слой темперированного шоколада Печенье получается очень нежным по текстуре: в меру мягким, рассыпчатым и с лёгким…
Photo, posted without a caption
Автор. @zhil _bil_tort
ТОРТ С КАРАМЕЛИЗОВАННЫМИ БАНАНАМИ ⠀ Торт сделанный своими руками - всегда самый вкусный и особенный! ⠀ Поэтому не бойся печь, экспериментировать! ⠀ Попробуй сделать такой, оч вкусно 👌🏻 ⠀ Нам потребуется: ⠀ Для бисквита: ⠀ Мука 300 гр Сахар 300 гр Яйцо 4 шт С1 Молоко 110 мл Ванильный сахар 10 гр Разрыхлитель 10 гр Растительное масло без запаха 55 гр Кипяток 5 ст.ложек ⠀ Как делаем: ⠀ Яйца взбиваем до светлой пены и по…
❤1👍1
Photo, posted without a caption
Учимся делать море на торте 🌊🌊🌊 Автор @bondemoi_dessert
🍫 Шоколадно-малиновый торт с фундучным бисквитом Один из тех тортов, которые хочется готовить снова и снова. Нежный фундучно-шоколадный бисквит, яркая малиновая начинка, легкий сливочный крем и воздушный молочный ганаш для покрытия 💜 Фундучно-шоколадный бисквит Ингредиенты: • Желтки 70 г (примерно 5 шт.) • Соль 2 г • Сахар 60 г • Фундучная мука 40 г • Пшеничная мука 20 г • Какао 10 г • Кукурузный крахмал 5 г • Раз…
❤3
Video, posted without a caption
Торт «Киндер Пингви»🍫🥛 Ингредиенты на форму D18 см: * 3 яйца * 5 г ванильного сахара * 80 г сахара * 70 мл молока * 40 г растительного масла без запаха * 90 г муки * 20 г какао * 5 г разрыхлителя Шоколадный крем: * 335 мл молока * 90 г сахара * 10 г ванильного сахара * 25 г кукурузного крахмала * 2 яйца * 70 г тёмного шоколада * 130 г мягкого сливочного масла Сливочный крем: * 270 мл холодных сливок 30%+ * 10 г заг…
❤3
КРЕМ «ТОФФИ» ДЛЯ МЕДОВИКА 🍯 Карамельное безумие! Медовые коржи в сочетании с карамельным кремом «Тоффи» — это совершенно новый уровень! Торт пропитывается идеально, получается нереально нежным и буквально тает во рту. Сохраняй точные пропорции 📌 и погнали готовить! Ингредиенты: Сметана отвешенная — 400 г Сливки 33-35% (холодные, взбитые) — 150 г Готовая карамель (либо вареная сгущенка) — 200 г Собираем крем: К отв…
👍3❤1
Ингредиенты: Сыр Маскарпоне — 500г Желток - 120г Сахар - 80г Какао - 30г Черный кофе - 200г 1. Желтки с сахаром ставим на водяную баню и постоянно помешивая, прогреваем массу до 60—65°. Если сахар растворился — значит масса готова. 2. Взбиваем желтки с сахаром при помощи миксера до пышного состояния. 3. Ко взбитым желткам добавляем сыр Маскарпоне и взбиваем крем на низких оборотах миксера до однородности. 4. Печенье…
❤2
Showing the 12 most recent of 20 posts we hold for @zapiski_konditeta. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@zapiski_konditeta named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 4 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.
“Рецепты кондитеров. МК. Бесплатные вебинары. zapiski_konditera” (@zapiski_konditeta), 5,059 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/zapiski_konditeta.
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.