Telegram RegisterThe public register of Telegram
Telegram profile photo for Реновация Восточное Измайлово

Supergroup

Реновация Восточное Измайлово

@renovaciyaizmaylovo

On this record: Topic · Previous handles · Growth · Engagement · Cite this entry

1,073members

No longer on Telegram — last measured 7 October 2026

+5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002335057469
TypeSupergroup
Username@renovaciyaizmaylovo
DescriptionУважаемые соседи! Чат был создан для обмена информацией о процессе реновации нашего района. Приветствуется любая информация полезная для обсуждения вопросов реновации. Данные, публикуемые в чате взяты из общедоступных источников.
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live7 October 2026
Measurements held14
On Telegramt.me/renovaciyaizmaylovo

Topic

Local community — 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 7 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Previous handles

@renovaciyaizmaylovo was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@renovaciyaizmaylovo
held 7 October 2026 – 7 October 2026

Growth

1,0681,0931,080.57 August 2026 — 1,068 members11 August 2026 — 1,093 members15 August 2026 — 1,091 members21 August 2026 — 1,090 members24 August 2026 — 1,087 members27 August 2026 — 1,083 members30 August 2026 — 1,082 members2 September 2026 — 1,081 members6 September 2026 — 1,080 members11 September 2026 — 1,078 members15 September 2026 — 1,077 members26 September 2026 — 1,075 members5 October 2026 — 1,073 members7 October 2026 — 1,073 members1,0737 August 20267 October 2026
14 measurements spanning 60 days, net +5. 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,064–1,097 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
7 Oct 2026, 05:271,073no change
5 Oct 2026, 05:161,073-2
26 Sept 2026, 18:021,075-2
15 Sept 2026, 06:411,077-1
11 Sept 2026, 14:391,078-2
6 Sept 2026, 13:371,080-1
2 Sept 2026, 12:291,081-1
30 Aug 2026, 15:041,082-1
27 Aug 2026, 23:031,083-4
24 Aug 2026, 19:291,087-3
21 Aug 2026, 14:441,090-1
15 Aug 2026, 10:051,091-2
11 Aug 2026, 14:351,093+25
7 Aug 2026, 17:521,068first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“Реновация Восточное Измайлово” (@renovaciyaizmaylovo), 1,073 members as measured 7 October 2026. Telegram Register, tgregister.com/channel/renovaciyaizmaylovo.

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.