
Channel
Евангелие
@veragospel
On this record: Growth · Engagement · Citations · Telegram's recommendations · Cite this entry
21,434subscribers
+14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001675553133 |
|---|---|
| Type | Channel |
| Username | @veragospel |
| Created | 4 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 16 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/veragospel |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 21:45 | 21,434 | +3 |
| 16 Aug 2026, 03:03 | 21,431 | no change |
| 15 Aug 2026, 17:14 | 21,431 | +7 |
| 12 Aug 2026, 19:13 | 21,424 | -2 |
| 11 Aug 2026, 22:31 | 21,426 | +4 |
| 11 Aug 2026, 01:25 | 21,422 | +1 |
| 9 Aug 2026, 05:50 | 21,421 | +2 |
| 8 Aug 2026, 02:58 | 21,419 | -1 |
| 7 Aug 2026, 05:56 | 21,420 | -1 |
| 6 Aug 2026, 04:30 | 21,421 | +1 |
| 6 Aug 2026, 03:53 | 21,420 | first reading |
Engagement
No public post preview. We read this entry on 16 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
Citation-graph rank
Citation-graph rank — 130,555 of 1,481,502entries 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.
@pr_bogdanborchuk · 7220 postsХрам прп.Сергия Радонежского в Рогожской слободе
@sergeyradoneg · 6025 postsПравославие || Правый путь
@pravoput · 2072 postsВифлеемская звезда
@viphleemskaya_zvezda · 8162 postsНЕВСКАЯ ДРУЖИНА
@druzhinanevskogo · 1,4781 post«Элли и вторая чашка чая ☕️»
@elle_shytts · 231 postХрам Иверской иконы Божией Матери
@iverskiy · 2521 postХрам Святого мученика Вонифатия МП РПЦ в Донецке с придельным нижним храмом Прп. Шио Мгвимского на территории РНЦ.
@vonifatij · 3021 postЯна Капаева
@yana_kapaeva · 14,5171 post
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
Named by 10 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
@gospeleveryday · 4,70854 postsСвященник Богдан Борчук
@pr_bogdanborchuk · 7220 postsСкит у д. Сербишино🕊
@skit281020 · 25715 postsПравославие || Правый путь
@pravoput · 20711 postsХрамостроитель
@hramostroitel · 1023 postsТихорецкая епархия
@tiheparh · 6462 postsВифлеемская звезда
@viphleemskaya_zvezda · 8162 postsНЕВСКАЯ ДРУЖИНА
@druzhinanevskogo · 1,4781 post«Элли и вторая чашка чая ☕️»
@elle_shytts · 231 postХрам Иверской иконы Божией Матери
@iverskiy · 2521 post
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.
@pravoslavieVtelege · 99,088
Telegram ranks this channel #89 of 90 here — alongside 89 others — read 16 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Евангелие” (@veragospel), 21,434 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/veragospel.
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.