Telegram RegisterThe public register of Telegram

Channel

История создания Патриаршего подворья в «Сириусе»

@ubrus_sochi

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

1,621subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001304450235
TypeChannel
Username@ubrus_sochi
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/ubrus_sochi

Growth

1,6218 Aug 2026, 00:01 — 1,621 subscribers8 Aug 2026, 23:01 — 1,621 subscribers8 Aug 2026, 00:018 Aug 2026, 23:01
2 measurements taken within a single day. 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,619–1,623 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 23:011,621no change
8 Aug 2026, 00:011,621first reading

Engagement

20 posts held, back to 21 March 2024the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 2 September 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
11m 41s
Average length
11m 41s

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

2 Sept 2024, 17:02 UTC≈4,170 viewsread 8 August 2026
Video

Доброго вечера дорогие друзья! С памятью пророка Самуила поздравляю Вас! Крепости духа и спасения души желаю и всего что неизменно к этому главному в нашей жизни, ~ прилагается! По просьбам подписчиков, прикрепляю обращение отдельным файлом…🙏🏽

29 Aug 2024, 18:06 UTC≈5,060 viewsread 8 August 2026

Добрый вечер дорогие читатели канала. С Престольным Праздником Храма Нерукотворного Образа Христа Спасителя поздравляю Вас! ㅤ Как вы уже заметили, канал Храма Нерукотворного Образа Христа Спасителя, который действует с момента его открытия в 2014 году, переименован в «Историю создания Патриаршего подворья в «Сириусе»» Я, Эксузян Сурен Арутюнович являюсь создателем этого канала. Предлагаю вашему вниманию моё открыт

29 Aug 2024, 17:15 UTCviews —

Channel name was changed to «История создания Патриаршего подворья в «Сириусе»»

9 Apr 2024, 18:47 UTC≈7,920 viewsread 8 August 2026
Forwarded from @XXC_Sochi

Посмотрел это видео и подумал, что это может быть примером того, как Бог защищает верующих в Него и принимающих Святое Причастие от нападения дьявольских сил.

Signed Gelevan Ivan

9 Apr 2024, 06:05 UTC≈7,240 viewsread 8 August 2026
Forwarded from @XXC_Sochi

Братья и сестры! Просим ваших молитв о здравии рабы Божьей Галины. Она трудилась в церковной лавке нашего храма. Случился инсульт. Молитвенно желаем ей скорейшего исцеления и просим Господа «Рабу Твою Галину немощствующу посети и исцели ея возставив от одра и немощи».

Signed Gelevan Ivan

5 Apr 2024, 06:05 UTC≈4,550 viewsread 8 August 2026
Forwarded from @XXC_SochiPhoto

Поздравляем Митрополита Екатеринодарского и Кубанского Василия с Днем Ангела!!! Желаем владыке милости Божьей, крепости сил и мудрости в управлении Кубанской митрополией! Многая и благая лета!!!

Signed Gelevan Ivan

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

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

“История создания Патриаршего подворья в «Сириусе»” (@ubrus_sochi), 1,621 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ubrus_sochi.

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.