Channel
@Cakedeco
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4,565subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001126920581 |
|---|---|
| Type | Channel |
| Username | @Cakedeco |
| Created | Between 1 June 2017 and 31 July 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/Cakedeco |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 01:27 | 4,565 | +1 |
| 7 Aug 2026, 13:03 | 4,564 | no change |
| 7 Aug 2026, 12:56 | 4,564 | first reading |
8 posts held, back to 17 February 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 6 pagesof 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 8 posts for this entry, the most recent from 12 March 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
42 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 73.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 31 | 73.8% | |
| 👍 | 6 | 14.3% | |
| 🥰 | 5 | 11.9% |
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 8 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 42reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 17 February 2026 to 12 March 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.
Рецепт лимонно-маковых тарталеток🥰Маковый слой дает просто супер текстуру! рубрика - t.me/tortdeko автор - @orlova_na_kuhne Маковый слой: Мак 100 Вода 150 Масло сливочное 40 г Шоколад белый 80 г Мак залить водой и уварить на среднем огне до полного испарения воды. Шоколад растопить, добавить к нему мягкое сливочное масло, перемешать, добавить мак (мак должен быть без воды!). Заполнить тарталетки, убрать в холодильник…
❤4
Photo, posted without a caption
🌷💕Рецепт зефира для тюльпанов для небольшого миксера рубрика - t.me/tortdeko автор - @artdesserty 🌷В дежу миксера: 60 гр белка 50 гр сахара 10 гр ванильного сахара Лимонная кислота щепотка 🌷В ковш: 200 гр яблочного сока без сахара 160 гр сахара 50 гр инвертного сиропа 6 Гр агар-агара (900) Готовьте с удовольствием! #зефирныетюльпаны #зефирныетюльпаныобучение #рецептзефирныхтюльпанов #рецептзефира #рецептзефирадлятюль…
🥰5❤1
🍰РЕЦЕПТ ТОРТА 🍰Кофе - фундук - шоколад ☕️🌰🍫 рубрика - t.me/tortdeko автор - @cakeberry_33 В составе кофейный бисквит, фундучный дакуаз и два вида крема - шоколадно-кофейный и фундучный на основе творожного сыра и маскарпоне 😻 Рецепт рассчитан на торт диаметром 18 см. РЕЦЕПТ В КАРУСЕЛИ (листайте фото) ➡️➡️➡️
❤10
Video, posted without a caption
Почему велюр трескается? рубрика - t.me/tortdeko автор - @novik_bakery Шоколадный велюр — очень хрупкое покрытие, поэтому при работе с ним важно избегать ошибок, которые могут привести к трещинам💔 1. Слишком толстый слой велюра. Следите за равномерностью покрытия. 2. Торт не отстоялся и продолжает давать усадку. Не покрывайте торт сразу после сборки, дайте ему отстояться, иначе треснет скорее всего даже не сам велюр,…
👍6
ШОКОЛАДНЫЙ ФОНДАН🍫 рубрика - t.me/tortdeko автор - @carriecakeee Порция рассчитана на 2 формы диаметром 8 см ▫️Шоколад 54% - 65 г ▫️Сахар - 35 г ▫️Масло сливочное - 60 г ▫️Яйцо - 1 шт ▫️Мука - 13 г 1. Растопить шоколад с маслом в микроволновке или на водяной бане. 2. Взбить миксером яйцо с сахаром. Пару минут, чтобы появилась пенка и масса немного увеличилась. 3. Растопленный шоколад с маслом постепенно ввести в яичн…
❤6
Торт Рафаэлло🥥 рубрика - t.me/tortdeko автор - @muff_sweets Рецепт кокосового бисквита в предыдущем посте автора) Крем с белым шоколадом и сливками: Белый шоколад- 200гр Сливки (1) - 200 гр (горячие) 33% Сливки (2) - 300гр (холодные) 33% Этот крем готовится заранее, до 4-8 часов до взбивания. Удобно сделать его вечером, а утром уже взбить миксером. Нарезаем шоколад на мелкие кусочки. Отправляем в миску или в глубокую…
❤10
Showing the 8 most recent of 8 posts we hold for @Cakedeco. 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.
@Cakedeco named 3 handles 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Рецепты, декор, фото тортов. Журнал ТортДеко, CakeDeco.ru” (@Cakedeco), 4,565 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Cakedeco.
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.