Telegram RegisterThe public register of Telegram
Telegram profile photo for ИНТЕРУС - Плесецкая 10-1

Channel

ИНТЕРУС - Плесецкая 10-1

@ples10_1

On this record: Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,965subscribers

+2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002389622944
TypeChannel
Username@ples10_1
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held5
Confirmed unchanged3 times, most recently 27 August 2026
On Telegramt.me/ples10_1

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

2,9602,9652,962.57 August 2026 — 2,963 subscribers7 August 2026 — 2,963 subscribers11 August 2026 — 2,962 subscribers18 August 2026 — 2,960 subscribers21 August 2026 — 2,965 subscribers7 August 202621 August 2026
5 measurements spanning 14 days, net +2. 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 2,959–2,966 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 05:242,965+5
18 Aug 2026, 02:112,960-2
11 Aug 2026, 10:282,962-1
7 Aug 2026, 15:012,963no change
7 Aug 2026, 14:592,963first reading

Engagement

19 posts held, back to 29 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
59.8%
avg views ÷ 2,965 subscribers
Avg views / post
1,770
2 posts measured
Reaction rate
0.056%
reactions ÷ views · ER floor
Posts in window
2
of 19 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held19 (29 June 20263 August 2026)
Views total3,547
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:15 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.

Reaction mix

254 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 31.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎8131.9%
🤬5521.7%
👍3714.6%
🤮218.27%
👌197.48%
166.30%
😢145.51%
😱62.36%
👏20.787%
🙏20.787%
🤔10.394%

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 15 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 254reactions 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 June 2026 to 3 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.

Recent posts

3 Aug 2026, 08:32 UTC887 views1 reactionsread 8 August 2026

✅Резервный канал в мессенджере МАКС: http://max.ru/channel_interus_ples

🤮1

3 Aug 2026, 08:32 UTC≈2,660 views1 reactionsread 8 August 2026

‼Внимание 5 августа 2026 года в период с 11:00 до 16:00 компанией Невалинк будет производиться модернизация оборудования. Возможны перебои в работе интернета.

🙏1

29 Jul 2026, 12:40 UTC≈3,780 views13 reactionsread 8 August 2026

⚡️Отключение электроэнергии! В парадных 3, 4, 5 отключено электроснабжение в связи с аварией на сетях ПАО "Ленэнерго". Ведутся работы.

👎82👌1🤬1🤮1

23 Jul 2026, 17:10 UTC≈2,550 views7 reactionsread 8 August 2026

✅Резервный канал в мессенджере МАКС: http://max.ru/channel_interus_ples

🤮7

23 Jul 2026, 17:09 UTC≈2,330 viewsread 8 August 2026

‼️‼️‼️ Собственника/нанимателя квартиры 4354, просим срочно связаться с диспетчером. ☎️ +7 (911) 910-21-30 ☎️ +7 (812) 219-10-03 (доб. 6)

22 Jul 2026, 06:50 UTC≈5,160 views66 reactionsread 8 August 2026

Уважаемые жители! По вопросу отсутствия ГВС сообщаем, что по состоянию на 21.07.2026 года на вводе в дом, со стороны котельной теплоснабжающей организации не обеспечены необходимые параметры теплоносителя. Таким образом, возобновление горячего водоснабжения перенесено на 22.07.2026 года. Нагрев воды будет производиться постепенно в течение дня. Просим следить за соединением полотенцесушителя с системой ГВС. В слу

🤬30😢12👍11👎9🤮31

9 Jul 2026, 07:24 UTC≈3,550 views0 reactionsread 8 August 2026

‼️‼️‼️ Собственника/нанимателя квартиры 2579 просим срочно связаться с диспетчером. ☎️ +7 (911) 910-21-30 ☎️ +7 (812) 219-10-03 (доб. 6)

8 Jul 2026, 17:01 UTC≈6,540 views9 reactionsread 8 August 2026

⚡️⚡️⚡️Вниманию собственников, установивших накопительные водонагреватели (бойлеры)! Убедительная просьба, перекрыть стояки ГВС, т.к. холодную воду передавливает в систему ГВС, что осложняет осушение стояков.

👌72

8 Jul 2026, 12:55 UTC≈3,650 views2 reactionsread 8 August 2026

В связи с изменениями настройки приватности канала Интерус в мессенджере МАКС, публикуем новую ссылку на вступление: max.ru/channel_interus_ples ‼️Старая ссылка больше не работает

👏2

8 Jul 2026, 08:13 UTC≈4,740 views22 reactionsread 8 August 2026
Photo

Уважаемые жители! К сожалению, победить ошибку через техническую поддержку ГИС ЖКХ не удалось. Нами было направлено письмо в адрес АО "Оператор информационной системы" о необходимости проведения рабочего совещания по вопросу выработки решений имеющейся проблемы. По результатам рассмотрения нашего обращения, мы проинформируем дополнительно.

👍15👎3🤔1🤬1🤮1🙏1

7 Jul 2026, 10:11 UTC≈5,680 views42 reactionsread 8 August 2026

‼️‼️‼️‼️‼️‼️‼️‼️‼️‼️‼️ Внимание! Напоминаем, что с завтрашнего дня будет произведено отключение горячего водоснабжения со стороны ООО "Теплоэнерго". После отключения ООО "Интерус" будет осуществлять постепенный слив (осушение) стояков системы ГВС. На этот период в местах соединения полотенцесушителя с системой ГВС возможна небольшая течь. Это нормальный процесс при снижении давления. Просим следить за полотенцесу

👎18👌6👍6🤬63🤮3

7 Jul 2026, 09:48 UTC≈2,170 viewsread 8 August 2026

‼️‼️‼️ Собственников/нанимателей квартир 3323, 3388, 3401 просим срочно связаться с диспетчером. ☎️ +7 (911) 910-21-30 ☎️ +7 (812) 219-10-03 (доб. 6)

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

Citation-graph rank — 421,462 of 1,624,904entries 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

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.

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

“ИНТЕРУС - Плесецкая 10-1” (@ples10_1), 2,965 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/ples10_1.

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.