Telegram RegisterThe public register of Telegram
Telegram profile photo for ЗДОРОВОЕ ПИТАНИЕ🍅🥦🍊

Channel

ЗДОРОВОЕ ПИТАНИЕ🍅🥦🍊

@na_zdogovie

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

7,476subscribers

-67 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001524529777
TypeChannel
Username@na_zdogovie
DescriptionРецепты ПП кухни и для крепкого Здоровья!🤸🏋️⛹️ Наши проекты Салатики @salatiki_i Выпечка @h824tty Закатки и закаточки @zakatochki Админ @Tat_kyb Все вопросы по рекламе только через Админа!! Канал не несёт ответственности за Рекламу,будьте бдительны
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live13 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/na_zdogovie

Topic

Health & wellness — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Observations

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.

Content that also appears on other registered channels

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.

Matching posts — open both and compare (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@h824tty/893619 Aug 2026, 08:17 UTC@na_zdogovie/6632 · this entry24 Aug 2026, 09:26 UTC1.005 days
@na_zdogovie/6634 · this entry28 Aug 2026, 08:53 UTC@h824tty/894430 Aug 2026, 07:43 UTC1.0047 hours
@na_zdogovie/6661 · this entry13 Oct 2026, 10:26 UTC@h824tty/897213 Oct 2026, 10:32 UTC1.006 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@h824tty5 (5/5 hand-verifiable sample passed)1.0047 hours@h824tty (3–2)

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. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 53 comparable posts for this entry, running 16 July 2026 to 13 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_mutual, last confirmed 14 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.

Growth

7,4767,5437,509.511 August 2026 — 7,543 subscribers11 August 2026 — 7,543 subscribers15 August 2026 — 7,542 subscribers17 August 2026 — 7,539 subscribers21 August 2026 — 7,535 subscribers25 August 2026 — 7,532 subscribers27 August 2026 — 7,527 subscribers30 August 2026 — 7,521 subscribers2 September 2026 — 7,522 subscribers6 September 2026 — 7,516 subscribers11 September 2026 — 7,515 subscribers14 September 2026 — 7,512 subscribers29 September 2026 — 7,506 subscribers6 October 2026 — 7,502 subscribers12 October 2026 — 7,504 subscribers16 October 2026 — 7,507 subscribers18 October 2026 — 7,504 subscribers21 October 2026 — 7,497 subscribers24 October 2026 — 7,496 subscribers27 October 2026 — 7,494 subscribers30 October 2026 — 7,491 subscribers2 November 2026 — 7,485 subscribers5 November 2026 — 7,482 subscribers9 November 2026 — 7,479 subscribers13 November 2026 — 7,476 subscribers11 August 202613 November 2026
25 measurements spanning 94 days, net -67. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 7,466–7,553 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
13 Nov 2026, 20:277,476-3
9 Nov 2026, 09:107,479-3
5 Nov 2026, 16:587,482-3
2 Nov 2026, 13:577,485-6
30 Oct 2026, 20:407,491-3
27 Oct 2026, 11:017,494-2
24 Oct 2026, 14:097,496-1
21 Oct 2026, 09:197,497-7
18 Oct 2026, 17:507,504-3
16 Oct 2026, 00:167,507+3
12 Oct 2026, 19:577,504+2
6 Oct 2026, 12:587,502-4
29 Sept 2026, 07:207,506-6
14 Sept 2026, 22:417,512-3
11 Sept 2026, 07:367,515-1
6 Sept 2026, 19:167,516-6
2 Sept 2026, 10:237,522+1
30 Aug 2026, 15:437,521-6
27 Aug 2026, 23:377,527-5
25 Aug 2026, 02:287,532first reading

Engagement

56 posts held, back to 15 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 38 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.18%
avg views ÷ 7,476 subscribers
Avg views / post
238
11 posts measured
Reaction rate
0.536%
reactions ÷ views · ER floor
Posts in window
11
of 56 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 5 of 11 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 November 2026
Posts held56 (15 July 2026 – 13 November 2026)
Views total2,613
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 18:43 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
≈2,690
Videos
≈1,720
Links
≈400

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.

Video runtime
23m 23s
Average length
33s

Measured directly from 42 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

69 reactions across 42 posts, in 3 distinct kinds. The most used accounts for 62.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4362.3%
❤2434.8%
🔥22.90%

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 42 of the 56 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 69 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 56 most recent posts we hold, published 15 July 2026 to 13 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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 11 posts held from the last 30 days (9.09%) 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).

13 Nov 2026, 13:11 UTC125 viewsread 17 November 2026
Forwarded from @salatiki_iPhoto

Морковный салат на зиму.🥕🫑 ✅Ингредиенты: 2 кг моркови натереть на крупной терке 100 г чеснока (натереть на мелкой терке) 300 г болгарского перца (нарезать тонкой соломкой) 150 г сахарного песка 100 мл уксуса 9 % 400 г томатной пасты 250 мл раст. масла черный молотый перец 0,5 ч.л. 2 ст.л. соли Хорошо перемешать, тушить после закипания, помешивая, 40 мин. Закатать в стерильные банки, укутать до полного остывания. ‼…

12 Nov 2026, 13:47 UTC140 views2 reactionsread 17 November 2026
Video

Дачный салат🥰 Ингредиенты: • картофель - 3-4 шт • куриная грудка - 1 шт • малосольные огурцы - 4-5 шт • лук - 1/2 шт • уксус - 1 ст. л • соль, перец - по вкусу • сметана - 3 ст. л • горчица - 1 ч. л • укроп - пучок.

❤1👍1

8 Nov 2026, 12:33 UTC174 views2 reactionsread 17 November 2026
Forwarded from @h824ttyVideo

Вкусные пышки из детства🥰 Ингредиенты: 350 г мука 7 г сухие дрожжи 160 г молоко 40 г сахар Щепотка соли 7 г ванильный сахар Яйцо 30 г сл масло/маргарин Растительное масло для жарки Приготовление на видео!

👍2

7 Nov 2026, 20:01 UTC203 viewsread 17 November 2026
Forwarded from @h824ttyVideo

Треугольники с ветчиной на завтрак🥰 Ингредиенты: • ветчина - 200 гр • сыр - 100 гр • петрушка - пучок • помидоры - 2 шт • соль, перец, специи - по вкусу • сметана - 2 ст. л • Лаваш.

7 Nov 2026, 20:01 UTC182 viewsread 17 November 2026
Forwarded from @h824ttyVideo

Хрустящая кесадилья с курицей🥰 Ингредиенты: • лук - 1/2 шт • помидор - 1 шт • куриное филе - 1 шт • соль, перец, паприка, сухой чеснок - по вкусу • консервированная кукуруза - 2 ст. л • тортилья • кетчуп - 1 ст. л • сыр - 80 гр • растительное масло.

6 Nov 2026, 12:18 UTC181 viewsread 17 November 2026
Forwarded from @h824ttyVideo

Клубничный тирамису 🍓 ⠀ Ингредиенты: 300 гр. клубники + 2 ст. л. сахарной пудры печенье дамские пальчики 280 гр. творожного сыра 300 мл. сливок 33% 4-5 ст. л. сахарной пудры Приготовление на видео!

30 Oct 2026, 11:59 UTC300 viewsread 17 November 2026
Forwarded from @h824ttyVideo

Нежный творожный насыпной пирог🥰 Ингредиенты (тесто): 400 г мука 2 шт яйцо 80 г сахар 1 чл цедра лимона 180 г сливочное масло или маргарин 2 чл разрыхлитель Щепотка соли Начинка: 700 г творог 4 шт яйца 200 г сметана 1 п ванилин 60 г крахмал 130 г сахар Выпекаем при 180° 40-45 мин. Форма 36×24 (22×30) Приготовление на видео!

26 Oct 2026, 14:20 UTC340 views1 reactionsread 17 November 2026
Photo

по-херсонски Для приготовления понадобится: • Баклажаны - 3 кг.; • Перец сладкий красный (!) -1 кг.; • Перец горький стручковый -1-3 шт.; • Чеснок - 300 гр.; • Сахар - 1 стакан; • Уксус (я готовлю с яблочным) - 1 стакан; • Масло растительное - 1 стакан; • Соль - 15 ст. л. Приготовление: 1. Баклажаны необходимо очистить от плодоножек небольшие разрезать вдоль пополам а побольше - еще и поперек. Посолить и оставить…

❤1

23 Oct 2026, 05:15 UTC332 views1 reactionsread 17 November 2026
Video

Восхитительная томленая грудинка в пиве 😍 📋 Ингредиенты: • свиная грудинка - 1 кг • пиво - 0,5 л • соль - 1/2 ч. л • сахар - 1 ч. л • молотый черный перец - 1/2 ч. л • копченая паприка - 1 ст. л • соевый соус - 70 мл 📋 Приготовление в видео

❤1

21 Oct 2026, 05:57 UTC315 viewsread 17 November 2026
Video

Азиатский салат🥰 Ингредиенты: - говядина - 400 гр - огурец - 3 шт - лук - 1 шт - зеленый лук - пучок - соевый соус - 2 ст.л - соль - по вкусу - перец - по вкусу - чеснок - 3 зубчика - сухая кинза - 1 ч.л - красный перец - по вкусу - растительное масло - 100 мл - жаренный кунжут.

19 Oct 2026, 06:27 UTC321 views1 reactionsread 17 November 2026
Photo

ƂΕΦСΤΡОΓΑΗОΒ ИНГРЕДИЕНТЫ: мясо - 600 грамм лук - 1 штука томатная паста - 2 столовые ложки сметана - 3 столовые ложки мука - 1 столовая ложка соль перец лавровый лист ПРИГОТОВЛЕНИЕ: Мясо прᴏʍᴏйте и пᴏрежьте тᴏнĸиʍи и дʌинныʍи пᴏʌᴏсĸаʍи.Измельчите ʌyĸ и ᴏбжарьте дᴏ зᴏʌᴏтистᴏсти в режиʍе "Βыпечĸа" в мультиварке.Жарить и тyшить при заĸрытᴏй ĸрышĸе.Дᴏбавьте ĸ ʌyĸy ʍясᴏ тᴏʍатную пастy и сʍетанy.Βʌейте стаĸан вᴏды дᴏбавьт…

👍1

16 Oct 2026, 06:05 UTC327 views1 reactionsread 17 November 2026
Photo

Салат с мойвой. Очень простой и вкусный! Ингредиенты: 5 кг помидоров перекрутить 1 кг морковки потереть на терке 1 кг свеклы потереть на терке 1 кг лука порезать 300 гр масла растительного 12 чайных ложек соли Приготовление: 3 кг мойвы выпотрошить и промыть. Все сложить в кастрюлю и варить 2 часа. За 5 минут до окончания варки добавить 1 ст. ложку уксусной эссенции. Приятного аппетита!

👍1

Showing the 12 most recent of 56 posts we hold for @na_zdogovie. 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.

Posts recorded as deleted after publishing

We recorded 2 posts on @na_zdogovie 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.

First seen missing
9 November 2026
Most recent seen missing
13 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
2

Forward network

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

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.

Appears in Telegram’s recommendations for other channels

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.

САЛАТИКИ 🍅🌽ЗАКАТОЧКИ
@salatiki_i · 29,300
Telegram ranks this channel #7 of 62 here — alongside 61 others — read 8 September 2026
ЗАКАТКИ И ЗАКУСКИ 🥒🥗
@zakatochki · 44,240
Telegram ranks this channel #7 of 80 here — alongside 79 others — read 28 August 2026
ВЫПЕЧКА🧁 ПРОСТО 🍩
@h824tty · 121,432
Telegram ranks this channel #12 of 69 here — alongside 68 others — read 14 August 2026
По-домашнему 🥘 Рецепты | Салаты
@podomashnimy · 34,537
Telegram ranks this channel #15 of 52 here — alongside 51 others — read 7 September 2026
ПП - это полезно и вкусно 😋
@pp_polezno · 49,688
Telegram ranks this channel #29 of 61 here — alongside 60 others — read 25 August 2026
Домашние рецепты 🍳
@home_recept · 211,921
Telegram ranks this channel #39 of 79 here — alongside 78 others — read 11 August 2026

This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“ЗДОРОВОЕ ПИТАНИЕ🍅🥦🍊” (@na_zdogovie), 7,476 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/na_zdogovie.

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.