Telegram RegisterThe public register of Telegram
Telegram profile photo for Галина Болотова

Channel

Галина Болотова

@bolotova1175

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

193subscribers

+3 since we began measuring on 30 August 2026

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

Register entry

Telegram ID-1001714737015
TypeChannel
Username@bolotova1175
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live15 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 15 September 2026
On Telegramt.me/bolotova1175

Growth

190193191.530 August 2026 — 190 subscribers30 August 2026 — 190 subscribers7 September 2026 — 193 subscribers30 August 20267 September 2026
3 measurements spanning 9 days, net +3. 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 190–193 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 18:41193+3
30 Aug 2026, 11:47190no change
30 Aug 2026, 06:15190first reading

Engagement

6 posts held, back to 27 August 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
4.23%
avg views ÷ 193 subscribers
Avg views / post
8.2
6 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
6
of 6 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 29 August 2026
Posts held6 (27 August 2026 – 29 August 2026)
Views total49
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 06: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.

What this channel posts

Video runtime
31s
Average length
31s

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.

Recent posts

29 Aug 2026, 11:02 UTC8 viewsread 30 August 2026
Forwarded from @fedotova_khimkiPhoto

Связь поколений Сегодня в Ивакино вместе с жителями и строителями произвели закладку капсулы времени с посланием для будущих воспитанников строящегося детского сада. В послании - простые и важные слова для будущих поколений о семье, дружбе и любви к Родине. Строители рассказали, что детский сад рассчитан на 500 мест, там будут размещаться игровые комнаты, залы для музыкальных занятий и физкультуры, медицинские бло…

29 Aug 2026, 11:02 UTC7 viewsread 30 August 2026
Photo

Решения, которые формируют городскую среду Приняла участие во внеочередном заседании Совета депутатов городского округа Химки. Вместе с коллегами по депутатскому корпусу рассмотрели вопросы, требующие взвешенного подхода и конкретных решений. Важной частью повестки стал вопрос об упорядочении адресного пространства в микрорайоне Клязьма-Старбеево. Для новых многоквартирных домов утвердили наименования «1-й Олимпийс…

29 Aug 2026, 11:00 UTC7 viewsread 30 August 2026
Photo

186 лет со дня рождения Павла Брюллова — художника, который видел мир в деталях 🇷🇺 В рамках патриотической программы «Успехов V единстве поколений» сегодня вспоминаем Павла Александровича Брюллова — русского живописца-пейзажиста, архитектора и академика. 29 августа 1840 года в Павловске родился человек, чья жизнь удивительным образом объединила точные науки и искусство. Павел Брюллов окончил физико-математический …

28 Aug 2026, 13:28 UTC9 viewsread 30 August 2026
Forwarded from @gosuslugiforparents

💬 10 правил общения в родительском чате Используйте эти рекомендации для правил в своем чате. Составьте их для всех участников и закрепите — чтобы вопросы решались быстро, а переписка была комфортной для всех. ✅ Пишите не раньше 8:00 и не позже 21:00 Ночные уведомления могут разбудить детей и других родителей. Для утренних напоминаний используйте функцию отложенной отправки. ✅ Формулируйте мысль в одном сообщении …

28 Aug 2026, 13:28 UTC10 viewsread 30 August 2026
Photo

108 лет со дня рождения Лизы Чайкиной — героини-партизанки Великой Отечественной войны 🇷🇺 В рамках патриотической программы «Успехов V единстве поколений» сегодня вспоминаем Елизавету Ивановну Чайкину — Лизу Чайкину, Героя Советского Союза. 28 августа 1918 года в деревне Руно Тверской губернии родилась девочка, которой была суждена очень короткая жизнь и большая судьба. Лиза рано начала работать. Была заведующей и…

27 Aug 2026, 11:54 UTC8 viewsread 30 August 2026
Forwarded from @adm_himkiPhoto

Вот это кино! И на экранах — Химки! 🟣 27 августа — День российского кино. У Химок в этой истории — своя страница. Улицы города не раз становились съёмочной площадкой: Химки попадают в самые разные жанры современного кинематографа — от спортивных драм до фэнтези и мистики. Здесь возводят декорации, снимают эпизоды популярных сериалов и сцены для крупных кинопроектов. ✅ Мы подготовили подборку фильмов и сериалов, где…

Showing the 6 most recent of 6 posts we hold for @bolotova1175. 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.

Forward network

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.

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.

Appears in Telegram’s recommendations for other channels

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.

Академия AkStar
@akstar_music · 40,254
Telegram ranks this channel #62 of 73 here — alongside 72 others — read 30 August 2026

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.

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

“Галина Болотова” (@bolotova1175), 193 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/bolotova1175.

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.