Telegram RegisterThe public register of Telegram
Telegram profile photo for Жители Шилово (Воронеж)

Channel

Жители Шилово (Воронеж)

@zhitely_vrn

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

18,185subscribers

+303 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001796317282
TypeChannel
Username@zhitely_vrn
Description⚡︎ Самый большой канал Жителей Шилово (г.Воронеж) По рекламе: @zhitely_vrn_info_bot РКН gosuslugi.ru/snet/67376d4523bfbf2cbf4578f3
CreatedBetween 1 February 2022 and 31 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/zhitely_vrn

Topic

Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 40% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zhitely_voronezha/354985 Nov 2026, 15:44 UTC@zhitely_vrn/63291 · this entry5 Nov 2026, 15:45 UTC1.00under a minute
@zhitely_voronezha/355005 Nov 2026, 18:29 UTC@zhitely_vrn/63302 · this entry5 Nov 2026, 18:40 UTC1.0011 minutes
@zhitely_voronezha/355015 Nov 2026, 20:16 UTC@zhitely_vrn/63304 · this entry5 Nov 2026, 20:20 UTC1.004 minutes
@zhitely_voronezha/355176 Nov 2026, 19:02 UTC@zhitely_vrn/63351 · this entry6 Nov 2026, 19:02 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@zhitely_voronezha8 (8/8 hand-verifiable sample passed)1.004 minutes@zhitely_voronezha (8–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 4 of the 4 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 387 comparable posts for this entry, running 6 August 2026 to 14 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_copy, last confirmed 15 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

17,87018,18918,029.518,1857 August 202614 November 2026
64 measurements spanning 99 days, net +303. 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 17,822–18,237 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
14 Nov 2026, 05:0818,185+37
11 Nov 2026, 10:5718,148+1
9 Nov 2026, 19:0118,147-10
8 Nov 2026, 09:5618,157-1
7 Nov 2026, 03:3118,158-3
6 Nov 2026, 02:5718,161-5
5 Nov 2026, 01:2018,166-3
4 Nov 2026, 01:2918,169+4
3 Nov 2026, 04:5518,165+1
2 Nov 2026, 06:1818,164-2
1 Nov 2026, 07:3718,166-8
31 Oct 2026, 07:0418,174+2
30 Oct 2026, 07:1018,172-1
29 Oct 2026, 10:3118,173-6
28 Oct 2026, 11:5718,179-10
27 Oct 2026, 09:3118,189+20
26 Oct 2026, 06:1718,169+18
25 Oct 2026, 09:0618,151-14
24 Oct 2026, 06:4618,165+99
23 Oct 2026, 05:4118,066first reading

Engagement

825 posts held, back to 6 August 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 81 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.67%
avg views ÷ 18,185 subscribers
Avg views / post
1,030
287 posts measured
Reaction rate
0.664%
reactions ÷ views · ER floor
Posts in window
287
of 825 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 244 of 287 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 15 November 2026
Posts held825 (6 August 2026 – 15 November 2026)
Views total295,833
Reactions total1,721
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 17:13 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.

What this channel posts

Photos
≈42,100
Videos
≈8,240
Links
≈31,300

Lifetime counters from Telegram’s own channel header, read 15 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
46m 39s
Average length
19s

Measured directly from 147 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

4,314 reactions across 662 posts, in 32 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤90220.9%
👍50611.7%
🔥46410.8%
😁3157.30%
custom 63258648212542611482074.80%
😱1894.38%
🤯1693.92%
👏1673.87%
🦄1653.82%
custom 53751357225146855011463.38%
👀1262.92%
❤‍🔥1132.62%
💯992.29%
💔982.27%
🙊962.23%
🙏932.16%
🥰882.04%
😨781.81%
💘451.04%
☃400.927%
12 further kinds2084.82%

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 are Telegram’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 686 of the 825 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 4,314 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 825 most recent posts we hold, published 6 August 2026 to 15 November 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 825 we hold a reading for · 0.2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @zhitely_vrn. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 825 most recent posts we hold for this entry, published 6 August 2026 to 15 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 13 of 287 posts held from the last 30 days (4.53%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 16:21 UTC372 views1 reactionsread 15 November 2026

Posted without readable text

custom 53751357225146855011

15 Nov 2026, 15:48 UTC516 views1 reactionsread 15 November 2026
Photo

Сегодня было ну ооочень круто 👍😍 Жители Шилово ТГ✦МАХ✦ВК

❤‍🔥1

15 Nov 2026, 15:45 UTC522 views1 reactionsread 15 November 2026
Photo

😲 Небо сегодня словно треснуло пополам 😍 Жители Шилово ТГ✦МАХ✦ВК

❤1

15 Nov 2026, 15:09 UTC671 viewsread 15 November 2026
Video

«Соседи, подскажите пожалуйста куда звонить в случае аварийной ситуации, с радиатора льется вода ручьем, перекрыли, но стало сильнее!» • от подписчика • 💭 Пишите советы в комментарии 👇 Жители Шилово ТГ✦МАХ✦ВК

15 Nov 2026, 14:57 UTC685 views10 reactionsread 15 November 2026
Photo

Закат на озере 💙🌅 Так стремительно меняется небо!🌤️🌥️⛅️ ___ ©️Татьяна Землянухина Жители Шилово ТГ✦МАХ✦ВК

🥰7❤2🔥1

15 Nov 2026, 14:38 UTC735 views0 reactionsread 15 November 2026

🚰 Острогожская 168/2: воды нет, но появилась надежда! Жители дозвонились до аварийной службы по номеру 300-34-21 📞 В аварийке сообщили, что уже «разбираются» в ситуации. 🚙 Более того, поступила информация, что инженер уже выехал на место и должен запустить ПНС (насосы) Остается только ждать и надеяться, что специалист быстро решит проблему и в кранах снова появится вода. Держим кулачки! 🤞 #Острогожская #Воронеж #…

15 Nov 2026, 14:01 UTC797 views5 reactionsread 15 November 2026
Photo

🌆 Волшебное небо и сказочный закат в Шилово Жители Шилово ТГ✦МАХ✦ВК

🥰4🔥1

15 Nov 2026, 13:38 UTC864 views5 reactionsread 15 November 2026
Photo

🍁Осенние шиловские поля. • от подписчика • Жители Шилово ТГ✦МАХ✦ВК

❤2👍1🔥1🥰1

15 Nov 2026, 04:21 UTC153 viewsread 15 November 2026
Photo

☕️ Сегодня воскресенье, 15 ноября 2026 года в Воронеже: 🌄 Утро 3°C ⛅⛅⛅ 🗻 День 4°C ⛅⛅⛅ 🌇 Вечер 2°C ☁️☁️☁️ 🌃 Ночь 0°C ☁️☁️☁️ 🌿 Примета дня: Облака, плывущие против ветра, предвещают снегопад. А если небо затянуто тучами — ждите оттепели. Жители Шилово ТГ✦МАХ✦ВК

14 Nov 2026, 22:20 UTC≈1,060 views26 reactionsread 15 November 2026

💥Советский, Ленинский, Шилово тревога по БПЛА. ___ Работают системы ПВО. Жители Шилово ТГ✦МАХ✦ВК

custom 632586482125426114815😁5custom 53751357225146855014❤1💘1

14 Nov 2026, 20:36 UTC≈1,310 views6 reactionsread 15 November 2026
Photo

🤘 13 ноября в рамках проекта «Город творчества» прошёл квартирник «Акустический рок» в клубе «Шилово» Вечер получился камерным и душевным. Музыканты играли с такой отдачей, будто выступали в гостиной у друзей. Зрители подпевали, аплодировали и наслаждались каждой нотой. За чашкой ароматного чая, под любимые рок-композиции, делились впечатлениями, смеялись и просто наслаждались моментом. Вкусные печенья и другие уго…

❤3👏1💯1🔥1

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

Republishes

Channels on the register whose posts this channel has forwarded.

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 1 registered channel — 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.

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.

Воронеж VRN ️
@vrn36v · 70,099
Telegram ranks this channel #20 of 64 here — alongside 63 others — read 20 August 2026
Мой и твой Воронеж
@mtv36 · 190,164
Telegram ranks this channel #20 of 42 here — alongside 41 others — read 11 August 2026
Воронеж Сейчас
@voronezh1ru · 27,843
Telegram ranks this channel #21 of 88 here — alongside 87 others — read 9 September 2026
Новости Воронежа и Области
@smi_voronezh · 208,335
Telegram ranks this channel #21 of 61 here — alongside 60 others — read 11 August 2026
Т-Воронеж | Типичный | Новости Воронежа
@typicalvoronezh · 373,120
Telegram ranks this channel #23 of 66 here — alongside 65 others — read 10 August 2026
Большой воронежский
@voronezh_news_36 · 83,553
Telegram ranks this channel #24 of 79 here — alongside 78 others — read 18 August 2026
Тревожный Воронеж
@tre_voronezh · 51,731
Telegram ranks this channel #25 of 48 here — alongside 47 others — read 25 August 2026
Жесть Воронеж
@zhest_voronezh_136 · 61,926
Telegram ranks this channel #25 of 66 here — alongside 65 others — read 22 August 2026
Регион-36 (Воронеж с огоньком)
@voronezh_r36 · 73,333
Telegram ranks this channel #25 of 80 here — alongside 79 others — read 19 August 2026
Инцидент Воронеж
@vrinc · 64,190
Telegram ranks this channel #26 of 62 here — alongside 61 others — read 21 August 2026
МОЁ! Online. Воронеж
@moeonline · 38,002
Telegram ranks this channel #33 of 91 here — alongside 90 others — read 31 August 2026
ВОРОНЕЖ СЕГОДНЯ
@voronezh1 · 99,549
Telegram ranks this channel #33 of 67 here — alongside 66 others — read 15 August 2026
ВОРОНЕЖСКОЕ НЕБО
@nebovrn36 · 153,898
Telegram ranks this channel #35 of 39 here — alongside 38 others — read 13 August 2026
МЧС Воронежской области
@mchs36 · 27,229
Telegram ranks this channel #51 of 98 here — alongside 97 others — read 10 September 2026
Куда пойти в Воронеже | Афиша Воронежа
@go_vrn · 75,756
Telegram ranks this channel #56 of 85 here — alongside 84 others — read 19 August 2026
Гусев
@gusev_36 · 130,627
Telegram ranks this channel #56 of 83 here — alongside 82 others — read 13 August 2026
Воронеж №1
@vrn01 · 72,788
Telegram ranks this channel #63 of 84 here — alongside 83 others — read 19 August 2026
TV Губерния. Воронеж
@tvgubernia · 20,277
Telegram ranks this channel #66 of 97 here — alongside 96 others — read 28 September 2026
Блокнот Воронеж
@bloknot_vrn · 64,618
Telegram ranks this channel #69 of 88 here — alongside 87 others — read 21 August 2026
Типичный Воронеж | Настоящий
@Voronezh4 · 81,631
Telegram ranks this channel #78 of 89 here — alongside 88 others — read 21 August 2026

This channel appears in 20 seed channels' Telegram-generated recommendation lists 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Жители Шилово (Воронеж)” (@zhitely_vrn), 18,185 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/zhitely_vrn.

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.