Video, posted without a caption
❤11👍3

Channel
@tortyrecepti
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
49,404subscribers
-671 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001113514065 |
|---|---|
| Type | Channel |
| Username | @tortyrecepti |
| Description | По вопросам рекламы, сотрудничества писать: @Artunet74 Страница включена в перечень Роскомнадзора: https://gosuslugi.ru/snet/67891dc5fe9f43161513b694 День рождения канала 19 февраля 2017 г. #8VXTR |
| Created | 19 February 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/tortyrecepti |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @tortyrecepti/4479 · this entry27 Jul 2026, 04:29 UTC | @resept_sladosty/1039528 Jul 2026, 13:34 UTC | 1.00 | 33 hours |
| @tortyrecepti/4484 · this entry1 Aug 2026, 08:07 UTC | @resept_sladosty/104136 Aug 2026, 11:54 UTC | 1.00 | 5 days |
| @tortyrecepti/4495 · this entry7 Aug 2026, 10:59 UTC | @resept_sladosty/104157 Aug 2026, 11:40 UTC | 1.00 | 41 minutes |
| @tortyrecepti/4527 · this entry11 Sept 2026, 12:27 UTC | @resept_sladosty/1043216 Sept 2026, 10:50 UTC | 1.00 | 5 days |
| @tortyrecepti/4565 · this entry10 Nov 2026, 11:28 UTC | @resept_sladosty/1045210 Nov 2026, 11:31 UTC | 1.00 | 3 minutes |
| @tortyrecepti/4568 · this entry14 Nov 2026, 09:37 UTC | @resept_sladosty/1046014 Nov 2026, 09:52 UTC | 1.00 | 16 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @resept_sladosty | 6 (6/6 hand-verifiable sample passed) | 1.00 | 17 hours | this entry (6–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 52 comparable posts for this entry, running 4 June 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 02:58 | 49,404 | -4 |
| 11 Nov 2026, 21:10 | 49,408 | -17 |
| 9 Nov 2026, 21:07 | 49,425 | -14 |
| 8 Nov 2026, 14:49 | 49,439 | -7 |
| 7 Nov 2026, 11:37 | 49,446 | -11 |
| 6 Nov 2026, 11:07 | 49,457 | +3 |
| 5 Nov 2026, 10:26 | 49,454 | -12 |
| 4 Nov 2026, 09:01 | 49,466 | -10 |
| 3 Nov 2026, 10:55 | 49,476 | -12 |
| 2 Nov 2026, 12:28 | 49,488 | -7 |
| 1 Nov 2026, 11:58 | 49,495 | -7 |
| 31 Oct 2026, 09:50 | 49,502 | -11 |
| 30 Oct 2026, 11:38 | 49,513 | -8 |
| 29 Oct 2026, 08:55 | 49,521 | -30 |
| 28 Oct 2026, 08:14 | 49,551 | -7 |
| 27 Oct 2026, 09:39 | 49,558 | -9 |
| 26 Oct 2026, 09:49 | 49,567 | -8 |
| 25 Oct 2026, 10:56 | 49,575 | -13 |
| 24 Oct 2026, 12:16 | 49,588 | -6 |
| 23 Oct 2026, 11:46 | 49,594 | first reading |
74 posts held, back to 4 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 210 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 74 (4 June 2026 – 16 November 2026) |
| Views total | 96,560 |
| Reactions total | 552 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 14:07 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 52 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.
2,364 reactions across 73 posts, in 11 distinct kinds. The most used accounts for 65.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,543 | 65.3% | |
| 👍 | 387 | 16.4% | |
| 🔥 | 312 | 13.2% | |
| 🥰 | 71 | 3.00% | |
| ✍ | 19 | 0.804% | |
| 😍 | 14 | 0.592% | |
| 👌 | 7 | 0.296% | |
| 👏 | 7 | 0.296% | |
| 🎅 | 2 | 0.085% | |
| 💋 | 1 | 0.042% | |
| 🤗 | 1 | 0.042% |
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 73 of the 74 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 2,364 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 74 most recent posts we hold, published 4 June 2026 to 16 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tortyrecepti. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 74 most recent posts we hold for this entry, published 4 June 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 0 of 24 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Video, posted without a caption
❤11👍3
🍯 МИНИ-МЕДОВИЧКИ — ПИРОЖНЫЕ. На видео 1/2 порции Ингредиенты Для медового коржа: • Мёд — 2 ст. л. • Сахар — 100 г • Сливочное масло — 60 г • Сода — 1 ч. л. • Яйца — 3 шт. • Мука — 250 г Для начинки: • Варёная сгущёнка — 380 г • Мёд — 1 ст. л. (по желанию) • Грецкие орехи — по желанию Приготовление 1. В сотейнике соединяем мёд, сливочное масло и сахар. Нагреваем на небольшом огне, помешивая, пока сахар не раствори…
✍1❤1
Немного вдохновения перед праздником ♥️
❤30
Крем чиз для выравнивания на сливках 400гр творожного сыра Сливки 33% -50гр Сахарная пудра - 80гр( по вкусу) Сливки и сыр должны быть холодными!!! В чашу переложить все ингредиенты и взбить миксером, крем станет матовым и плотными. После перемешать лопаткой чтоб убрать пузырьки воздуха. Хватает на торт диаметром -16см, высота - 11- 12см. Автор riana.cake
👍12❤8
Video, posted without a caption
❤31👍12
🐌 Рулет «Улитка» Ингредиенты: Яйца — 3 шт Мука — 90г Сахар — 100г Разрыхлитель — 3г Соль — щепотка Молоко — 40г Растительное масло — 40г Ванильная паста Творожный сыр — 520г Сгущеное молоко — 150г Приготовление : 1. Разделяем белки и желтки. Взбиваем белки с сахаром до устойчивых пиков. 2. В желтки добавляем: молоко, растительное масло, 1/2 муки, ванильную пасту и соль. Смешать до объединения. 3. Часть получившейс…
✍6👍5❤1
Печенье «Трости» 🎅🏼🥂 Самое популярное новогоднее печенье, которое точно поднимет вам настроение и настроит на праздничный лад💫 Ингредиенты: 180 гр сливочного масла 150 гр сахара 10 гр ванильного сахара Щепотка соли 1 яйцо 290 гр муки 1/2 чайной ложки разрыхлителя 15 гр какао порошка для коричневой части 1. Масло комнатной температуры взбиваем с сахаром и ванильным сахаром около 3 микро. Добавляем яйцо и соль, взби…
❤20🔥6🥰3✍2
Глазурь: На яйцо С1 - 200 грамм пудры На яйцо С0 - 220 грамм пудры Смешать яйцо и пудру. Взбить миксером до белой плотной массы. Отделить плотную глазурь для контуров и рисунков. Постепенно вводить питьевую воду (по чайной ложке), довести до консистенции жидкой сметаны, но не переборщите с водой! Окрасить глазурь красителями и можно украшать печенье 😊 Автор mama.v.shocke
🔥20👍4✍3❤3
Павлуша ❤️ ингредиенты для меренги: - 8 яичных белков - 350г сахара - щепотка соли - 1 ст. л лимонного сока - 15 г крахмала для крема: - 250 мл сливок 33% - 150 мл сгущенки приготовление: 1. взбиваем белки до густых пиков и понемногу добавляем сахара, не переставая взбивать. 2. после того как добавили весь сахар, кидаем крахмал и лимонный сок. еще раз хорошенько взбиваем. масса должна получиться плотной и гладкой.…
❤31🔥7👍1
Медово-имбирное пряничное тесто Мед 320гр Сахар 200гр Соль 2 больш щеп Корица 12гр Имбирь 10гр Масло сливочное 82,5% 250гр Сода 9гр Яйцо куриное С1 2шт (102гр) Мука 750гр Перед выпечкой тесто достать из холодильника за 30 минут, размять Далее раскатываем пласт толщиной 5мм Выпекать при температуре 180град 8 мин Но лучше ориентироваться на свою духовку Важные моменты: ❎Все ингредиенты топим на небольшом огне ❎…
❤20🔥3👍2✍1
Video, posted without a caption
🔥23❤3
🎂 Бисквитный торт с варёной сгущёнкой и грецкими орехами Ингредиенты для бисквита: * 6 яиц * 150 г сахара * 1 ч. л. ванильного сахара * 200 г муки Приготовление бисквита: * Яйца, сахар и ванильный сахар взбить миксером до пышной светлой массы. * Добавить просеянную муку и аккуратно перемешать лопаткой движениями снизу вверх до однородного теста. * Перелить тесто в круглую форму. * Выпекать при температуре 180°C п…
❤14✍1
Showing the 12 most recent of 74 posts we hold for @tortyrecepti. 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.
We recorded 5 posts on @tortyrecepti as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 25 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 9 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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“Торты. Капкейки.Рецепты” (@tortyrecepti), 49,404 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/tortyrecepti.
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.