Channel
@estzenshiny
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
656subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001726984481 |
|---|---|
| Type | Channel |
| Username | @estzenshiny |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/estzenshiny |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 04:41 | 656 | no change |
| 9 Aug 2026, 15:00 | 656 | first reading |
20 posts held, back to 9 March 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 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 20 posts for this entry, the most recent from 26 March 2026. An engagement rate over an empty window would be a number about nothing.
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.
713 reactions across 20 posts, in 26 distinct kinds. The most used accounts for 28.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 201 | 28.2% | |
| 😁 | 106 | 14.9% | |
| 🔥 | 92 | 12.9% | |
| 👍 | 57 | 7.99% | |
| 🤣 | 43 | 6.03% | |
| 👏 | 35 | 4.91% | |
| 👀 | 33 | 4.63% | |
| 🤪 | 22 | 3.09% | |
| 🙏 | 20 | 2.81% | |
| ❤🔥 | 16 | 2.24% | |
| 🙈 | 12 | 1.68% | |
| 🥰 | 10 | 1.40% | |
| 😍 | 8 | 1.12% | |
| 🤔 | 8 | 1.12% | |
| 😭 | 7 | 0.982% | |
| 🤝 | 7 | 0.982% | |
| 🫡 | 7 | 0.982% | |
| 🤯 | 6 | 0.842% | |
| 🌚 | 5 | 0.701% | |
| 🤷♀ | 4 | 0.561% | |
| 6 further kinds | 14 | 1.96% |
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 20 of the 20 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 713reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 9 March 2026 to 26 March 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.
Спелеолечебница под землëй имеет два отделения. Старое, открытое в 1990 году и новое. Старое меньше, с более низкими сводами и с перепадами рельефа. Новое с ровным полом и стенами, в которых больше присутствует красной соли. Вчера отделение #1 ходило на экскурсию в отделение #2. И наоборот. Жители обоих отделенией постановили, что их место обитания лучше соседнего. Приводились железные аргументы, призывались свидетел…
😁33❤19👍2
Ну что, отвоевали пока телегу?
🫡7👍3
Вчера на КПП перед ночным спуском получили от охранницы Беларуськалия суровое шахтëрское пожелание: Желаю, чтобы вы выздоровели. И желаю, чтобы вы забыли сюда дорогу. От создателей "глаза б мои вас не видели". Лучшее, любимое, только для вас.
😁24❤18👍4🤔1😭1
Осталось три спуска.
❤14👏4
Во время прогулок под землёй постоянно сталкиваемся с соседями. Моя любимица - женщина внушительных достоинств и возраста. Днём на поверхности она читает книги. Вечером, под землёй, пересказывает своей соседке. Т.к. помещение ограниченное, целый круг терренкуров 360 м, я, пробегая мимо них в очередной раз, слышу отрывки: ... Горы трупов. Го-ры тру-пов! И яна стоить посредь их... ... А ëн как заскочыт в ету сторожку, …
🤣20🥰10👍4🔥3😭2🙏1
Сегодня только обсуждали с подругой, что живём в учебнике истории. В том числе истории того, до какого трупоедства может довести ненависть.
🙈8🤯6😭4🤬3
Мой распорядок такой: первые полчаса хожу быстрым шагом, потом полчаса дыхательная гимнастика с инструктором, далее свободное время. Ходи, читай, играй в теннис, просто болтай с сокамерниками. Ходьба способствует активному дыханию, поэтому в отделениях предусмотрена закольцованная система дорожек. В целом то, в чём я нахожусь, это не отдых. Это серьëзная физическая работа. Спальные комнаты на 4 кровати. Стараются раз…
❤22👍11🔥1
Люди лечатся в двух подземных отделениях, каждое со своей системой терренкуров, комнатами для сна, спортивными залами. Мне предложили старое отделение #1. Тут теплее и, говорят, новичкам лучше сначала туда. После того как шахтная клеть достигает уровня спелеолечебницы, пациентов реальными рабочими тоннелями Беларуськалия, ведут в отделение. Заметила, что в тоннелях, под землёй, люди начинают идти так быстро, наскольк…
👍12👀5❤2
А какое сегодня число и день недели?
😁8🤝6🤗2🔥1🤓1
Наблюдая за деятельностью коллег по НКО можно уцепить какие-то новые приметы времени. Например, увеличение целевой аудитории с коморбидностью ВИЧ/ПТСР. Похоже, государственная система не готова к этому увеличению.
🙈4💯3🙏3
Получила минувшим вечером шуточный удар кулаком в плечо и претензию, что теперь не дают белорусу визу в Европу, потому что мы, россияне, начали войну. На более чем четырëхстах метрах вглубь матушки-земли. Посреди соляного терренкура. Под каменными сводами, которые, случись что, безразлично похоронят и любителей Карловых Вар, и представителей воинствующей расы. Пациентка Константинова Т.А., г. Москва, фрустрирована по…
👏13🤔4🤷♀4
Была с утра на лекции: Аллергический ринит. Знаю теперь всё про круговорот соплей в природе и зачем человеку нос. Лектор - заслуженный специалист в области аллергологии. Эмоциональная и визуальная подача лекции - ведущая свадьбы в начале фильма "Горько". Ну и весь набор ошибок лектора: монотонное повествование (сзади меня зевали безбожно, бесили, потому что я тоже хотела, но сидела на первом ряду прямо перед лектором…
🤪22❤3
Showing the 12 most recent of 20 posts we hold for @estzenshiny. 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 — 1,115,922 of 1,340,412entries 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.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Есть женщины в русских селеньях” (@estzenshiny), 656 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/estzenshiny.
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.