Channel
@ssmplo
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,512subscribers
-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 | -1001470901888 |
|---|---|
| Type | Channel |
| Username | @ssmplo |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/ssmplo |
Local community — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 00:21 | 1,512 | +1 |
| 16 Sept 2026, 18:17 | 1,511 | +1 |
| 8 Sept 2026, 07:58 | 1,510 | -1 |
| 2 Sept 2026, 21:15 | 1,511 | +2 |
| 31 Aug 2026, 02:54 | 1,509 | +4 |
| 28 Aug 2026, 04:23 | 1,505 | -1 |
| 25 Aug 2026, 03:41 | 1,506 | -3 |
| 18 Aug 2026, 17:23 | 1,509 | -2 |
| 15 Aug 2026, 15:43 | 1,511 | -3 |
| 11 Aug 2026, 16:31 | 1,514 | +1 |
| 7 Aug 2026, 23:46 | 1,513 | no change |
| 7 Aug 2026, 23:39 | 1,513 | first reading |
7 posts held, back to 28 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 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 7 posts for this entry, the most recent from 7 August 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.
89 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 37.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 33 | 37.1% | |
| 👍 | 21 | 23.6% | |
| custom 5461036399874565094 | 16 | 18.0% | |
| 🔥 | 10 | 11.2% | |
| 🙏 | 5 | 5.62% | |
| custom 5233730869256016719 | 2 | 2.25% | |
| 👏 | 2 | 2.25% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 6 of the 7 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 89 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 28 July 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.
Чаще всего помощь скорой беременным пациенткам - это транспортировка в больницу, но бывает и так, что медики бригады принимают непосредственное участие в одном из самых важных событий в жизни - в появлении малыша на свет! 🚑На днях в Лужском районе фельдшер скорой помощи принял роды прямо на дому. Всё прошло без осложнений, в процессе очень помогал супруг пациентки. Новорожденный сразу же громко закричал, маму с малы…
❤🔥4👍3👏2
Скорая, спасатели, санавиация, полиция, дорожные службы - сегодня утром водители, проезжавшие по федеральной трассе А-121 «Сортавала», могли наблюдать работу экстренных служб. На 31 км трассы, на площадке для стоянки автомобилей и отдыха водителей, проходили тактико-специальные учения по ликвидации последствий ДТП. По легенде учений автобус с 30 пассажирами двигался с разрешённой скоростью в направлении города Сорт…
❤🔥11👍7custom 54610363998745650943custom 52337308692560167191
Скорая помощь Ленобласти pinned a photo
Летом учащаются случаи падения детей и взрослых с высоты. Малыши не осознают опасности и опираются на москитную сетку на окнах, могут заиграться и не рассчитать силы, залезая на дерево, а взрослые часто пренебрегают техникой безопасности при прыжках в воду или при проведении ремонтных работ в дачных домах. 🚨Вчера бригады областной Станции скорой помощи трижды выезжали на вызовы с поводом «падение с высоты». КАК ВЫ …
🙏4custom 54610363998745650943custom 52337308692560167191
❗️Инфаркт не всегда сопровождается сильной болью - бывает, что человек буквально переносит его на ногах, как и произошло с 86-летней женщиной в Ломоносовском районе. В течение трёх суток её беспокоили слабость и головокружение, а началось недомогание с эмоционального потрясения - женщина была на похоронах своей знакомой, там и отметила боль между лопаток и чувство тяжести за грудиной. Дома несколько дней принимала …
❤🔥5custom 54610363998745650945🙏1
На 99‑летии Ленинградской области в Ивангороде бригады областной Станции скорой помощи были на страже здоровья гостей праздника - и не зря! За время торжества медики помогли 27 зрителям. Люди обращались к нашим специалистам с самыми разными недомоганиями: кто‑то жаловался на головную боль, у кого‑то подскочило давление, а кому‑то потребовалась помощь из‑за небольших травм. Ни один обратившийся не остался без внимани…
👍6custom 54610363998745650945🔥2
По просьбе родственников спасённого Токсовской бригадой пациента с большой радостью публикуем благодарность медикам: Максиму Буйнякову и Дарье Яруниной❤️ Если вы хотите выразить благодарность бригадам смп 📍Всеволожского, 📍Волосовского, 📍Волховского, 📍Выборгского, 📍Гатчинского, 📍Кингисеппского, 📍Киришского, 📍Кировского, 📍Ломоносовского, 📍Лужского, 📍Приозерского, 📍Сланцевского, 📍Тихвинского, 📍Тосненского районов, то …
❤🔥13🔥8👍5
Showing the 7 most recent of 7 posts we hold for @ssmplo. 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.
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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Скорая помощь Ленобласти” (@ssmplo), 1,512 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/ssmplo.
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.