Telegram RegisterThe public register of Telegram
Telegram profile photo for Росприроднадзор

Channel

Росприроднадзор

@rpngovru

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

1,691subscribers

-12 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001370475320
TypeChannel
Username@rpngovru
Created6 September 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held12
Confirmed unchanged2 times, most recently 19 September 2026
On Telegramt.me/rpngovru

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 53% 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. They sit inside a group of 3 channels that share the same post bodies with each other. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Rosprirodnadzor_official/31323 Aug 2026, 09:04 UTC@rpngovru/3274 · this entry3 Aug 2026, 09:12 UTC0.957 minutes
@Rosprirodnadzor_official/31355 Aug 2026, 07:59 UTC@rpngovru/3277 · this entry5 Aug 2026, 08:06 UTC0.946 minutes
@Rosprirodnadzor_official/31365 Aug 2026, 08:59 UTC@rpngovru/3278 · this entry5 Aug 2026, 09:25 UTC0.9426 minutes
@Rosprirodnadzor_official/31344 Aug 2026, 08:59 UTC@rpngovru/3276 · this entry4 Aug 2026, 09:12 UTC0.9413 minutes
@Rosprirodnadzor_official/31333 Aug 2026, 12:04 UTC@rpngovru/3275 · this entry3 Aug 2026, 12:34 UTC0.9329 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Rosprirodnadzor_official5 (5/5 hand-verifiable sample passed)0.9413 minutes@Rosprirodnadzor_official (50)

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. None of the 5 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 28 July 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 3, the earliest publisher we hold is @Rosprirodnadzor_official. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 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 2 other registered channels, 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

1,6911,7041,697.56 August 2026 — 1,703 subscribers6 August 2026 — 1,703 subscribers7 August 2026 — 1,704 subscribers10 August 2026 — 1,703 subscribers17 August 2026 — 1,700 subscribers24 August 2026 — 1,702 subscribers27 August 2026 — 1,700 subscribers30 August 2026 — 1,698 subscribers3 September 2026 — 1,696 subscribers7 September 2026 — 1,692 subscribers11 September 2026 — 1,693 subscribers15 September 2026 — 1,691 subscribers6 August 202615 September 2026
12 measurements spanning 39 days, net -12. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,689–1,706 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 01:361,691-2
11 Sept 2026, 18:211,693+1
7 Sept 2026, 09:581,692-4
3 Sept 2026, 01:021,696-2
30 Aug 2026, 16:421,698-2
27 Aug 2026, 11:071,700-2
24 Aug 2026, 19:151,702+2
17 Aug 2026, 11:571,700-3
10 Aug 2026, 09:371,703-1
7 Aug 2026, 00:281,704+1
6 Aug 2026, 20:011,703no change
6 Aug 2026, 19:521,703first reading

Engagement

19 posts held, back to 28 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
15s
Average length
15s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

7 Aug 2026, 09:23 UTC35 viewsread 7 August 2026
Photo

Росприроднадзор выявил слив отходов в Дон 6 августа. / ВЕРСИЯ /. Инспекторы Центрально-Черноземного управления Росприроднадзора провели проверку очистных сооружений, находящихся в ведении МУП «Аквасервис», и зафиксировали целый ряд серьезных отклонений от природоохранных норм. Как установили специалисты, утвержденная программа производственного экологического мониторинга не отвечает предъявляемым требованиям, полно

6 Aug 2026, 10:29 UTC55 viewsread 7 August 2026
Photo

Росприроднадзор (VK) Суды трех инстанций поддержали требование Приамурского межрегионального управления Росприроднадзора о взыскании с жителя Амурской области более 9,6 млн рублей. 🟢 Установлено, что в феврале 2024 года нарушитель сбросил жидкие бытовые отходы на земельный участок. В результате загрязненной оказалась территория площадью 2210 м². Размер ущерба, причиненного окружающей среде, составил 9,6 млн рублей

6 Aug 2026, 08:52 UTC54 viewsread 7 August 2026

Новосибирский регоператор ТКО намерен оспорить требование Росприроднадзора Ведомство потребовало выплатить компанию 2,14 млрд рублей за негативное воздействие на окружающую среду в 2025 году 6 августа. /ТАСС/. Региональный оператор по обращению с отходами в Новосибирской области - компания "Спецавтохозяйство" (САХ) - намерен оспорить в суде требование Росприроднадзора о погашении задолженности на сумму 2,1 млрд руб

5 Aug 2026, 09:25 UTC64 viewsread 7 August 2026
Photo

Росприроднадзор (VK) Специалисты Межрегионального управления Росприроднадзора по Саратовской и Пензенской областям выявили расхождение между сведениями, указанными ООО «ИПОД» в декларации о плате за негативное воздействие на окружающую среду за 2025 год, и фактическим объемом отходов, переданных на размещение. 🟢 После проверки предприятию было направлено требование о перерасчете и внесении платы. Организация скорр

5 Aug 2026, 08:06 UTC120 viewsread 7 August 2026
Photo

Росприроднадзор (VK) 6 августа 2026 года Общественный совет при Федеральной службе по надзору в сфере природопользования проведет заседание, на котором представит ежегодный доклад за 2025 год, подготовленный экспертами Национального исследовательского университета «Высшая школа экономики». Участники заседания ознакомятся с результатами работы в 2025 году по трем ключевым направлениям: • рейтинг ведущих природоохра

4 Aug 2026, 09:12 UTC74 viewsread 7 August 2026
Photo

Росприроднадзор (VK) ООО «Управляющая компания «Предприятие жилищно-коммунального хозяйства» компенсировало ущерб, причиненный почвам, размещением отходов. 🟢 В мае 2024 года специалисты Волжско-Камского межрегионального управления выявили несанкционированное размещение отходов на земельном участке, принадлежащем компании. Это привело к загрязнению почв. Росприроднадзор оценил размер вреда в 11,7 млн рублей. Поскол

3 Aug 2026, 12:34 UTC73 viewsread 7 August 2026
Photo

Росприроднадзор (VK) Нарушение выявили инспекторы Волжско-Камского межрегионального управления Росприроднадзора во время плановой проверки. Исследования показали превышение содержания нефтепродуктов, марганца, нитритов и других загрязняющих веществ в почве. Размер причиненного окружающей среде вреда Росприроднадзор оценил более чем в 860 тыс. рублей. После обращения ведомства в Арбитражный суд Республики Татарстан

3 Aug 2026, 09:12 UTC70 viewsread 7 August 2026
Photo

Росприроднадзор (VK) Суды двух инстанций поддержали требования Росприроднадзора о взыскании с АО ХК «Якутуголь» более 3 млн рублей за вред, причиненный реке Верхней Нерюнгре. 🟢 В ходе внеплановых выездных проверок объекта, оказывающего негативное воздействие на окружающую среду, инспекторы выявили сброс недостаточно очищенных сточных вод в реку Верхнюю Нерюнгру с превышением содержания загрязняющих веществ. Специа

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

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

“Росприроднадзор” (@rpngovru), 1,691 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/rpngovru.

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.