3 measurements spanning 6 days, net -1. 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 381–382 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 06:13
381
-1
8 Aug 2026, 06:05
382
no change
7 Aug 2026, 19:07
382
first reading
Engagement
4 posts held, back to 10 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 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 4 posts for this entry, the most recent from 2 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
5s
Average length
5s
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.
Reaction mix
131 reactions across 4 posts, in 10 distinct kinds. The most used accounts for 37.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5440718610404241986
49
37.4%
custom 5215561710189947188
18
13.7%
custom 5384522343475334333
13
9.92%
custom 5357536209256071373
11
8.40%
custom 5363988860747400777
11
8.40%
custom 5296632567976441082
10
7.63%
😘
8
6.11%
🕊
5
3.82%
custom 5291760649133641296
3
2.29%
custom 5406848317919351516
3
2.29%
Custom emoji. 8 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 areTelegram’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 4 of the 4 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 131reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 10 May 2026 to 2 June 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.
«Когда следующий концерт?» — спрашиваете вы 👀…
Если честно, мы пока сами не знаем.💔
Сейчас мы отдыхаем и переводим дух после нашего грандиозного Дня Рождения!
В ближайших планах — записать песню «Земля», а также очень хочется записать ещё две наши авторские песни!
И, конечно, как только мы определимся с датой следующего концерта, вы узнаете об этом первыми!
За прекрасные фото благодарим Свету Рубцову 💕
Друзья, вот и отгремел наш ДЕНЬ РОЖДЕНИЯ!
Нам самим не верится, что нам удалось сделать такой большой и прекрасный праздник🫶
И сегодня мы хотим сказать спасибо всем, без кого этого праздника не было бы!
В первую очередь благодарим всех вас — наших зрителей! ❤
За вашу поддержку и энергию🔥
Как же приятно было собрать такой большой зал своих людей!🫶🏻
Спасибо нашим музыкальным гостям — счастье и удовольствие быть с …
Showing the 4 most recent of 4 posts we hold for @sestrapetra. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“Сестрá Петрá” (@sestrapetra), 381 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/sestrapetra.
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.
