Telegram RegisterThe public register of Telegram
Telegram profile photo for МИР КАДАСТРА

Channel

МИР КАДАСТРА

@wokad

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

359subscribers

-1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002056896978
TypeChannel
Username@wokad
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/wokad

Growth

359360359.58 August 2026 — 360 subscribers8 August 2026 — 360 subscribers28 August 2026 — 359 subscribers8 August 202628 August 2026
3 measurements spanning 21 days, net -1. 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 359–360 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 14:25359-1
8 Aug 2026, 06:34360no change
8 Aug 2026, 00:15360first reading

Engagement

10 posts held, back to 19 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 10 posts for this entry, the most recent from 6 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
55s
Average length
18s

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

85 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 67.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5767.1%
1720.0%
👏89.41%
🥰22.35%
🤩11.18%

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

Measured over the 10 most recent posts we hold, published 19 May 2025 to 6 June 2025, 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

6 Jun 2025, 06:20 UTC673 views19 reactionsread 8 August 2026
Video

В этом году мы возродили формат Конгрессов после долгого перерыва Получилось ли у нас? Да😌 Будем ли мы проводить их ещё? Конечно!

🔥162👏1

30 May 2025, 10:48 UTC798 views20 reactionsread 8 August 2026
Photo

За суетой совсем забыли сказать VII Конгресс прошел просто отлично Спасибо всем за активное участие. Было живо, интересно, местами громко😄

🔥182

29 May 2025, 07:05 UTC614 views9 reactionsread 8 August 2026
Photo

Начинаем второй день 🔴10:00 – 11:30 Круглый стол «Повышение эффективности работы при электронном взаимодействии с ОРП»: 🔵11:30 – 12:15 Кофе-брейк 🔴12:15 – 14:00 Круглый стол «Основные вопросы при выполнении кадастровых работ в отношении объектов капитального строительства» 🔵14:00 – 15:00 Обед 🔴15:00 – 17:00 Круглый стол «Концепция развития кадастровой деятельности» 🔴17:00 – 18:00 Подведение итогов VII конгресса када

🔥72

28 May 2025, 11:36 UTC501 viewsread 8 August 2026

За закрывающими документами подходите к столу регистрации

28 May 2025, 08:40 UTC473 views4 reactionsread 8 August 2026

Вторая часть 12:15 – 12:45 Ответственность 🔴при выполнении договора подряда: 🔴как защитить бизнес и кадастрового инженера; 🔴кто и за что отвечает при выполнении договора подряда. 12:45 – 13:10 Стоимость кадастровых работ (порядок составления сметы): 🔴составление сметы на выполнение работ; 🔴стоимость кадастровых работ. 13:10 – 13:30 Способы привлечения клиентов: 🔴ведение социальных сетей и сайта; 🔴реклама услуг. 1

🔥4

28 May 2025, 06:55 UTC≈1,460 views4 reactionsread 8 August 2026
Photo

Первый день Конгресса Первая часть программы: 10:00-10:10 Приветственное слово 10:10-10:30 Подведение итогов форума профессионалов в сентябре 2024 года 10:30-11:30 Кадастровая деятельность – текущее положение дел в отрасли 11:30-12:15 Кофе-брейк

🔥4

27 May 2025, 13:14 UTC410 views10 reactionsread 8 August 2026
Photo

Коробки, пакеты, проводочки.... Завтра ждём вас на Конгрессе 🥰

👏53🥰2

22 May 2025, 14:46 UTC≈1,520 views9 reactionsread 8 August 2026
Video

Показываем место, в котором будет проходить ужин в первый день Конгресса✨ Если вы уже оплатили участие в конгрессе, но хотите присоединиться к ужину, напишите нам на почту [email protected] Если вы ещё не подавали заявку на участие в Конгрессе, то это можно сделать вот тут: https://wokad.ru/заявка-на-участие/ там же можно записаться на ужин✨

4🔥4👏1

20 May 2025, 08:23 UTC≈1,380 views9 reactionsread 8 August 2026
Photo

Для тех участников Конгресса, кто ещё не знаком с Ростовом-на-Дону мы организовали обзорную экскурсию Когда: 29.05.2025 в 20:30 Стоимость: 1000 руб. Регистрация на экскурсию по ссылке: https://forms.yandex.ru/u/682c367ce010dba1f854484f/ Вы увидите: Соборную площадь, Набережную, площадь Советов, Театральную площадь, Нахичевань Эта экскурсия отлично сочетается с экскурсией по "Ростов Арене"🕺

4🔥4🤩1

19 May 2025, 09:06 UTC≈1,330 views1 reactionsread 8 August 2026
Photo

Можно начинать обратный отсчёт До VII Конгресса КИ осталось 10 дней Напоминаем, что посмотреть программу и подать заявку на участие можно на нашем сайте wokad.ru Будем рады видеть вас среди участников🤩

👏1

Showing the 10 most recent of 10 posts we hold for @wokad. 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.

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

“МИР КАДАСТРА” (@wokad), 359 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/wokad.

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.