Самые вкусные голодные помидорки 😍

Channel
Лучшие салаты и закуски
@s_a_l_a_t
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
17,304subscribers
-33 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001461267928 |
|---|---|
| Type | Channel |
| Username | @s_a_l_a_t |
| Description | Здесь собраны самые лучшие рецепты салатов и закусок на любой вкус! Добро пожаловать и приятного аппетита! По всем вопросам ТОЛЬКО на @TS_adminn Других аккаунтов у нас нет. |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/s_a_l_a_t |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 20:55 | 17,304 | -2 |
| 14 Aug 2026, 11:46 | 17,306 | +1 |
| 13 Aug 2026, 05:23 | 17,305 | -9 |
| 12 Aug 2026, 06:12 | 17,314 | -5 |
| 11 Aug 2026, 09:29 | 17,319 | -4 |
| 10 Aug 2026, 12:22 | 17,323 | +1 |
| 9 Aug 2026, 15:17 | 17,322 | -6 |
| 8 Aug 2026, 16:54 | 17,328 | -2 |
| 7 Aug 2026, 20:22 | 17,330 | -2 |
| 6 Aug 2026, 18:00 | 17,332 | -5 |
| 6 Aug 2026, 07:15 | 17,337 | no change |
| 6 Aug 2026, 07:09 | 17,337 | first reading |
Engagement
31 posts held, back to 22 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 22 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.91%
- avg views ÷ 17,304 subscribers
- Avg views / post
- 504
- 31 posts measured
- Reaction rate
- 0.588%
- reactions ÷ views · ER floor
- Posts in window
- 31
- of 31 held
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 15 of 31 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 August 2026 |
|---|---|
| Posts held | 31 (22 July 2026 – 16 August 2026) |
| Views total | 15,635 |
| Reactions total | 46 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Aug 2026, 16:49 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.
What this channel posts
- Photos
- ≈102
- Videos
- ≈237
- Links
- ≈5,780
Lifetime counters from Telegram’s own channel header, read 16 August 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.
- Video runtime
- 21m 28s
- Average length
- 1m 39s
Measured directly from 13 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.
Reaction mix
46 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 60.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 28 | 60.9% | |
| 👍 | 12 | 26.1% | |
| ✍ | 2 | 4.35% | |
| 👏 | 2 | 4.35% | |
| 🔥 | 2 | 4.35% |
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 15 of the 31 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 46reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 22 July 2026 to 16 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.
Recent posts
Перцы в медово-горчичном маринаде Ингредиенты: ▫️перец болгарский — 1 кг ▫️оливковое масло — 150 г ▫️горчица — 2 ст. л. ▫️мед — 2 ст. л. ▫️соль — 1 ч. л. ▫️перец горошком — 1 ч. л. ▫️лавровый лист — 6 шт. Способ приготовления: 1. Вымыть перцы и уложить их на противень, застеленный бумагой для выпечки. 2. Запекать перцы при температуре 260°C, периодически переворачивая. Как только на нижней части перцев появятся тем…
🍶20 СОУСОВ ДЛЯ ЗАПРАВОК САЛАТОВ И ВТОРЫХ БЛЮД ✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦✦ 1. Сметана+зелень 2. Йогурт+томатная паста 3. Мягкий творог+зелень+чеснок 4. Йогурт+сок лимона+горчицы 5. Фета+йогурт+укроп 6. Тертое яблоко+карри+йогурт 7. Йогурт+тертый чеснок 8. Оливковое масло+горчица+кунжут 9. Оливковое масло+соевый соус+зелень 10. Жидкий мёд+лимонный сок 11. Оливковое масло+сок лимона+зелень 12. Оливковое масло+соевый с…
ЛЕТОМ ВСЕГДА ГОТОВЛЮ Рулетики из перца🌶 🌶перец болгарский - 4 шт 🌶сыр Фета - 250 г 🌶сметана - 3 ст.л 🌶грецкий орех - 50-70 г 🌶чеснок - 2–3 зубчика 🌶кинза - 1 пучок 🌶оливковое масло Перцы запекать 20 минут при 200 градусах
❤3
Тёплый салат из печени Ингредиенты: ✅Печень любая - 150 гр ✅Луковица - 1 шт ✅Красный болгарский перец - 1 шт ✅Чеснок - 1 зубчик ✅Зелень - кинза, укроп или петрушка. ✅Острый перец - по вкусу ✅2 ст л соевого соуса ✅Молотый кориандр. 1. Печень очистить от плёнки, нарезать тоненькими пластами. Промыть в воде и сварить в подсоленной подсоленной водичке. Буквально три минуты, чтоб прокипело, не больше. Затем нужно изъят…
ЯРКИЙ КОРЕЙСКИЙ САЛАТ (ЗАКУСКА) - ХЕ ИЗ ГОВЯДИНЫ Ингредиенты: 500 г говядины 1 репчатый лук 1 сладкий болгарский перец 3 зубчика чеснока 1 пучок кинзы 1 ч.л. соли 1 ч.л. сахара 1 ч.л. кориандра 1/2 ч.л. черного перца 1 ст.л. красного перца (замените на паприку, если не любите острое) 2 ст.л. соевого соуса 1/2 ст.л. уксуса (70%) 100 мл растительного масла 100 мл говяжьего бульона Приятного аппетита!
❤2
🍆Мясные баклажаны🍆 Баклажаны 3 шт Фарш говяжий 700гр Лук репчатый 1шт Чеснок 2 зубчика Соль по вкусу Перец по вкусу Перцы острый красный 1/4чл Паприка 1/2чл Специи для мяса 1/2чл СОУС: Томаты в/с 400гр Соль 1чл Сахар 1-2чл Перец острый красный 1/3чл Орегано 1чл Чеснок 4 зубчика Масло оливковое 5ст л
👍5
🥒Салат-закуска из молодых кабачков🥒
❤4
🥒Закуска из кабачков🥒 Кабачки молодые 4шт Соль по вкусу Масло раст. для смазки Намазка: Майонез 3ст л Сметана 20% 3ст л Чеснок 4 зубчика Соль по вкусу Перец по вкусу Укроп 30гр Соус черный перец (по желанию)2чл
❤3
ПРЯНЫЕ КАБАЧКИ В СОЕВОМ СОУСЕ 🇯🇵🇨🇳🇰🇷 Требуется: •кабачки - 1000 г •чеснок - 6 зубчиков •соевый соус- 100 мл •крахмал- 2 ч. л. •сахар - 2 ч. л. •кинза (или петрушка) - по вкусу •кунжут - 2 ч. л. •растительное масло - 100 мл Смешайте соевый соус, сахар, крахмал и измельченный чеснок. Я пропустила его через пресс, но можно натереть зубчик на терке или измельчить ножом. Все хорошо перемешайте. Кабачки очистите (молод…
Нереально вкуснущий закусочный торт!!! Я его буду готовить на все праздники 👍 ✅Обжарить 2 луковицы и 2 моркови ✅Обжарить 300 гр шампиньонов ( или других грибов) ✅500гр сырой куриный фарш посолить и поперчить ✅Круглую форму обложить фольгой или пергаментной бумагой Собираем торт ✅Вафельный корж на дно, сверху третью часть от фарша( разровнять), опять корж, на него обжаренные лук в морковью, опять корж, сверху грибы. ✅…
👍2
Я не обжариваю и не тушу капусту. Вместо этого использую другой способ приготовления, который выходит вкуснее, быстрее и проще. Мне кажется, что проще рецепта капустных блюд просто не найти! Этот рецепт настолько лёгкий, что не требует особых усилий — достаточно лишь нарезать капусту. В итоге получается очень вкусное блюдо! Готовая капуста, приготовленная таким способом, отлично подходит к любым мясным, куриным …
❤5
Showing the 12 most recent of 31 posts we hold for @s_a_l_a_t. 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.
Citation-graph rank
Citation-graph rank — 478,344 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 14 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.
@top_kanalov2025 · 343 postsРецепты со всего мира
@receptopedia · 352 postsРекламное Агенство
@seotg · 82 postsБудь здоров
@byd_zdorov · 24,8931 postДомашние рецептики
@domashnie_receptiki · 30,3411 postGIF Рецепты. Быстро и Вкусно!
@EdaGif · 38,4821 postEnglish Words 🤓 | Английский в словах
@EnglishBooksTG · 23,4731 postEnglish Polls | Английский в опросах
@EngPolls · 14,8531 postуᴛᴩᴇнняя ᴩᴏᴄᴀ ♡
@estetika924 · 11 postПервый Книжный | Бестселлеры
@FirstBookTG · 15,3401 post❤️ Рецепты Красоты
@krasot_a · 13,5161 postРемонт и стройка
@stroikairemot · 51 postРецепты Быстро и Вкусно!
@vkusno_recepty · 22,9381 postMust Read | Что почитать
@YourMustRead · 25,8841 post
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.
Cite this entry
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Лучшие салаты и закуски” (@s_a_l_a_t), 17,304 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/s_a_l_a_t.
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.