Telegram RegisterThe public register of Telegram

Channel

Типичные Клинцы

@tipical_klintsy

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

9,085subscribers

-6 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-1001468777722
TypeChannel
Username@tipical_klintsy
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/tipical_klintsy

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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.

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 word for word 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
@klintsyregion_32/419725 Aug 2026, 10:00 UTC@tipical_klintsy/21277 · this entry5 Aug 2026, 10:00 UTC1.00under a minute
@tipical_klintsy/21279 · this entry6 Aug 2026, 04:04 UTC@klintsyregion_32/419796 Aug 2026, 06:00 UTC1.001.9 hours
@klintsyregion_32/419856 Aug 2026, 07:09 UTC@tipical_klintsy/21286 · this entry6 Aug 2026, 07:09 UTC1.00under a minute
@tipical_klintsy/21281 · this entry6 Aug 2026, 06:01 UTC@klintsyregion_32/419866 Aug 2026, 08:01 UTC1.002.0 hours
@klintsyregion_32/419886 Aug 2026, 10:39 UTC@tipical_klintsy/21287 · this entry6 Aug 2026, 10:39 UTC1.00under a minute
@klintsyregion_32/419977 Aug 2026, 07:35 UTC@tipical_klintsy/21290 · this entry7 Aug 2026, 07:35 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@klintsyregion_3214 (8/8 hand-verifiable sample passed)1.0072 secondsthis entry (86)

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 6 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 19 comparable posts for this entry, running 4 August 2026 to 7 August 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).

Across the whole group of 2, the earliest publisher we hold is @klintsyregion_32. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

9,0859,0919,0887 August 2026 — 9,091 subscribers7 August 2026 — 9,091 subscribers8 August 2026 — 9,090 subscribers10 August 2026 — 9,091 subscribers13 August 2026 — 9,085 subscribers7 August 202613 August 2026
5 measurements spanning 6 days, net -6. 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 9,084–9,092 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 15:489,085-6
10 Aug 2026, 19:489,091+1
8 Aug 2026, 01:169,090-1
7 Aug 2026, 11:009,091no change
7 Aug 2026, 10:559,091first reading

Engagement

49 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.17%
avg views ÷ 9,085 subscribers
Avg views / post
652
49 posts measured
Reaction rate
0.818%
reactions ÷ views · ER floor
Posts in window
49
of 49 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 25 of 49 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 11 August 2026
Posts held49 (4 August 202611 August 2026)
Views total31,935
Reactions total136
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 15:36 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.

Reaction mix

136 reactions across 25 posts, in 15 distinct kinds. The most used accounts for 22.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡3122.8%
😢2216.2%
👎1611.8%
🙏1410.3%
118.09%
🤬118.09%
😱96.62%
😁64.41%
👏32.21%
🕊32.21%
🤔32.21%
🎄21.47%
👍21.47%
🫡21.47%
🔥10.735%

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

Measured over the 49 most recent posts we hold, published 4 August 2026 to 11 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

11 Aug 2026, 14:56 UTC660 views7 reactionsread 12 August 2026
Photo

В Клинцах простятся с погибшим участником специальной военной операции Максимом Шестерневым 28 марта 2026 года при выполнении задач в ходе специальной военной операции погиб уроженец Клинцов Максим Вячеславович Шестернев. Максим Шестернев родился 17 декабря 1978 года в городе Клинцы Брянской области. После окончания 9 классов школы №3 он получил профессию каменщика в ПТУ №4. С 1996 по 1998 год проходил срочную военн

🙏3😁2😢2

11 Aug 2026, 13:29 UTC647 views2 reactionsread 12 August 2026

❗️ВСУ продолжают атаковать Брянскую область В поселке Белая Березка Трубчевского района дрон-камикадзе ударил по продуктовому магазину. Осколочные ранения получила продавец. Женщине оказана вся необходимая медицинская помощь.

👍2

11 Aug 2026, 10:03 UTC624 views1 reactionsread 12 August 2026

🌾 В число лидеров России по урожайности пшеницы вошла Брянская область В Минсельхозе России сообщили, что наш регион демонстрирует одни из самых высоких показателей в стране. Брянские аграрии собирают в среднем порядка 60 центнеров зерна с одного гектара. По уровню эффективности Брянщина встала в один ряд с традиционными житницами и передовыми сельхозрегионами — Краснодарским краем, Курской и Калининградской областя

🤡1

11 Aug 2026, 09:12 UTC566 viewsread 12 August 2026
Photo

С начала года в Клинцах и районе произошло 6 пожаров в автомобилях Автомобильный пожар может произойти внезапно — от технической неисправности до короткого замыкания. С начала 2026 года на территории города Клинцы и Клинцовского района уже зафиксировано 6 случаев возгорания транспортных средств. Чтобы снизить риск серьёзных последствий, специалисты напоминают водителям о необходимости иметь в машине исправный огнету

11 Aug 2026, 06:18 UTC501 viewsread 12 August 2026

❗️ Оперативная информация За прошедшие сутки над территорией Брянской области подразделениями ПВО Министерства обороны РФ, мобильно-огневыми группами бригады «БАРС-Брянск», МОГ Брянского ЛО МВД России на транспорте, спецподразделениями Росгвардии по Брянской области уничтожено 128 вражеских БпЛА самолетного типа.

11 Aug 2026, 06:02 UTC489 views10 reactionsread 12 August 2026

💸Пенсию около 32000₽ будут получать россияне со средней зарплатой и 30 годами стажа Если гражданин официально зарабатывает в среднем около 114–120 тысяч рублей в месяц и честно отработал 30 лет трудового стажа, размер его ежемесячной пенсии составит всего около 31–32 тысяч рублей. Получается, что после выхода на заслуженный отдых уровень доходов упадет почти в четыре раза. При этом, чтобы накопить достаточное колич

🤬7😱2🎄1

11 Aug 2026, 05:01 UTC472 views4 reactionsread 12 August 2026
Photo

10 августа 2026 года, в городе Клинцы состоялась торжественная церемония вручения государственных наград. Глава города Клинцы О. П. Шкуратов, глава Клинцовской городской администрации С. Ю. Евтеев и военный комиссар города Клинцы, Клинцовского, Гордеевского и Красногорского районов А. Е. Зубиков передали медали Суворова и Жукова, а также вручили семьям военнослужащих, погибших при выполнении задач в ходе специальной

2🤡2

11 Aug 2026, 04:04 UTC505 views6 reactionsread 12 August 2026
Photo

📅 7 августа 2026 года в большом зале администрации города Клинцы состоялась встреча врио губернатора Брянской области Егора Викторовича Ковальчука с жителями города. В рамках рабочей поездки прошёл содержательный диалог с горожанами, в ходе которого обсудили ключевые вопросы развития муниципалитета. 🏭 В числе посещённых объектов — Клинцовский завод поршневых колец. Предприятие выпускает поршневые кольца для теплово

🤔3👎2😁1

10 Aug 2026, 15:31 UTC601 viewsread 12 August 2026
Photo

Не уступил дорогу электровелосипеду: житель Клинцов получил наказание за ДТП с тяжкими последствиями Клинцовский городской суд вынес приговор 34-летнему местному жителю, признанному виновным в нарушении правил дорожного движения, которое привело к причинению тяжкого вреда здоровью человека. Суд установил, что мужчина, управляя автомобилем «ВАЗ», при повороте налево с улицы Займищенской на 1-ю Путевую не предоставил

10 Aug 2026, 12:54 UTC622 viewsread 12 August 2026
Photo

Поворот на проспекте Ленина закончился столкновением: водитель мопеда госпитализирован в Клинцах Утром 9 августа в Клинцах произошло ДТП. Авария случилась около 07:45 на проспекте Ленина. По предварительной информации, 34-летний водитель «Газели» двигался в сторону улицы 8 Марта. При повороте налево он, предположительно, не убедился в безопасности манёвра и столкнулся с мопедом, который двигался навстречу. За рулё

10 Aug 2026, 06:12 UTC625 views1 reactionsread 12 August 2026

❗️Оперативная информация За прошедшие сутки над территорией Брянской области подразделениями ПВО Министерства обороны РФ, мобильно-огневыми группами бригады «БАРС-Брянск», МОГ Брянского ЛО МВД России на транспорте, спецподразделениями Росгвардии по Брянской области уничтожен 341 вражеский БпЛА самолетного типа.

😁1

10 Aug 2026, 06:03 UTC234 viewsread 10 August 2026

Избавиться от вейпов призвал регионы Володин Он потребовал от местных властей жестче взяться за электронные сигареты. Федеральный закон от 2023 года (со штрафами до 2 млн рублей и уголовкой) проблему не решил — за год число точек продаж в миллионниках просело всего на 10%. С июня 2026 года у субъектов РФ появилось право вводить полный запрет на розничную торговлю «электронками» и жидкостями. Но воспользовались им п

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

ТИПИЧНЫЙ БРЯНСК | НОВОСТИ
@tipicl32 · 159,313
Telegram ranks this channel #18 of 44 here — alongside 43 others — read 14 August 2026
ПОДСЛУШАНО БРЯНСК
@pb_032 · 300,430
Telegram ranks this channel #19 of 40 here — alongside 39 others — read 14 August 2026

This channel appears in 2 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Типичные Клинцы” (@tipical_klintsy), 9,085 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/tipical_klintsy.

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.