Channel
@hrammolokovo
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
303subscribers
+2 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001577691176 |
|---|---|
| Type | Channel |
| Username | @hrammolokovo |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/hrammolokovo |
Religion — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 21:59 | 303 | -1 |
| 10 Sept 2026, 11:56 | 304 | +3 |
| 31 Aug 2026, 18:26 | 301 | no change |
| 31 Aug 2026, 03:33 | 301 | first reading |
13 posts held, back to 14 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 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.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 13 (14 August 2026 – 28 August 2026) |
| Views total | 257 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 03:33 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.
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.
С Праздником Успения Пресвятой Владычицы нашей Богородицы и Приснодевы Марии! Этот праздник завершает церковный год, он - как определенный итог нашего годичного круга в церковной жизни. А далее - Рождество Богородицы, как начало земного круга. Кто не смог быть на чине погребения Пресвятой Богородицы, можно самим почитать последование службы, особенно Статии (они после шестопсалмия, листайте), это перемежающиеся сти…
Друзья, 28 августа мы празднуем Успение Пресвятой Богородицы, один из двенадцати самых важных праздников годового круга (двунадесятый). Богослужения в нашем храме на Успение: 🌿 27 августа праздничное Всенощное бдение в 16:00. 🌿 28 августа праздничная Божественная литургия в 8:00. 🌿 28 августа молебен ко Пресвятой Богородице в Андреевском храме в 12:00. 🌿 28 августа Утреня с торжественным чином Погребения Пресвятой Б…
Немного о нашем новом мозаичном образе Богородицы: https://vk.ru/wall-61134819_4016
File, posted without a caption
С воскресным днем! 16 И вот, некто, подойдя, сказал Ему: Учитель благий! что сделать мне доброго, чтобы иметь жизнь вечную? 17 Он же сказал ему: что ты называешь Меня благим? Никто не благ, как только один Бог. Если же хочешь войти в жизнь вечную, соблюди заповеди. 18 Говорит Ему: какие? Иисус же сказал: не убивай; не прелюбодействуй; не кради; не лжесвидетельствуй; 19 почитай отца и мать; и: люби ближнего твоего, к…
Дорогие прихожане, предлагаем вашему вниманию интервью с протоиереем Валерием Бодровым, настоятелем Казанского храма с 1991 по 2009 годы. Интервью опубликовано в газете Мирянин за июль 2026 г.
Photo, posted without a caption
Photo, posted without a caption
File, posted without a caption
С праздником Преображения Господа Бога и Спаса нашего Иисуса Христа!
23 Посему Царство Небесное подобно царю, который захотел сосчитаться с рабами своими; 24 когда начал он считаться, приведен был к нему некто, который должен был ему десять тысяч талантов; 25 а как он не имел, чем заплатить, то государь его приказал продать его, и жену его, и детей, и всё, что он имел, и заплатить; 26 тогда раб тот пал, и, кланяясь ему, говорил: государь! потерпи на мне, и всё тебе заплачу. 27 Государ…
С воскресным днем и продолжением Успенского поста! 18 августа в 16:00 праздничное Всенощное бдение, 19 августа - великий двунадесятый праздник Преображения Господня, Литургия в 8:00.
Showing the 12 most recent of 13 posts we hold for @hrammolokovo. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Казанский храм с. Молоково, приход. Новости, анонсы, помощь.” (@hrammolokovo), 303 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hrammolokovo.
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.