Telegram RegisterThe public register of Telegram

Channel

Дневник служителя

@dnevnik_vl

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,577subscribers

-1 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001442461615
TypeChannel
Username@dnevnik_vl
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/dnevnik_vl

Growth

1,5771,5781,577.511 Aug 2026, 06:30 — 1,578 subscribers12 Aug 2026, 04:18 — 1,577 subscribers11 Aug 2026, 06:3012 Aug 2026, 04:18
2 measurements taken within a single day, 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 1,577–1,578 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 04:181,577-1
11 Aug 2026, 06:301,578first reading

Engagement

20 posts held, back to 5 August 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
9.09%
avg views ÷ 1,577 subscribers
Avg views / post
143
20 posts measured
Reaction rate
3.56%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 19 of 20 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 11 August 2026
Posts held20 (5 August 202611 August 2026)
Views total2,868
Reactions total96
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 06:30 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

96 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 36.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3536.5%
❤‍🔥2627.1%
🙏2121.9%
🔥99.38%
custom 541151302176999853322.08%
👍22.08%
custom 541361983207770479311.04%

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

Measured over the 20 most recent posts we hold, published 5 August 2026 to 11 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

11 Aug 2026, 04:10 UTC37 views3 reactionsread 11 August 2026

Ищи возможности наполнять себя Божьим Словом! Когда встает выбор: поехать на христианскую конференцию, где ты услышишь хорошие проповеди или просто потусить с друзьями без какой-то доброй цели — выбирай первое💯 @dnevnik_vl

3

10 Aug 2026, 16:34 UTC85 views5 reactionsread 11 August 2026

🗡️Один из судов, который Господь обещает Своему народу — жажда Божьего Слова. В 8 главе книги Амоса звучит такое обещание: «Вот наступают дни, говорит Господь Бог, когда Я пошлю на землю голод, — не голод хлеба, не жажду воды, но жажду слышания слов Господних. И будут ходить от моря до моря и скитаться от севера к востоку, ища слова Господня, и не найдут его.» (11-12) 😩Далее написано, что даже молодые парни и девушк

❤‍🔥4🙏1

10 Aug 2026, 15:17 UTC103 views7 reactionsread 11 August 2026

Какие есть альтернативы бездумному скроллингу? - книги - учеба - прогулка - отдых - хобби - живое общение

🔥43

10 Aug 2026, 14:37 UTC82 views8 reactionsread 11 August 2026
Forwarded from @khan_suren

Почему я навсегда решил отказаться от скроллинга коротких видео? Мы живем в эпоху, когда алгоритмы знают о нашей психике больше, чем мы сами. Короткие видео — Reels, Shorts, TikTok — давно перестали быть просто развлечением. Это отлаженная система по удержанию внимания, которая незаметно меняет наши привычки, мысли и внутреннее состояние. Вот главные причины, по которым я принял решение полностью исключить их из св

❤‍🔥8

9 Aug 2026, 10:55 UTC119 views2 reactionsread 11 August 2026
Forwarded from @Biblical_exegesis_and_TheologyPhoto

📌Открытые уроки по библейским языкам в августе📌 Приглашаю всех братьев и сестёр на открытые уроки древнегреческого и древнееврейского языков. Поговорим о том, зачем изучать библейские языки, какая от этого польза и как учить их эффективно. Разберём алфавит и некоторые грамматические особенности каждого языка. Языки полезны не только семинаристам и проповедникам — они дают возможность глубже изучать Писание и сёст

2

9 Aug 2026, 09:24 UTC127 views5 reactionsread 11 August 2026

❗️Перед Иродом стоял вопрос: что он сделает с истиной, которую услышал? ❗️Перед Иоанном же стоял вопрос: что он сделает с истиной, которую ему нужно сказать? ❓Готов ли ты говорить истину, когда за нее придется платить? 📰Сергей Вязников #СлушаюПроповедь@dnevnik_vl

2❤‍🔥2🔥1

9 Aug 2026, 08:08 UTC126 views10 reactionsread 11 August 2026

Сегодня у нас в церкви много народа💒 Мечтаем о пробуждении в нашем народе и в нашей стране🙏

❤‍🔥8🙏1custom 54136198320777047931

9 Aug 2026, 08:07 UTC125 views4 reactionsread 11 August 2026
Video message

Video message, posted without a caption

❤‍🔥4

8 Aug 2026, 15:45 UTC164 views4 reactionsread 11 August 2026

Спасение заключается не просто в том, что Христос сделал что-то для меня. Оно заключается в том, что я принадлежу Христу и поэтому участвую в результатах того, что Он сделал🙌 @dnevnik_vl

🙏4

8 Aug 2026, 12:46 UTC149 views6 reactionsread 11 August 2026
Photo

Благословенное общение с братом🤝

4🔥2

8 Aug 2026, 10:10 UTC152 views2 reactionsread 11 August 2026

Каждый раз, когда Христос совершает послушание Отцу во время своего пребывания на земле, Он сознательно делает это ради нас, верующих в Него! Потому что «послушанием Одного сделаются праведными многие» (Рим. 5:19). Осознание этого раскрывает глубокую любовь Божьего Сына к Своему народу! @dnevnik_vl

custom 54115130217699985332

Showing the 12 most recent of 20 posts we hold for @dnevnik_vl. 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.

Citation-graph rank

Citation-graph rank — 1,031,568 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“Дневник служителя” (@dnevnik_vl), 1,577 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dnevnik_vl.

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.