Channel
@russku
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
11,793subscribers
-64 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001347468438 |
|---|---|
| Type | Channel |
| Username | @russku |
| Description | Множество вкусных рецептов русской кухни! Если Вы любите блюда русской кухни и вообще любите вкусно покушать - присоединяйтесь! По всем вопросам ТОЛЬКО на @TS_adminn Других аккаунтов у нас нет. |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 54 |
| Confirmed unchanged | 4 times, most recently 7 November 2026 |
| On Telegram | t.me/russku |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 22:45 | 11,793 | +1 |
| 3 Nov 2026, 23:40 | 11,792 | +6 |
| 2 Nov 2026, 22:20 | 11,786 | -4 |
| 1 Nov 2026, 18:48 | 11,790 | -2 |
| 30 Oct 2026, 16:54 | 11,792 | -2 |
| 29 Oct 2026, 15:29 | 11,794 | -1 |
| 28 Oct 2026, 11:37 | 11,795 | -6 |
| 27 Oct 2026, 08:25 | 11,801 | +1 |
| 26 Oct 2026, 04:55 | 11,800 | -5 |
| 25 Oct 2026, 04:56 | 11,805 | -4 |
| 23 Oct 2026, 01:17 | 11,809 | +4 |
| 22 Oct 2026, 00:29 | 11,805 | -7 |
| 20 Oct 2026, 17:40 | 11,812 | -1 |
| 19 Oct 2026, 17:28 | 11,813 | +2 |
| 18 Oct 2026, 20:38 | 11,811 | -6 |
| 17 Oct 2026, 17:29 | 11,817 | -1 |
| 15 Oct 2026, 17:07 | 11,818 | -12 |
| 14 Oct 2026, 15:20 | 11,830 | -2 |
| 13 Oct 2026, 02:47 | 11,832 | -2 |
| 8 Oct 2026, 20:15 | 11,834 | first reading |
77 posts held, back to 23 July 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 64 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. It is computed over the 24 of 25 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 77 (23 July 2026 – 7 November 2026) |
| Views total | 11,079 |
| Reactions total | 97 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 22:18 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 7 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 54 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.
330 reactions across 75 posts, in 7 distinct kinds. The most used accounts for 71.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 237 | 71.8% | |
| ❤ | 78 | 23.6% | |
| 🔥 | 7 | 2.12% | |
| ✍ | 3 | 0.909% | |
| 🎄 | 2 | 0.606% | |
| 🤗 | 2 | 0.606% | |
| 👌 | 1 | 0.303% |
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 75 of the 77 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 330 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 77 most recent posts we hold, published 23 July 2026 to 7 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 @russku. 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 77 most recent posts we hold for this entry, published 23 July 2026 to 7 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 25 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).
KУРИHЫЕ ЗРАЗЫ C ГРИБАМИ Ингpeдиeнты: • Куриныe гpудки — 400–500 г • Лук - 100 г • Pаститeльноe мaсло — 60 мл • Опятa, шампиньоны — 250 г • Соль — 1,5 ч.л. • Яйца куриные - 2 шт. • Молотый чеpный пeрeц - 1/2 ч. л. • Панирoвoчные сyхари — 6 ст. л. Приготовление: 1. Спepва луĸ мелкo нaрежьте и обжaрьте в мaсле дo прoзрачнoсти. Добавьтe грибы. Eсли они крyпныe, рaзрежьте их на неcкoлькo чaстей. Поcолитe и готовьте на с…
🐟 Скумбрия сухого посола (очень простой и вкусный рецепт) 😋 🧾 Ингредиенты: 🐟 Скумбрия - 2 шт 🧂 Соль крупная - 4 ст. л. 🍬 Сахар - 1 ст. л. 🌶 Черный перец горошком - 1 ч. л. 🌿 Кориандр семена - 1 ч. л. 🍃 Листья каффрского лайма - 4-5 шт #блюда_из_рыбы
👍2
Рыба в духовке по-министерски #блюда_из_рыбы
👍4
#блюда_из_рыбы
👍3
Потрясающе вкусные бутерброды Картофель - 3 шт (сырой) Лук - 1 шт Сыр - 100 гр Зелень - по вкусу Фарш - 200-300 гр Яйца - 2 шт Соль - по вкусу Батон #закуски
👍4
Сочные котлеты Котлеты 2.0 Что надо: Фарш ( на выбор любой) - 500г Соль, специи по вкусу Яйцо С1- 2 шт Сыр - 70г. Вафельные коржи- 2 шт Панировочные сухари Фарш посолить, добавить специи, сыр. 70 грамм фарша и вафли. Обмакнуть в яйцо и панировку. запечь в аэрогриле 18-20 минут при 180 Приятного аппетита! #блюда_из_говядины #блюда_из_свинины #блюда_из_курицы
👍5
Если приготовите так один раз — дальше будете делать только так #сладкое #выпечка
❤1👍1
Деликатесная елка 🎄🧀 #закуски
👍4❤2
Суп из фасоли с говядиной и сельдереем. Приготовить планировал давно, две банки фасоли ждали своей очереди две недели, но как-то не складывалось. Сегодня, всё сложилось, наслаждаюсь и ещё два дня хватит на ужин. Рецепт на 2 литра супа (8 порций). Состав: * Вода питьевая - 3 литра * Говядина на кости для бульона - 0,300 кг * Лук репчатый (подготовленный ) - 0,150 кг * Морковь (подготовленная) - 0,150 кг * Сельдерей ч…
👍1
Это круче чем Беляши и Чебуреки! За 10 мин. Муж съедает по 10 штук и не поправляется. НАУЧИЛА ВСЕХ ПОДРУГ ГОТОВИТЬ ТАКИЕ ВКУСНЯШКИ! Мало кто знает этот чудесный рецепт #выпечка
❤4👍2
Мясо тушеное с хлебом
👍1
Как тушили капусту в советских столовых: вкус, который не забыть. Делюсь рецептом 1955 года Ингредиенты: Половина вилка молодой капусты 1 столовая ложка томатной пасты 1 луковица 1 морковь Соль и черный перец по вкусу 1/2 чайных ложки сахара 1 столовая ложка сливочного масла #разное
👍5
Showing the 12 most recent of 77 posts we hold for @russku. 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 8 posts on @russku 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.
Named by 41 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 11 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Русская кухня” (@russku), 11,793 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/russku.
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.