Telegram RegisterThe public register of Telegram
Telegram profile photo for РязПлюс • Новости Рязани

Channel

РязПлюс • Новости Рязани

@ryazplus

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

15,178subscribers

+103 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-1002388096189
TypeChannel
Username@ryazplus
DescriptionОперативные новости Рязани и области. Главные события, происшествия, городская жизнь - всё в одном канале. Прислать новость: @Ryazplus_Bot Приобрести рекламу: @voen_kontur Мы в МАХ: https://max.ru/ryazplus
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/ryazplus

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 99% 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. This entry also forms a group of 2 channels linked by matching posts. 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
@lipetska4/356649 Aug 2026, 08:46 UTC@ryazplus/7008 · this entry9 Aug 2026, 08:47 UTC1.0072 seconds
@lipetska4/3598222 Aug 2026, 12:44 UTC@ryazplus/7160 · this entry22 Aug 2026, 13:53 UTC1.0070 minutes
@lipetska4/3605025 Aug 2026, 15:13 UTC@ryazplus/7198 · this entry25 Aug 2026, 19:34 UTC1.004.3 hours
@lipetska4/3608226 Aug 2026, 18:50 UTC@ryazplus/7213 · this entry26 Aug 2026, 18:51 UTC1.00under a minute
@lipetska4/3615730 Aug 2026, 09:00 UTC@ryazplus/7245 · this entry30 Aug 2026, 10:18 UTC1.0078 minutes
@lipetska4/3615930 Aug 2026, 11:18 UTC@ryazplus/7247 · this entry30 Aug 2026, 12:40 UTC1.0082 minutes
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
@lipetska463 (8/8 hand-verifiable sample passed)1.0081 minutes@lipetska4 (63–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. 63 of the 63 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 253 comparable posts for this entry, running 6 August 2026 to 10 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @lipetska4. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

15,01715,19915,1087 August 2026 — 15,075 subscribers7 August 2026 — 15,075 subscribers8 August 2026 — 15,068 subscribers9 August 2026 — 15,100 subscribers10 August 2026 — 15,095 subscribers11 August 2026 — 15,100 subscribers12 August 2026 — 15,099 subscribers13 August 2026 — 15,116 subscribers14 August 2026 — 15,112 subscribers17 August 2026 — 15,108 subscribers20 August 2026 — 15,109 subscribers21 August 2026 — 15,104 subscribers23 August 2026 — 15,108 subscribers24 August 2026 — 15,109 subscribers25 August 2026 — 15,102 subscribers26 August 2026 — 15,088 subscribers27 August 2026 — 15,111 subscribers30 August 2026 — 15,110 subscribers31 August 2026 — 15,113 subscribers1 September 2026 — 15,109 subscribers2 September 2026 — 15,110 subscribers3 September 2026 — 15,111 subscribers5 September 2026 — 15,108 subscribers8 September 2026 — 15,096 subscribers11 September 2026 — 15,087 subscribers13 September 2026 — 15,080 subscribers14 September 2026 — 15,074 subscribers18 September 2026 — 15,075 subscribers2 October 2026 — 15,035 subscribers7 October 2026 — 15,017 subscribers11 October 2026 — 15,019 subscribers14 October 2026 — 15,020 subscribers15 October 2026 — 15,025 subscribers16 October 2026 — 15,061 subscribers16 October 2026 — 15,059 subscribers17 October 2026 — 15,050 subscribers18 October 2026 — 15,049 subscribers19 October 2026 — 15,047 subscribers20 October 2026 — 15,041 subscribers21 October 2026 — 15,038 subscribers23 October 2026 — 15,035 subscribers24 October 2026 — 15,042 subscribers25 October 2026 — 15,039 subscribers26 October 2026 — 15,176 subscribers27 October 2026 — 15,177 subscribers28 October 2026 — 15,172 subscribers29 October 2026 — 15,162 subscribers30 October 2026 — 15,161 subscribers31 October 2026 — 15,160 subscribers1 November 2026 — 15,162 subscribers2 November 2026 — 15,161 subscribers3 November 2026 — 15,155 subscribers4 November 2026 — 15,158 subscribers5 November 2026 — 15,199 subscribers6 November 2026 — 15,198 subscribers7 November 2026 — 15,196 subscribers8 November 2026 — 15,182 subscribers10 November 2026 — 15,178 subscribers15,1787 August 202610 November 2026
58 measurements spanning 95 days, net +103. 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 14,990–15,226 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
10 Nov 2026, 12:2115,178-4
8 Nov 2026, 23:1515,182-14
7 Nov 2026, 18:4515,196-2
6 Nov 2026, 15:4115,198-1
5 Nov 2026, 13:0915,199+41
4 Nov 2026, 13:0415,158+3
3 Nov 2026, 13:2715,155-6
2 Nov 2026, 11:1015,161-1
1 Nov 2026, 12:2515,162+2
31 Oct 2026, 11:2815,160-1
30 Oct 2026, 10:0615,161-1
29 Oct 2026, 09:0615,162-10
28 Oct 2026, 05:5115,172-5
27 Oct 2026, 06:4115,177+1
26 Oct 2026, 03:1415,176+137
25 Oct 2026, 01:2815,039-3
24 Oct 2026, 01:3115,042+7
23 Oct 2026, 00:0615,035-3
21 Oct 2026, 21:1115,038-3
20 Oct 2026, 16:3915,041first reading

Engagement

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

ERR · 30 days
16.6%
avg views ÷ 15,178 subscribers
Avg views / post
2,510
97 posts measured
Reaction rate
0.815%
reactions ÷ views · ER floor
Posts in window
97
of 397 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 92 of 97 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 November 2026
Posts held397 (6 August 2026 – 11 November 2026)
Views total243,754
Reactions total1,900
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 06:56 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
≈2,680
Videos
≈484
Links
≈6,340

Lifetime counters from Telegram’s own channel header, read 11 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
13m 09s
Average length
27s

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

7,175 reactions across 382 posts, in 18 distinct kinds. The most used accounts for 23.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,71823.9%
❤1,04414.6%
👎1,00614.0%
🤡81311.3%
🤣5818.10%
🙏4225.88%
🤬3835.34%
custom 53729156839841526373344.66%
🤮2142.98%
😱1852.58%
😭1191.66%
🥰1171.63%
🔥1051.46%
🕊540.753%
🗿540.753%
🤝130.181%
🫡100.139%
🤔30.042%

Custom emoji. One row above is a 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 count beside it is 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 383 of the 397 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 7,175 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 397 most recent posts we hold, published 6 August 2026 to 11 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
6
across the posts below
Posts paid on
3
of 397 we hold a reading for · 0.8%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ryazplus. 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 397 most recent posts we hold for this entry, published 6 August 2026 to 11 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: 10 of 97 posts held from the last 30 days (10.3%) 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).

11 Nov 2026, 03:34 UTC694 views1 reactionsread 11 November 2026

🟢 Отбой режима «Опасность атаки БПЛА» по Рязанской области. 🟣 Подписаться | Написать нам | Max

🙏1

10 Nov 2026, 21:55 UTC≈1,390 views8 reactionsread 11 November 2026

⚠️ Вблизи Рязани БПЛА фиксации БПЛА транзитом в соседние регионы, — мониторинг. 🟣 Подписаться | Написать нам | Max

🥰3🙏3❤2

10 Nov 2026, 21:47 UTC≈1,530 views85 reactionsread 11 November 2026

😯 В Рязани громко: в городе работает ПВО. Вы слышали хлопок? 👍/ 👎 🟣 Подписаться | Написать нам | Max

👎47👍37🙏1

10 Nov 2026, 21:44 UTC≈1,390 views1 reactionsread 11 November 2026

🔴 Объявлен режим «Опасность атаки БПЛА» по Рязанской области. 🟣 Подписаться | Написать нам | Max

🙏1

10 Nov 2026, 17:03 UTC≈2,180 views10 reactionsread 11 November 2026

⚡️ В Рязани расширили зону ЧС после атаки БПЛА, произошедшей 5 ноября. Решение приняли из-за уточнения масштабов повреждений жилых домов и социальных объектов. В обновлённый список вошли школа №58 и адреса на следующих улицах: Олимпийский городок Предзаводская Интернациональная Бирюзова Луговая (Канищево) Московская Преображенская Княжье Поле Станкозаводская Забайкальская Пугачева Луговая (Соколовка) Загородная 4-й…

❤6😱4

10 Nov 2026, 15:05 UTC≈1,910 views8 reactionsread 11 November 2026
Photo

🚗 Девятибалльные пробки сковали Рязань вечером 10 ноября. Заторы образовались на Московском и Касимовском шоссе, Северной окружной дороге, а также на улицах Ленина, Дзержинского, Гагарина, Новосёлов и Зубковой. 🟣 Подписаться | Написать нам | Max

😱5👍3

10 Nov 2026, 13:30 UTC≈1,780 views14 reactionsread 11 November 2026

🔌 На Московском шоссе в Рязани уберут провода под землю в рамках проекта «Чистое небо». Кабельные каналы уже проложили, а завершить перенос коммуникаций планируют до 25 декабря. 🟣 Подписаться | Написать нам | Max

👍13❤1

10 Nov 2026, 11:05 UTC≈1,930 views27 reactionsread 11 November 2026

⚡️ Трёхсторонние переговоры с участием делегаций России, США и Украины стартовали в Абу-Даби. 🟣 Подписаться | Написать нам | Max

🙏18❤6🕊2🥰1

10 Nov 2026, 10:27 UTC≈2,020 views4 reactionsread 11 November 2026
Photo

👮‍♂️ Сегодня отмечается День сотрудника органов внутренних дел РФ. 🟣 Подписаться | Написать нам | Max

❤4

9 Nov 2026, 18:08 UTC≈2,380 views19 reactionsread 11 November 2026

😧 В Скопине двое мужчин ворвались в квартиру к местному жителю и пытали его утюгом ради банковского счёта, сообщили в полиции. Злоумышленники избили 42-летнего хозяина, выведали пароль от онлайн-банка и похитили 81 тысячу рублей. Подозреваемых задержали, им грозит до 12 лет лишения свободы. 🟣 Подписаться | Написать нам | Max

😱17🤣1🤬1

9 Nov 2026, 12:45 UTC≈2,450 views7 reactionsread 11 November 2026
Photo

🚗 Два человека пострадали при столкновении автомобилей Volkswagen и Haval на трассе Р-22 «Каспий» в Пронском округе. Травмы получили 33-летний водитель и 40-летняя пассажирка иномарок. Полиция устанавливает все обстоятельства произошедшего. 🟣 Подписаться | Написать нам | Max

😱5❤1🙏1

9 Nov 2026, 10:37 UTC≈2,410 views16 reactionsread 11 November 2026

🚫 Россиян не будут штрафовать за рекламу в Telegram с января 2027 года. Ограничения перенесли. «Если не случится форс-мажора, то с наступлением 2027 года ни для тех, кто ставит рекламу в каналах, ни для тех, кто её размещает, ничего не изменится». 🟣 Подписаться | Написать нам | Max

❤9🤡3😱3🤮1

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

@ryazplus edited 1 post 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
7 November 2026

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

“РязПлюс • Новости Рязани” (@ryazplus), 15,178 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/ryazplus.

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.