Telegram RegisterThe public register of Telegram
Telegram profile photo for Жесть Старый Оскол

Channel

Жесть Старый Оскол

@zhest_st_oskol

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

7,956subscribers

-65 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001663799007
TypeChannel
Username@zhest_st_oskol
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 live17 November 2026
Measurements held29
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/zhest_st_oskol

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zhest_kursk_146/444275 Nov 2026, 09:02 UTC@zhest_st_oskol/16421 · this entry5 Nov 2026, 09:02 UTC1.00under a minute
@zhest_kursk_146/444637 Nov 2026, 09:07 UTC@zhest_st_oskol/16488 · this entry7 Nov 2026, 13:20 UTC1.004.2 hours
@zhest_kursk_146/444738 Nov 2026, 11:54 UTC@zhest_st_oskol/16512 · this entry8 Nov 2026, 18:04 UTC1.006.2 hours
@zhest_kursk_146/444949 Nov 2026, 18:04 UTC@zhest_st_oskol/16539 · this entry9 Nov 2026, 18:08 UTC1.004 minutes
@zhest_st_oskol/16657 · this entry14 Nov 2026, 09:08 UTC@zhest_kursk_146/4458014 Nov 2026, 12:54 UTC1.003.8 hours
@zhest_kursk_146/4458715 Nov 2026, 09:02 UTC@zhest_st_oskol/16699 · this entry15 Nov 2026, 18:38 UTC1.009.6 hours
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
@zhest_kursk_1466 (6/6 hand-verifiable sample passed)1.003.0 hours@zhest_kursk_146 (5–1)

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. 5 of the 5 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 403 comparable posts for this entry, running 6 August 2026 to 16 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 17 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

7,9568,0337,994.57 August 2026 — 8,021 subscribers7 August 2026 — 8,021 subscribers7 August 2026 — 8,023 subscribers10 August 2026 — 8,021 subscribers13 August 2026 — 8,024 subscribers17 August 2026 — 8,028 subscribers20 August 2026 — 8,025 subscribers23 August 2026 — 8,033 subscribers26 August 2026 — 8,032 subscribers29 August 2026 — 8,028 subscribers1 September 2026 — 8,022 subscribers6 September 2026 — 8,029 subscribers11 September 2026 — 8,030 subscribers15 September 2026 — 8,026 subscribers19 September 2026 — 8,029 subscribers29 September 2026 — 8,022 subscribers6 October 2026 — 8,016 subscribers12 October 2026 — 8,007 subscribers15 October 2026 — 8,006 subscribers18 October 2026 — 8,003 subscribers22 October 2026 — 7,998 subscribers25 October 2026 — 7,991 subscribers27 October 2026 — 7,981 subscribers30 October 2026 — 7,973 subscribers2 November 2026 — 7,971 subscribers5 November 2026 — 7,974 subscribers8 November 2026 — 7,965 subscribers12 November 2026 — 7,961 subscribers17 November 2026 — 7,956 subscribers7 August 202617 November 2026
29 measurements spanning 103 days, net -65. 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,944–8,045 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
17 Nov 2026, 22:297,956-5
12 Nov 2026, 11:057,961-4
8 Nov 2026, 14:587,965-9
5 Nov 2026, 03:297,974+3
2 Nov 2026, 12:177,971-2
30 Oct 2026, 19:217,973-8
27 Oct 2026, 19:177,981-10
25 Oct 2026, 03:147,991-7
22 Oct 2026, 00:517,998-5
18 Oct 2026, 14:308,003-3
15 Oct 2026, 13:388,006-1
12 Oct 2026, 18:298,007-9
6 Oct 2026, 14:018,016-6
29 Sept 2026, 07:018,022-7
19 Sept 2026, 07:158,029+3
15 Sept 2026, 05:398,026-4
11 Sept 2026, 17:418,030+1
6 Sept 2026, 17:578,029+7
1 Sept 2026, 23:498,022-6
29 Aug 2026, 14:058,028first reading

Engagement

483 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 49 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.73%
avg views ÷ 7,956 subscribers
Avg views / post
217
278 posts measured
Reaction rate
0.651%
reactions ÷ views · ER floor
Posts in window
278
of 483 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 59 of 278 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 17 November 2026
Posts held483 (6 August 2026 – 17 November 2026)
Views total60,292
Reactions total87
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 16:51 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

Video runtime
34m 41s
Average length
28s

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

189 reactions across 102 posts, in 11 distinct kinds. The most used accounts for 30.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5730.2%
👎2513.2%
😁2111.1%
👍2010.6%
🤬178.99%
😱157.94%
🔥147.41%
😢126.35%
🤔42.12%
👏31.59%
🤩10.529%

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

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

Advertising

Ad load
1.24%
6 of 483 posts carry an ad marker
Regulatory tokens
6
posts carrying an erid · 6 distinct tokens
Median views · ads
178
over 6 measured posts
Median views · rest
215
over 477 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2Vtzqv1DXHG13 November 20263 November 2026
2VtzqvXyQyy17 August 20267 August 2026
2VtzqwQBfft113 November 202613 November 2026
2VtzqwUeGaS19 November 20269 November 2026
2Vtzqwahust14 November 20264 November 2026
2VtzqwcSSCB128 August 202628 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 483 most recent posts we hold, published 6 August 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 13 of 278 posts held from the last 30 days (4.68%) 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).

17 Nov 2026, 16:34 UTC29 viewsread 17 November 2026

⚡️В Шебекинском округе при атаках дронов ранены три человека В селе Новая Таволжанка FPV-дрон атаковал автомобиль. Женщина получила проникающие ранения живота и грудной клетки, ее состояние оценивается как тяжелое. У мужчины непроникающие осколочные ранения головы, тела, рук и ног. Бойцы самообороны доставили пострадавших в Шебекинскую ЦРБ, машина повреждена. Второй дрон ударил по многоквартирному дому, повредив кр…

17 Nov 2026, 15:35 UTC104 viewsread 17 November 2026
Photo

Читатель прислал кадры наглой парковки возле дворца спорта «Аркада» 😞 В то время как другие автомобилисты заняли асфальтированные места на парковке, владелец иномарки решил проигнорировать правила благоустройства. Даже если мест для стоянки не было, это не повод портить газон. 📩 Стали свидетелем подобного хамства, ДТП или другого происшествия? Присылайте фото и видео в нашу предложку: https://max.ru/id312182167850…

17 Nov 2026, 14:43 UTC130 viewsread 17 November 2026
Photo

Ночью на проспекте А. Угарова ДПС задержали пьяного старооскольца 🚔 За рулем находился 19-летний молодой человек с признаками опьянения. Результат освидетельствования показал 0,600 мг/л алкоголя в выдыхаемом воздухе. Ему грозит штраф в размере 45 тысяч рублей и лишение прав на срок от полутора до двух лет. Больше ЖЕСТИ публикуем в нашем MAХ 👇🏻👇🏻👇🏻 https://max.ru/channel_zhest_stary_oskol

17 Nov 2026, 13:58 UTC143 viewsread 17 November 2026
Photo

В Старом Осколе мужчина угрожал прохожему пистолетом ради наушников В мае 2026 года 38-летний житель округа, находясь в состоянии опьянения, пристал к незнакомцу в микрорайоне Макаренко. В присутствии своих знакомых мужчина достал пневматический пистолет и направил его на прохожего. Злоумышленник потребовал отдать ему наушники. Как выяснилось, умысла на кражу у него не было — таким образом он хотел продемонстрирова…

17 Nov 2026, 13:05 UTC161 viewsread 17 November 2026
Photo

Староосколец Матвей Кисляк вошёл в топ-30 самых ценных спортсменов России ⚽️ За год его стоимость выросла с 8 до 25 млн евро — сейчас он самый дорогой игрок РПЛ. Также Кисляка признали лучшим молодым футболистом лиги в сезоне 2025/26. По упоминаниям в соцсетях он оказался на восьмом месте среди участников списка. Больше ЖЕСТИ публикуем в нашем MAХ 👇🏻👇🏻👇🏻 https://max.ru/channel_zhest_stary_oskol

17 Nov 2026, 12:21 UTC159 viewsread 17 November 2026

❗️В Белгородском округе при атаке дрона погибла женщина В селе Черемошное Белгородского округа беспилотник атаковал автомобиль. От полученных травм женщина скончалась на месте происшествия. Ее супруг получил множественные осколочные ранения рук. Бригада скорой помощи доставила пострадавшего мужчину в городскую больницу №2 Белгорода, ему оказывают необходимую медицинскую помощь. Больше ЖЕСТИ публикуем в нашем MAХ …

17 Nov 2026, 11:34 UTC162 viewsread 17 November 2026
Photo

⚡️Больше 700 000 российских сайтов могут умереть — масштабный сбой произошёл у провайдера Timeweb Несколько тысяч жалоб поступило на хостинг и их облачные сервисы всего за час — в компании подтвердили проблемы с сетевым оборудованием. Прямо сейчас по всей России фиксируют сбои в работе интернета и кучи сайтов. Больше ЖЕСТИ публикуем в нашем MAХ 👇🏻👇🏻👇🏻 https://max.ru/channel_zhest_stary_oskol

17 Nov 2026, 10:48 UTC161 viewsread 17 November 2026
Photo

В районе Харьковского шоссе обнаружили три взрывоопасных предмета времен ВОВ Взрывотехники оперативно вывезли опасные находки и ликвидировали их на специальном полигоне. Больше ЖЕСТИ публикуем в нашем MAХ 👇🏻👇🏻👇🏻 https://max.ru/channel_zhest_stary_oskol

17 Nov 2026, 09:50 UTC160 viewsread 17 November 2026

❗️Жителя Калужской области осудили за призывы к ударам по Белгороду Суд установил, что в ноябре 2022 года 38-летний мужчина оставил в Telegram комментарий под постом о последствиях ракетного удара в Вышгороде. В сообщении содержались признаки призывов к терактам и нанесению ударов по Белгороду. За это его приговорили к трем годам колонии общего режима. Помимо этого, мужчину на два года лишили права заниматься админ…

17 Nov 2026, 08:50 UTC156 views1 reactionsread 17 November 2026
Photo

🚧 Жители Старого Оскола обратили внимание на результаты благоустройства набережной пляжа «Юность» Новые пешеходные дорожки и плитка появились, однако удобных спусков к прибрежной зоне так и не сделали. Из-за отсутствия лестниц людям приходится буквально скатываться по чернозему. Обустроенные заходы находятся далеко друг от друга, поэтому горожане снова протаптывают стихийные тропинки. Местные жители недоумевают, п…

🤬1

17 Nov 2026, 08:09 UTC167 viewsread 17 November 2026
Photo

🛠 Водоканал информирует об аварийном отключении водоснабжения по следующим адресам: Старооскольский городской округ г. Старый Оскол — мкр. Макаренко 1, 20, 32, 33, 34, 35, 36, 38, 41, 41а; — детский сад № 52; — школа № 28. Больше ЖЕСТИ публикуем в нашем MAХ 👇🏻👇🏻👇🏻 https://max.ru/channel_zhest_stary_oskol

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

Posts edited after publishing

@zhest_st_oskol edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
7 November 2026
Most recent edit
12 November 2026

Posts recorded as deleted after publishing

We recorded 1 post on @zhest_st_oskol as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
10 November 2026
Most recent seen missing
10 November 2026
Median time before seen missing
12 hours
Seen missing in the last 30 days
1

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 4 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.

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

“Жесть Старый Оскол” (@zhest_st_oskol), 7,956 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/zhest_st_oskol.

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.