Telegram RegisterThe public register of Telegram
Telegram profile photo for Подслушано Воронеж

Channel

Подслушано Воронеж

@podslushano_voronezh36

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

1,503subscribers

-184 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001727671476
TypeChannel
Username@podslushano_voronezh36
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/podslushano_voronezh36

Topic

Local community — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.

Growth

1,5031,6871,5957 August 2026 — 1,687 subscribers7 August 2026 — 1,687 subscribers7 August 2026 — 1,686 subscribers11 August 2026 — 1,672 subscribers14 August 2026 — 1,663 subscribers17 August 2026 — 1,657 subscribers20 August 2026 — 1,640 subscribers24 August 2026 — 1,632 subscribers27 August 2026 — 1,630 subscribers30 August 2026 — 1,618 subscribers3 September 2026 — 1,600 subscribers8 September 2026 — 1,586 subscribers12 September 2026 — 1,561 subscribers17 September 2026 — 1,542 subscribers26 September 2026 — 1,517 subscribers5 October 2026 — 1,509 subscribers11 October 2026 — 1,503 subscribers7 August 202611 October 2026
17 measurements spanning 65 days, net -184. 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,475–1,715 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 18:161,503-6
5 Oct 2026, 03:361,509-8
26 Sept 2026, 14:371,517-25
17 Sept 2026, 04:021,542-19
12 Sept 2026, 20:151,561-25
8 Sept 2026, 11:561,586-14
3 Sept 2026, 11:001,600-18
30 Aug 2026, 19:191,618-12
27 Aug 2026, 12:321,630-2
24 Aug 2026, 20:041,632-8
20 Aug 2026, 22:561,640-17
17 Aug 2026, 16:051,657-6
14 Aug 2026, 06:571,663-9
11 Aug 2026, 04:011,672-14
7 Aug 2026, 18:141,686-1
7 Aug 2026, 07:451,687no change
7 Aug 2026, 07:361,687first reading

Engagement

13 posts held, back to 10 June 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 2 pages 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 13 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
17s
Average length
17s

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.

Reaction mix

6 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤466.7%
🔥116.7%
😁116.7%

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

Measured over the 13 most recent posts we hold, published 10 June 2026 to 5 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

5 Aug 2026, 19:16 UTC92 viewsread 7 August 2026

❗️ Аннинский, Бобровский и Бутурлиновский районы - тревога в связи с угрозой непосредственного удара БПЛА. Работают системы оповещения. 🦅

5 Aug 2026, 18:24 UTC109 viewsread 7 August 2026
Photo

Задержан !!! Подробности https://max.ru/join/Mbt7sjRQYUUzcng6fa5wOLxmq1--1aj0kRyMGJGFtrk

4 Aug 2026, 06:49 UTC125 viewsread 7 August 2026

❗️ Две жительницы Воронежской области пострадали при атаке на Архипо-Осиповку В результате удара по курортному селу в Краснодарском крае погибли 7 человек, около 40 получили ранения. Среди госпитализированных - две жительницы Воронежской области (56 и 47 лет). Глава региона выразил глубокие соболезнования семьям погибших и пожелал стойкости всем раненым.

3 Aug 2026, 19:17 UTC137 viewsread 7 August 2026
Photo

Подробности страшной трагедии https://max.ru/join/Mbt7sjRQYUUzcng6fa5wOLxmq1--1aj0kRyMGJGFtrk

3 Aug 2026, 19:16 UTC114 viewsread 7 August 2026
Photo

Друзья,у кого плохо работает тг,мы есть в Макс https://max.ru/join/Mbt7sjRQYUUzcng6fa5wOLxmq1--1aj0kRyMGJGFtrk

3 Aug 2026, 10:25 UTC123 viewsread 7 August 2026

🥵4, 5 и 6 августа термометры сойдут с ума и покажут до +35 градусов План действий на ближайшие дни: не выходить под солнце без панамки, закупаться минералкой ящиками и надеяться на кондиционеры.

3 Aug 2026, 10:17 UTC125 viewsread 7 August 2026
Photo

🏍 Под Воронежем 18-летняя девушка на «Ладе» сбила 13-летнего мотоциклиста Авария произошла 2 августа в посёлке Нижний Кисляй. На перекрёстке девушка не уступила дорогу подростку на мотоцикле, который ехал по главной. 13-летний байкер получил травмы и был доставлен в больницу. Фото: Полиция Воронежской области

22 Jul 2026, 10:01 UTC413 views2 reactionsread 7 August 2026
Photo

📚 В школьную программу включили книги об СВО и патриотические произведения. Минпросвещения дополнило перечень патриотических произведений. В новую программу вошли книги о Великой Отечественной войне, героях России и СВО. Список разделён по возрастам: 1–4, 5–9 и 10–11 классы.

🔥1😁1

1 Jul 2026, 12:52 UTC556 viewsread 7 August 2026
Photo

Два человека пострадали в серьезном ДТП на Московском проспекте. Tiguan-перевертыш всмятку, «Ниве» повезло чуть больше. Авария произошла вечером 30 июня у дома №151. 62-летний водитель Chevrolet Niva при перестроении не убедился в безопасности манёвра и врезался в попутный Volkswagen Tiguan. От удара внедорожник опрокинулся на бок и уткнулся в отбойник. Пострадали 22-летний водитель Volkswagen и его 20-летняя пас…

1 Jul 2026, 12:48 UTC352 viewsread 7 August 2026
Video

На трассе М-4 «Дон» в Богучарском районе горит грузовик Видео: TV Губерния. Воронеж

11 Jun 2026, 08:50 UTC783 views0 reactionsread 7 August 2026

😱 Умерли дети, муж и мама: сбор грибов закончился страшной трагедией для воронежской семьи 30 октября 2021 года семья из воронежского посёлка пошла в лес за грибами. Мама Кристина, папа Александр (имена изменены) и четырёхлетние двойняшки набрали сыроежек. Кристина вымочила грибы и сварила суп. Поели она и дети, отец не стал. Вечером поужинали магазинными консервами с кашей. К десяти вечера у всех троих началась р…

11 Jun 2026, 06:01 UTC645 views0 reactionsread 7 August 2026
Photo

Задержанный с 12 пакетами марихуаны воронежский актер смог избежать тюрьмы Дмитрий Лысенко уверял, что в октябре прошлого года наткнулся на куст дикорастущей конопли у реки Усманка, после чего высушил растение и расфасовал его в 14 полимерных пакетов — все для личного употребления. С 12 из этих пакетов его и задержали на трассе в январе. Сегодня стало известно, что актёр отделался штрафом в 20 тысяч рублей.

Showing the 12 most recent of 13 posts we hold for @podslushano_voronezh36. 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 11 October 2026 — this entry's latest reading, not the date you are reading this.

“Подслушано Воронеж” (@podslushano_voronezh36), 1,503 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/podslushano_voronezh36.

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.