Telegram RegisterThe public register of Telegram
Telegram profile photo for Панорамы Воронежа

Channel

Панорамы Воронежа

@voronezh360

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

7subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003026089835
TypeChannel
Username@voronezh360
Created27 August 2025measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live31 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 31 August 2026
On Telegramt.me/voronezh360

Growth

787.57 August 2026 — 8 subscribers12 August 2026 — 8 subscribers23 August 2026 — 7 subscribers7 August 202623 August 2026
3 measurements spanning 16 days, 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 7–8 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 15:177-1
12 Aug 2026, 15:478no change
7 Aug 2026, 13:128first reading

Engagement

10 posts held, back to 27 August 2025the 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.

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

What this channel posts

Video runtime
2m 19s
Average length
28s

Measured directly from 5 videos 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.

Reaction mix

11 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 54.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
654.5%
🔥327.3%
👍218.2%

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 9 of the 10 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 27 August 2025 to 28 December 2025, 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

28 Dec 2025, 12:56 UTC50 views1 reactionsread 12 August 2026
Video

Новогодняя елка на площади Ленина.

1

21 Dec 2025, 07:24 UTC57 views2 reactionsread 12 August 2026
Photo

Театр кукол - место, где живёт сказка. Приглашаем вас в гости. ** ЗАЙТИ **

🔥2

3 Dec 2025, 08:47 UTC61 views1 reactionsread 12 August 2026
Photo

Кольцовский сквер любимое место жителей Воронежа. Можно виртуально прогуляться по скверу и заглянуть в самые укромные уголки. **ПРОГУЛЯТЬСЯ**

🔥1

2 Dec 2025, 10:47 UTC54 views1 reactionsread 12 August 2026
Photo

В первые дни зимы хочется вспомнить о теплом лете. Прогуляться по залитому Солнцем парку "Динамо". **СМОТРЕТЬ**

1

2 Dec 2025, 10:38 UTC47 views2 reactionsread 12 August 2026
Video

Желаете увидеть фонтан парка Динамо в новом ракурсе? Пожалуйста!😉

2

30 Sept 2025, 13:04 UTC112 views1 reactionsread 12 August 2026
Photo

А вы бывали на пирсе Чернавского моста? Нет? Взгляните какой шикарный вид открывается от туда. **СМОТРЕТЬ**

👍1

30 Sept 2025, 12:58 UTC102 views1 reactionsread 12 August 2026
Video

Белки из парка "Алые паруса" серьёзные ребята.

1

30 Sept 2025, 12:42 UTC96 views1 reactionsread 12 August 2026
Video

Милашка Бим, на своем месте.

1

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

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

“Панорамы Воронежа” (@voronezh360), 7 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/voronezh360.

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.