Telegram RegisterThe public register of Telegram

Channel

Артём Глухих | Цифровая Страна

@Digital_homeland

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

661subscribers

-1 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-1003574266090
TypeChannel
Username@Digital_homeland
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/Digital_homeland

Topic

Real estate — 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 37% 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
@basis_nedvizhimost/722616 Jul 2026, 07:58 UTC@Digital_homeland/240 · this entry16 Jul 2026, 07:59 UTC1.00under a minute
@basis_nedvizhimost/723723 Jul 2026, 13:01 UTC@Digital_homeland/255 · this entry23 Jul 2026, 13:01 UTC1.00under a minute
@basis_nedvizhimost/724127 Jul 2026, 08:00 UTC@Digital_homeland/260 · this entry27 Jul 2026, 08:01 UTC1.00under a minute
@basis_nedvizhimost/724230 Jul 2026, 06:00 UTC@Digital_homeland/262 · this entry30 Jul 2026, 06:04 UTC1.004 minutes
@basis_nedvizhimost/72465 Aug 2026, 07:31 UTC@Digital_homeland/266 · this entry5 Aug 2026, 07:32 UTC1.0072 seconds
@basis_nedvizhimost/72477 Aug 2026, 07:42 UTC@Digital_homeland/267 · this entry7 Aug 2026, 07:44 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@basis_nedvizhimost6 (6/6 hand-verifiable sample passed)1.00under a minute@basis_nedvizhimost (60)

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. 1 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 9 comparable posts for this entry, running 16 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 2, the earliest publisher we hold is @basis_nedvizhimost. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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

661662661.57 Aug 2026, 18:18 — 662 subscribers8 Aug 2026, 02:35 — 662 subscribers8 Aug 2026, 07:23 — 661 subscribers7 Aug 2026, 18:188 Aug 2026, 07:23
3 measurements taken within a single day, 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 661–662 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 07:23661-1
8 Aug 2026, 02:35662no change
7 Aug 2026, 18:18662first reading

Engagement

11 posts held, back to 16 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
16.4%
avg views ÷ 661 subscribers
Avg views / post
109
11 posts measured
Reaction rate
10.5%
reactions ÷ views · ER floor
Posts in window
11
of 11 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held11 (16 July 20267 August 2026)
Views total1,195
Reactions total125
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:35 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

Video runtime
4m 36s
Average length
1m 32s

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

125 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 36.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4636.8%
2016.0%
👍2016.0%
💯1713.6%
😢108.00%
👏97.20%
🤝32.40%

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

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

7 Aug 2026, 07:44 UTC47 views8 reactionsread 8 August 2026
Video

🎁 Распаковали новый мерч. И спрятали в нём пасхалку Включайте видео — разбираем коробку с новой партией. А ближе к концу доходим до самого интересного. Деталь маленькая, глазом сразу не цепляется — но думали мы над ней дольше, чем над всем мерчем. Спойлерить не будем: заметят её далеко не все. 😉 Середина года. Лёгким это полугодие не было ни для кого в девелопменте — ставка, спрос, планы, пересобранные по три раз

🔥4💯21🤝1

5 Aug 2026, 07:32 UTC61 views7 reactionsread 8 August 2026
Video

🗓️ Бумага → ежедневник → Excel → Google-таблицы → система. Знакомый маршрут? Помните, мы спрашивали, как вы записываете дольщиков на приёмку? А вот компания, которая прошла этот путь целиком. ☝️ На видео — Яна, руководитель новосибирского отдела продаж ГК «Астон». Снимали на ЖК «Астон.Геометрия». Спросили прямо: а как вы передавали ключи раньше? Голубями, в эксельках, в блокноте? Ответ — почти слово в слово как у

3🔥3🤝1

30 Jul 2026, 06:04 UTC100 views8 reactionsread 8 August 2026
Photo

🧮 Деньги на стройке утекают в четырёх местах. Ни одного нет в отчёте А начинается всё буднично. Планёрка, прораб докладывает: переделали санузлы на трёх этажах, подрядчик накосячил. Покивали, записали, поехали дальше. Спросите на этом месте: во сколько это обошлось компании? Ответить будет некому. Такой строки в бюджете нет. Переделка размазана: тут доплатили, там бригада простояла, здесь инженер две недели перес

👍3👏2🔥2💯1

28 Jul 2026, 08:15 UTC96 views9 reactionsread 8 August 2026
Photo

Это не жадные покупатели. Это отлаженный конвейер Знаете, у застройщиков есть любимое объяснение всех бед на приёмке: «покупатель нынче пошёл жадный». Мол, люди специально ищут, к чему придраться, лишь бы урвать денег. Я долго тоже так думал. А потом присмотрелся внимательнее — и понял, что это удобная, но неправильная картинка. Дело не в жадности людей. Дело в том, что вокруг приёмки выросла целая индустрия. И у

🔥4👏2👍1💯1😢1

27 Jul 2026, 08:01 UTC107 views12 reactionsread 8 August 2026
Photo

🎤 «Внедрение за два дня обещают мошенники». Честный разговор о цифровизации стройки Наш операционный директор Александр Разин дал интервью «Движению». Без парадных формулировок — как всё устроено на самом деле. Собрали главное. Начнём с парадокса. Казалось бы, кризис — и IT-бюджет режут первым. Логично же: не до жиру. А на деле наоборот. Застройщики, которые понимают ценность цифры, инвестиции в неё увеличивают.

🔥6👍3👏3

24 Jul 2026, 10:31 UTC117 views16 reactionsread 8 August 2026

Ключевая ставка 14% Теперь точно заживем? - Заживем 🔥 - Нет, пока не заживем 😢

😢9🔥7

23 Jul 2026, 13:01 UTC121 views8 reactionsread 8 August 2026
Photo

Квартиру сегодня можно купить за один вечер. А строят её по-прежнему с блокнотом в руках Ипотеку одобряют онлайн за минуты, деньги на эскроу, договор регистрируют без визита в МФЦ. А теперь — на площадку. Инженер обходит этажи и пишет замечания в блокнот или в чат, фото — отдельной папкой. И реальное качество стройки впервые встречается с покупателем на приёмке. Когда исправлять поздно и дорого. Чувствуете разрыв?

🔥4👍2💯1🤝1

21 Jul 2026, 13:16 UTC130 views25 reactionsread 8 August 2026
Photo

Прямо сейчас происходит большой процесс гос регулирования применения ИИ в целом, и в строительстве в частности Сегодня выступил с докладом как представитель бизнеса по теме примирения ИИ в стройке. Мы как коммерческий проект нацелены на решение проблем наших клиентов, а государство решает задачу стандартизации процессов, трансформации консервативной строительной отрасли в том числе с примирением ИИ. И вот что я почу

11🔥7👍6💯1

21 Jul 2026, 10:49 UTC106 views9 reactionsread 8 August 2026
Photo

482-ФЗ: что на самом деле изменилось для застройщика Про новый закон я слышу сейчас в двух версиях. Одни говорят: «всё, застройщиков спасли, можно выдохнуть». Другие мрачно кивают: «да ничего это не поменяет». Мне кажется, правы и те, и другие. Сейчас объясню, почему. Давайте по-честному, что реально изменилось. Взыскание за недостатки теперь ограничено 3% от цены договора. Потребительский штраф срезали радикальн

4👍2🔥2💯1

19 Jul 2026, 22:11 UTC126 views12 reactionsread 8 August 2026

Испания - заслуженно 🏆

💯101🔥1

16 Jul 2026, 07:59 UTC184 views11 reactionsread 8 August 2026
Video

🔑 Отзывы о нас пишем не мы. Их говорят застройщики — от Сочи до Красноярска Со всей страны на связи. Мы не будем в сотый раз рассказывать, какой у нас классный продукт. Вместо этого — собрали, что говорят сами застройщики. Те, кто каждый день передаёт ключи, ведёт приёмку и работает с гарантией в «Базис недвижимость». Разные города. Разный масштаб. А выводы — одни и те же. Что меняется, когда передача уходит в ед

🔥6👍3👏2

Showing the 11 most recent of 11 posts we hold for @Digital_homeland. 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Артём Глухих | Цифровая Страна” (@Digital_homeland), 661 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Digital_homeland.

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.