Telegram RegisterThe public register of Telegram
Telegram profile photo for 🌸СА́ВИТРИ🌸 Клуб духовного развития

Channel

🌸СА́ВИТРИ🌸 Клуб духовного развития

@SAVITRI_CLUB

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

399subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002076358116
TypeChannel
Username@SAVITRI_CLUB
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/SAVITRI_CLUB

Growth

396399397.57 August 2026 — 398 subscribers8 August 2026 — 398 subscribers15 August 2026 — 396 subscribers22 August 2026 — 399 subscribers7 August 202622 August 2026
4 measurements spanning 14 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 396–399 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 05:44399+3
15 Aug 2026, 07:26396-2
8 Aug 2026, 05:50398no change
7 Aug 2026, 17:52398first reading

Engagement

10 posts held, back to 10 July 2026the 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.

ERR · 30 days
7.83%
avg views ÷ 399 subscribers
Avg views / post
31.3
8 posts measured
Reaction rate
20.0%
reactions ÷ views · ER floor
Posts in window
8
of 10 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. It is computed over the 1 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held10 (10 July 20266 August 2026)
Views total250
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05: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.

What this channel posts

Video runtime
59s
Average length
20s

Measured directly from 3 videos 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

11 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11100.0%

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 2 of the 10 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 11reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 10 July 2026 to 6 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

6 Aug 2026, 05:50 UTC31 viewsread 8 August 2026

Присоединяйся к каналу по ссылке: https://max.ru/join/1TIWlRsw-EQBHFzdXMcfp6wGmP052gNN8PMYI6Orwoo

6 Aug 2026, 05:50 UTC32 viewsread 8 August 2026

‼️‼️‼️‼️‼️‼️‼️ Если вам сейчас удобнее читать в Максе, то там у меня тоже есть канал-дублёр. Проходите по ссылке и подписывайтесь👍

6 Aug 2026, 05:41 UTC34 viewsread 8 August 2026

Августовское затмение для них — не просто внешнее событие, а личное зеркало, потому что оно задевает те же градусы, что и в момент их рождения. Им стоит прожить этот период как второй день рождения: с уважением к себе, с готовностью принять перемены, но без спешки. Если вы узнали себя в этом абзаце — доверьтесь своей интуиции, она сейчас обостряется до предела. Остальные знаки тоже не останутся в стороне, но для ни

6 Aug 2026, 05:39 UTC28 viewsread 8 August 2026
Photo

Полное Солнечное затмение 12 августа уже сейчас начинает ощущаться на уровне подсознания — как предчувствие, как звоночек, который трудно игнорировать. ☀️ Что вообще происходит во время солнечного затмения? Если совсем просто: Луна на мгновение встаёт между нами и Солнцем, и свет на несколько минут гаснет. В астрологии этот момент считается сверхзаряженным новолунием, только действует оно не как обычное начало цикл

6 Aug 2026, 05:30 UTC28 viewsread 8 August 2026
Photo

А здесь прочтите рекомендации поведения в этот день и практику, которая усилит благоприятное влияние затмения🌒

6 Aug 2026, 05:23 UTC27 viewsread 8 August 2026
Video

12 АВГУСТА - СОЛНЕЧНОЕ ЗАТМЕНИЕ 12 августа в 20:37 по Москве произойдёт солнечное затмение. Это солнечное затмение будет находиться в знаке Льва. Оно обещает быть особенно значимым, так как затрагивает такие сферы, как творчество и лидерство. Лев — знак, символизирующий уверенность и харизму, что даёт шанс многим проявить себя, заявить о своих талантах и оставить след в истории. Солнечное затмение во Льве ярко п

6 Aug 2026, 04:41 UTC35 views7 reactionsread 8 August 2026
Photo

🌑 КОРИДОР ЗАТМЕНИЙ - ВРЕМЯ ДЛЯ ИЗМЕНЕНИЯ СУДЬБЫ 🌑 💯 ❗️Событие года начнётся 12 августа 2026 года (Солнечное затмение) - по 28 августа 2026 года (Лунное затмение). 💥 Период между затмениями - это уникальное время для позитивной трансформации судьбы! Есть шанс кардинально собственными усилиями повлиять на важные сферы жизни. Вам понадобится верное и уверенное решение + страстное позитивное желание, мощный энергетичес

7

6 Aug 2026, 04:33 UTC35 viewsread 8 August 2026

Добрый день, дорогие друзья 🌿 После долгого перерыва возвращаюсь в канал. Лето получается очень насыщенным и не успевается писать и публиковать посты. Но впереди очень важные события, поэтому не пропустите!!!

10 Jul 2026, 13:03 UTC111 viewsread 8 August 2026
Photo

Всем доброго дня, дорогие друзья!🌸 Я вернулась с чудесного фестиваля, где окунулась во все прелести лета : сплав по реке, походы с палатками, восхождение в горы, купание в озёрах... Это всё прекрасно!!! Но это не главное...

Showing the 10 most recent of 10 posts we hold for @SAVITRI_CLUB. 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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“🌸СА́ВИТРИ🌸 Клуб духовного развития” (@SAVITRI_CLUB), 399 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/SAVITRI_CLUB.

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.