Telegram RegisterThe public register of Telegram

Channel

я (не) лечу

@ya_ne_lechy

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

321subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001843467913
TypeChannel
Username@ya_ne_lechy
Descriptionздесь про то, как выбраться из клинического вакуума❤️‍🩹 управляю качеством и безопасностью в «Трех сестрах», создаю самый модный медицинский турнир «Я лечу» говорю про качество и карьеру в медицине автор: @tayakov
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/ya_ne_lechy

Growth

3217 Aug 2026, 23:31 — 321 subscribers8 Aug 2026, 07:31 — 321 subscribers7 Aug 2026, 23:318 Aug 2026, 07:31
2 measurements taken within a single day. 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 320–322 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 07:31321no change
7 Aug 2026, 23:31321first reading

Engagement

19 posts held, back to 29 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 19 posts for this entry, the most recent from 5 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
54
Videos
25
Links
44

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
2m 11s
Average length
2m 11s

Measured directly from 1 video 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

175 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 62.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10962.3%
🔥2514.3%
💅169.14%
😁105.71%
🤡74.00%
👍31.71%
🙈31.71%
👎21.14%

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

Measured over the 19 most recent posts we hold, published 29 January 2026 to 5 June 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

5 Jun 2026, 17:13 UTC252 views15 reactionsread 8 August 2026

Это было не просто смело… Предыстория👇🏻 Здесь меньше чем год назад рассказывала вам о том, как в сингапурской клинике информацию о количестве и видах инцидентов спокойно располагают в коридорах клиники, где ее могут увидеть пациенты. Мы тогда все обалдели и подумали «если бы у меня такое было…» А здесь мы с вами развели самую бурную в истории канала дискуссию про kpi в клинике. *** Прошло несколько месяцев, в ян

10👍2🤡2💅1

21 May 2026, 19:05 UTC330 views9 reactionsread 8 August 2026
Video message

Video message, posted without a caption

7👎1🤡1

21 May 2026, 19:05 UTC347 views9 reactionsread 8 August 2026
Video message

Video message, posted without a caption

3😁3🤡2👎1

21 May 2026, 19:05 UTC320 views4 reactionsread 8 August 2026

Еще сняла кружочки про доступную среду и иллюзию таковой👇🏻 Если в ваших клиниках реализованы какие-то крутые штуки по доступной среде – делитесь. Вдохновимся и порадуемся!

3🤡1

16 May 2026, 13:52 UTC391 views13 reactionsread 8 August 2026

История о том, как два разных администратора ресепшен создали противоположные вайбы от посещения клиники… Кейс 1. Две недели назад пошла к врачу в одну из клиник-крутышек Питера. Ожидания были высокие, давно слежу за ними. Открываю дверь в клинику, девушка за стойкой сразу говорит: – Здравствуйте, Таисия! Я в шоке, в голове мысли «неужели она посмотрела мою фотку в тг», так я впервые испытала эффект того самого ва

12👍1

23 Apr 2026, 17:18 UTC361 views6 reactionsread 8 August 2026
Video message

Video message, posted without a caption

6

23 Apr 2026, 17:18 UTC349 views2 reactionsread 8 August 2026

Врываюсь спустя месяц сразу с викториной! Жду ваших ответов и затем делюсь своим планом действий по внедрению СКАТа 🦠

1💅1

16 Mar 2026, 12:11 UTC530 views13 reactionsread 8 August 2026

Размышления про форму медиков 👚 Во-первых, я ненавижу размусоливать хайповые темы о новых резонансных законопроектах и всяком таком, но тут чую потребность. Во-вторых, в очередной раз благодарна судьбе (и себе), что не имею никакого отношения к гос медицине🙏🏻😅 и могу размышлять без применения к себе. Итак, мое мнение с точки зрения качества и безопасности👇🏻 Если не брать во внимание собственно выбор цветов, фасон

11💅2

13 Mar 2026, 14:13 UTC370 viewsread 8 August 2026
Poll

Назовем мое Альтер-это в халате:

  1. Стервелла28%
  2. Плохая училка19%
  3. ПрофЭссор Мракобесова53%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

13 Mar 2026, 14:12 UTC291 viewsread 8 August 2026

Моё театральное прошлое было для этого😅

13 Mar 2026, 14:12 UTC355 views26 reactionsread 8 August 2026
Forwarded from @threesistersruVideo

«Раз врач так сказал — значит, так надо» И другие фразы, по которым вы можете распознать клинику, где что-то не так с безопасностью. 📹Как отличить безопасную клинику от той, которая только кажется надежной, разбираемся с Таисией Ковалёвой. Таисия отвечает за качество и безопасность в «Трех сестрах», с ней мы подготовили чек-лист вопросов, которые помогут раскусить любое медучреждение.

🔥13😁76

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

13 Mar 2026, 14:13 UTCAnonymous Poll43 voters

Назовем мое Альтер-это в халате:

  1. Стервелла28%
  2. Плохая училка19%
  3. ПрофЭссор Мракобесова53%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

29 Jan 2026, 12:17 UTCAnonymous Poll28 voters

Такая ситуация:

  1. Норм, все как обычно57%
  2. Стрем, напишу в комменты что смутило43%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 19 most recent posts we hold, published 29 January 2026 to 5 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 837,132 of 1,480,688entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

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 1 registered channel — 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.

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

“я (не) лечу” (@ya_ne_lechy), 321 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ya_ne_lechy.

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.