Channel
@pushkino_rb
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,705subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001753850615 |
|---|---|
| Type | Channel |
| Username | @pushkino_rb |
| Created | 13 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/pushkino_rb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 02:37 | 2,705 | -1 |
| 3 Sept 2026, 10:03 | 2,706 | -2 |
| 31 Aug 2026, 00:28 | 2,708 | -1 |
| 28 Aug 2026, 01:34 | 2,709 | -4 |
| 24 Aug 2026, 19:45 | 2,713 | -3 |
| 21 Aug 2026, 00:46 | 2,716 | +6 |
| 17 Aug 2026, 20:19 | 2,710 | +3 |
| 15 Aug 2026, 01:45 | 2,707 | +3 |
| 11 Aug 2026, 18:52 | 2,704 | -1 |
| 8 Aug 2026, 12:02 | 2,705 | +1 |
| 7 Aug 2026, 14:32 | 2,704 | no change |
| 7 Aug 2026, 14:29 | 2,704 | first reading |
5 posts held, back to 6 August 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 page of 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
19 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 47.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 47.4% | |
| 🎉 | 4 | 21.1% | |
| 👍 | 3 | 15.8% | |
| 👏 | 2 | 10.5% | |
| 🔥 | 1 | 5.26% |
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 3 of the 5 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 6 August 2026 to 7 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.
Пушкинская больница в лицах - Гитинова Тальмира Абдуллаевна 🗣️Есть профессии, которые выбирают сердцем, и акушер- гинеколог - одна из них. Тальмира Абдуллаевна Гитинова – коренная жительница Ивантеевки, врач высшей квалификационной категории, Заслуженный врач Российской Федерации, которая 45 лет своей жизни посвятила медицине, и ровно три десятилетия возглавляла отделение гинекологии в Ивантеевке. Она для нескольких…
❤9
🎁 Именинники сегодня🎁: 🎀 Бердиева Фатима Казиевна, врач-кардиолог, поликлиника №9 (Ивантеевка); 🎀 Басова Наталья Васильевна, медсестра кабинета врача-инфекциониста по работе с больными ВИЧ-инфекцией, поликлиника №5 (Правдинский); 🎀 Ёрова Лутфия Гулмахмадовна, врач-терапевт участковый, поликлиника №9 (Ивантеевка); 🎀 Клепикова Марина Васильевна, медсестра приемного отделения, стационар №1 (Пушкино); 🎀 Мордовина Эржебет…
🎉4👏2
Медицинские мероприятия следующей недели 🔹Для начала напоминаем, что завтра, 8 августа, пройдет единый день диспансеризации в поликлиниках №1 в Пушкино, №3 в Лесном, №4 в Клязьме, №5 в Правдинском, №6 в Софрино, №7 в Софрино-1, №8 в Ашукино и №9 в Ивантеевке. В этот же день медосмотр можно пройти и в городском парке культуры и отдыха в Ивантеевке, по адресу: Студенческий проезд, д.12, с 9.00 до 13.00. ➡️Мобильный ф…
Первые шаги на пути к выздоровлению – для медицинской реабилитации в Пушкинскую больницу поступило новое оборудование 🔵Отделение медицинской реабилитации Пушкинской клинической больницы имени профессора Розанова В.Н. известно на все Подмосковье современными методиками, профессионализмом врачей и своим современным, практически «космическим», оборудованием. И его арсенал продолжает пополняться и обновляться. В этом го…
👍3🔥1
Грудное вскармливание полезно для мамы и для ребенка
Showing the 5 most recent of 5 posts we hold for @pushkino_rb. 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.
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.
Named by 3 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.
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 1 seed channel's Telegram-generated recommendation list 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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“ПКБ им. проф. Розанова В.Н.” (@pushkino_rb), 2,705 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/pushkino_rb.
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.