Telegram RegisterThe public register of Telegram
Telegram profile photo for ЖК БОЛЬШАЯ СЕМЕРКА/ЖК КРЫЛЬЯ/НЕУСТОЙКА⚖

Channel

ЖК БОЛЬШАЯ СЕМЕРКА/ЖК КРЫЛЬЯ/НЕУСТОЙКА⚖

@neustoyka_ddu_krilja

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

7subscribers

+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-1001774722267
TypeChannel
Username@neustoyka_ddu_krilja
Created18 February 2022 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live6 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 6 October 2026
On Telegramt.me/neustoyka_ddu_krilja

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 73% 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.

Growth

676.57 August 2026 — 6 subscribers12 August 2026 — 6 subscribers10 September 2026 — 7 subscribers7 August 202610 September 2026
3 measurements spanning 35 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 6–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 18:417+1
12 Aug 2026, 20:046no change
7 Aug 2026, 04:506first reading

Engagement

6 posts held, back to 18 February 2022 — the 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 6 posts for this entry, the most recent from 23 September 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 Sept 2024, 20:30 UTC211 viewsread 12 August 2026
Photo

Что делать, если застройщик задерживает сдачу жилья или передал квартиру ненадлежащего качества? Знаю не по наслышке — Застройщики регулярно грешат этим. 📍Решение любого вопроса начинается с консультации опытного специалиста. Профессиональная юридическая помощь и сопровождение споров с застройщиками по договору долевого участия (ДДУ)📍 Помогу Вам в решении следующих вопросов: — взыскание неустойки в случае нарушени…

16 May 2024, 11:46 UTC11 viewsread 12 August 2026
Photo

📣Преображенским районным судом вынесено очередное успешное решение📣 В этот раз за просрочку передачи машино-места 🚌 ⚡️Более 200 000 рублей удовлетворённая судом сумма⚡️ ⚠️Для получения консультации Вы всегда можете связаться с @vburavlev ⚠️

31 Oct 2023, 19:55 UTCviews —

Channel name was changed to «ЖК БОЛЬШАЯ СЕМЕРКА/ЖК КРЫЛЬЯ/НЕУСТОЙКА⚖»

27 Jun 2023, 14:09 UTC79 viewsread 12 August 2026
Photo

Есть неустойка за нарушение сроков передачи застройщиком объекта строительства по ДДУ?Имеются строительные недостатки объекта?Смело идём в суд! Имеются вопросы и не хотите заниматься процессом самостоятельно?Тогда стоит обсудить это с профильным юристом @vburavlev напрямую! Что войдёт в работу юриста: ✅ расчет суммы неустойки; ✅ подготовка и направление досудебной претензии застройщику; ✅ подача в соответствующий с…

18 Feb 2022, 20:53 UTC153 viewsread 12 August 2026
Photo

Есть неустойка за нарушение сроков передачи застройщиком объекта строительства по ДДУ?Имеются строительные недостатки объекта?Смело идём в суд! Имеются вопросы и не хотите заниматься процессом самостоятельно?Тогда стоит обсудить это с профильным юристом @vburavlev напрямую! Что войдёт в работу юриста: ✅ расчет суммы неустойки; ✅ подготовка и направление досудебной претензии застройщику; ✅ подача в соответствующий с…

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

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“ЖК БОЛЬШАЯ СЕМЕРКА/ЖК КРЫЛЬЯ/НЕУСТОЙКА⚖” (@neustoyka_ddu_krilja), 7 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/neustoyka_ddu_krilja.

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.