5 measurements spanning 22 days, net -274. 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 29–390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
30 Aug 2026, 03:12
71
-13
22 Aug 2026, 08:57
84
-264
15 Aug 2026, 13:25
348
+3
8 Aug 2026, 06:50
345
no change
8 Aug 2026, 00:14
345
first reading
Engagement
8 posts held, back to 20 May 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.
ERR · 30 days
50.7%
avg views ÷ 71 subscribers
Avg views / post
36.0
1 post measured
Reaction rate
13.9%
reactions ÷ views · ER floor
Posts in window
1
of 8 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
Window
Rolling 30 days · latest post in window 3 August 2026
Posts held
8 (20 May 2026 – 3 August 2026)
Views total
36
Reactions total
5
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 06:50 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
46 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 56.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
26
56.5%
🔥
14
30.4%
👏
3
6.52%
👍
2
4.35%
😁
1
2.17%
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 8 of the 8 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 20 May 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.
🔐 Залоги в WeRent: меньше ручной работы
Теперь вы можете принимать и возвращать залоги гостей прямо через WeRent
Как это работает:
🔹 Укажите стандартную сумму залога для объекта — она будет автоматически добавляться в новые бронирования.
🔹 Гость получает персональную ссылку и оплачивает залог через ЮKassa.
🔹 Статус оплаты отображается в бронировании: вы сразу видите, какие залоги оплачены, а какие ещё ожидают оп…
⚡️ Новый календарь для одного объекта уже в WeRent!
Мы добавили одинарную шахматку, чтобы работать с одним объектом стало ещё удобнее.
🔹 Если у вас 1 активный объект, при открытии раздела «Календарь» теперь автоматически открывается одинарная шахматка вместо мультишахматки.
Что это дает?
✅ На экране видно больше дат.
✅ Удобнее просматривать бронирования.
✅ Проще управлять ценами.
✅ Быстрее ориентироваться в распи…
🚀 Bronevik теперь доступен в WeRent!
Подключайте Bronevik и управляйте им так же удобно, как и другими каналами бронирования.
Всё в одном месте:
🔹 бронирования
🔹 цены
🔹 календарь
⚡️ Данные синхронизируются автоматически — без ручных обновлений.
Как подключить Bronevik?
https://werent.me/help/channel_bronevik/
🎉WeRent х Domiksmart - новая интеграция!
Теперь вы можете подключить Domiksmart в WeRent, и управлять им так же, как и другими площадками.
🔹бронирования
🔹цены
🔹календарь
⚡️Всё синхронизируется автоматически.
Как подключить?
https://werent.me/help/channel_domiksmart/
⚡️Подготовка к подключению WeRent, если у вас уже настроены iCal-синхронизации.
Многие пользователи до подключения WeRent связывают календари между сервисами напрямую через iCal. Это помогает избегать пересечений бронирований, когда сервисы работают отдельно друг от друга.
Но после подключения WeRent старая схема больше не нужна.
Теперь именно WeRent становится центром управления календарями и бронированиями:
🔹все…
⚡Как перейти в WeRent из другой системы управления?
При переходе нельзя просто подключить площадки в WeRent поверх старой синхронизации.
Если объект всё ещё подключён к другой системе, могут возникнуть проблемы с:
• ценами
• доступностью
• передачей броней
Главное правило:
сначала отключите площадки от старой системы - и только потом подключайте их в WeRent
Инструкция по переходу:
https://werent.me/help/change_p…
🎉Новая функция в WeRent - доплата за гостя в модуле бронирования
Теперь вы можете настроить доплату за каждого дополнительного гостя прямо в объявлении 🏡
Как включить?
1. Зайдите в раздел «Мои объявления»
2. Нажмите «Редактировать»
3. В разделе «Доплата» укажите:
• лимит гостей без доплаты
• стоимость за каждого гостя сверх лимита
✨ Готово! Система автоматически рассчитает доплату при бронировании через модуль
🎉Новая функция WeRent - доплата за гостей!
Теперь вы можете получать дополнительную прибыль за каждого гостя сверх базового количества.
Как подключить?
📌 Авито
Инструкция
📌 Суточно
Инструкция
📌 Островок
Инструкция
Остались вопросы?
Пишите в комментариях👇🏻
❤5
Showing the 8 most recent of 8 posts we hold for @werentme. 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.
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 30 August 2026 — this
entry's latest reading, not the date you are reading this.
“WeRent” (@werentme), 71 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/werentme.
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.