Telegram RegisterThe public register of Telegram
Telegram profile photo for Филиал ППК «Роскадастр» по ЮФО

Channel

Филиал ППК «Роскадастр» по ЮФО

@kadastr_kuban

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

646subscribers

-9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001365560046
TypeChannel
Username@kadastr_kuban
Created14 April 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/kadastr_kuban

Topic

Other / unclassifiable — 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 59% 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 2 other registered channels. They sit inside a group of 4 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 (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@rosreestr_news/36495 Aug 2026, 09:17 UTC@kadastr_kuban/3747 · this entry5 Aug 2026, 14:37 UTC0.935.3 hours
@kadastr102/11575 Aug 2026, 11:07 UTC@kadastr_kuban/3747 · this entry5 Aug 2026, 14:37 UTC0.933.5 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@rosreestr_news6 (6/6 hand-verifiable sample passed)0.995.3 hours@rosreestr_news (42)
@kadastr1025 (5/5 hand-verifiable sample passed)0.993.6 hours@kadastr102 (41)

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 0 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 16 comparable posts for this entry, running 22 July 2026 to 5 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 4, the earliest publisher we hold is @kadastr102. 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 3 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

646655650.57 August 2026 — 655 subscribers7 August 2026 — 655 subscribers14 August 2026 — 653 subscribers20 August 2026 — 649 subscribers5 September 2026 — 648 subscribers12 September 2026 — 646 subscribers7 August 202612 September 2026
6 measurements spanning 37 days, net -9. 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 645–656 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 22:58646-2
5 Sept 2026, 05:57648-1
20 Aug 2026, 14:46649-4
14 Aug 2026, 01:16653-2
7 Aug 2026, 00:47655no change
7 Aug 2026, 00:33655first reading

Engagement

16 posts held, back to 22 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 1 page 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 16 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.0%

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

Measured over the 16 most recent posts we hold, published 22 July 2026 to 5 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

5 Aug 2026, 14:37 UTC33 viewsread 7 August 2026
Forwarded from @kadastr_officialPhoto

🌐 Представители Росреестра и ППК «Роскадастр» провели совместное заседание Секретариата и Рабочей группы по инфраструктуре пространственных данных (ИПД) Межгоссовета по геодезии, картографии, кадастру и дистанционному зондированию Земли государств - участников СНГ. Обсуждалась подготовка к 48-й сессии Межгоссовета, а также вопросы наполнения и развития Геопортала СНГ (cisgeo.info). В режиме ВКС в мероприятии приняли

5 Aug 2026, 14:37 UTC31 views1 reactionsread 7 August 2026
Forwarded from @kadastr_officialPhoto

🏗️ Друзья, в преддверии 70-летия Дня строителя продолжаем рассказывать о взаимодействии ППК «Роскадастр» со строительной отраслью. По поручению Росреестра компания развивает информационное взаимодействие ФГИС ЕЦП НСПД с единой информационной системой «Стройкомплекс.РФ» Минстроя России. 📝 Автоматический обмен данными между двумя системами регламентируется соглашением об информационном взаимодействии. 📲 В системе «С

1

5 Aug 2026, 14:37 UTC27 viewsread 7 August 2026
Forwarded from @rosreestr_newsPhoto

🤩 Президент России Владимир Путин подписал закон о продлении «гаражной амнистии» на 5 лет – до сентября 2031 года 🤩 Соответствующий документ размещен на сайте официального опубликования правовых актов. Такая амнистия действует с 1 сентября 2021 года, позволяя гражданам в упрощенном порядке оформить в собственность капитальный гараж и землю под ним, причем участок предоставляется им бесплатно. 🤩 Данная инициатива бы

4 Aug 2026, 11:38 UTC38 viewsread 7 August 2026
Forwarded from @kadastr_officialPhoto

🌐 Большой Росреестр, Минэкономразвития России и Минстрой России совместно с другими заинтересованными ведомствами формируют единую систему классификации и кодирования пространственных данных (ЕСКК НСПД). Разработку классификаторов для строительной отрасли осуществляют специалисты ППК «Роскадастр». 📌 План реализации проекта утвержден Заместителем Председателя Правительства Российской Федерации Маратом Хуснуллиным от

4 Aug 2026, 08:40 UTC44 viewsread 7 August 2026
Forwarded from @rosreestr_newsPhoto

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

2 Aug 2026, 12:00 UTC53 viewsread 7 August 2026
Forwarded from @rosreestr_newsPhoto

🤩 Воскресенье – время дайджеста новостей Росреестра. Напомним о самом интересном на уходящей неделе! 🔹Олег Скуфинский дал интервью программе «Есть решение» на телеканале «Россия-24» - https://max.ru/rosreestr/AZ-y6-HECZA 🔹Руководитель Росреестра и губернатор Псковской области обсудили ключевые проекты в сфере земли и недвижимости - https://rosreestr.gov.ru/press/archive/rukovoditel-rosreestra-i-gubernator-pskovskoy

31 Jul 2026, 09:39 UTC74 viewsread 7 August 2026
Forwarded from @rosreestr_newsPhoto

🤩 На очередном заседании межведомственной рабочей группы по развитию «Национальной системы пространственных данных» обсудили результаты внедрения НСПД в регионах и статус работ по предоставлению с помощью платформы государственных и муниципальных услуг. 🤩 «Задачи, которые ставит перед ведомством руководство страны, требуют от нас опережающих темпов внедрения Единой цифровой платформы НСПД на всех уровнях. Важно уско

30 Jul 2026, 13:38 UTC67 viewsread 7 August 2026
Forwarded from @rosreestr_newsVideo

🤩 Руководитель Росреестра Олег Скуфинский дал интервью программе «Есть решение» на телеканале «Россия-24». 🤩 Беседа с телеведущей Мариной Громовой состоялась в одном из живописных мест Москвы – парке «Зарядье». 🤩Поговорили о цифровой трансформации ведомства, ключевых результатах в этой сфере и о грядущем 70-летии Дня строителя: 🔹От «болевых точек» до портала Госуслуг: какими были основные этапы цифрового развития

29 Jul 2026, 10:16 UTC65 viewsread 7 August 2026
Forwarded from @kadastr_officialPhoto

🌐 Команда Большого Росреестра приняла участие в 5-м заседании Рабочей группы БРИКС по геопространственным технологиям и их применению, представив доклад о развитии флагманского проекта ведомства – Национальной системы пространственных данных (НСПД). Представители 7 стран - Индонезии, Индии, Ирана, Китая, России, Эфиопии и Южной Африки - обсудили развитие фундаментальной геопространственной инфраструктуры для сотрудн

28 Jul 2026, 14:20 UTC54 viewsread 7 August 2026
Forwarded from @rosreestr_newsPhoto

🤩В Росреестре апробируют типовой проект внедрения искусственного интеллекта, разработанный с учетом опыта Аппарата Правительства Российской Федерации. ИИ планируют использовать для автоматизации внутренних процессов и повышения качества государственных услуг. 🤩 Подготовку пилотного проекта обсудили руководитель Росреестра Олег Скуфинский и руководство Центра развития искусственного интеллекта Аналитического центра п

27 Jul 2026, 06:25 UTC66 viewsread 7 August 2026
Photo

🗓️ 27 июля свой профессиональный праздник отмечают работники МФЦ! 🇷🇺 Благодаря вам граждане и бизнес-сообщество могут получить бесплатную и квалицированную консультацию по государственным и муниципальным услугам. Каждый день вы помогаете заявителям решать важные жизненные вопросы. От качества вашей работы зависит эффективность взаимодействия общества с органами государственной власти. 🎊 Филиал ППК «Роскадастр» позд

26 Jul 2026, 09:45 UTC73 viewsread 7 August 2026
Forwarded from @rosreestr_newsPhoto

🤩 Друзья, завершаем неделю дайджестом новостей Росреестра. Короткой строкой расскажем о самом важном. 📍По проекту «Земля для туризма» выявлено 47,6 тыс. га территорий под туристические объекты - https://rosreestr.gov.ru/press/archive/marat-khusnullin-po-proektu-zemlya-dlya-turizma-vyyavleno-47-6-tys-ga-territoriy-pod-turisticheskie-/ 📍Руководитель Росреестра и губернатор Санкт-Петербурга подвели итоги совместной ра

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

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.

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.

Росреестр
@rosreestr_news · 36,284
Telegram ranks this channel #79 of 93 here — alongside 92 others — read 1 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 12 September 2026 — this entry's latest reading, not the date you are reading this.

“Филиал ППК «Роскадастр» по ЮФО” (@kadastr_kuban), 646 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/kadastr_kuban.

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.