Telegram RegisterThe public register of Telegram
Telegram profile photo for N2

Supergroup

N2

@moskva_kvartiri2

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

1,188members

-63 since we began measuring on 7 August 2026

7 online right now

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

Register entry

Telegram ID-1001646429642
TypeSupergroup
Username@moskva_kvartiri2
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 October 2026
Last confirmed live6 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/moskva_kvartiri2

Topic

Real estate — 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 4 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

1,1671,2661,216.57 August 2026 — 1,251 members8 August 2026 — 1,256 members11 August 2026 — 1,247 members14 August 2026 — 1,249 members17 August 2026 — 1,254 members20 August 2026 — 1,264 members24 August 2026 — 1,256 members27 August 2026 — 1,257 members30 August 2026 — 1,264 members2 September 2026 — 1,266 members7 September 2026 — 1,248 members11 September 2026 — 1,249 members15 September 2026 — 1,238 members27 September 2026 — 1,211 members4 October 2026 — 1,211 members5 October 2026 — 1,198 members11 October 2026 — 1,185 members14 October 2026 — 1,187 members17 October 2026 — 1,185 members19 October 2026 — 1,178 members22 October 2026 — 1,167 members25 October 2026 — 1,172 members28 October 2026 — 1,180 members30 October 2026 — 1,170 members2 November 2026 — 1,176 members6 November 2026 — 1,188 members1,1887 August 20266 November 2026
26 measurements spanning 91 days, net -63. 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,152–1,281 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 26
Measured (UTC)MembersChange
6 Nov 2026, 01:561,188+12
2 Nov 2026, 20:261,176+6
30 Oct 2026, 18:361,170-10
28 Oct 2026, 05:191,180+8
25 Oct 2026, 07:161,172+5
22 Oct 2026, 17:371,167-11
19 Oct 2026, 19:291,178-7
17 Oct 2026, 02:551,185-2
14 Oct 2026, 12:011,187+2
11 Oct 2026, 09:551,185-13
5 Oct 2026, 10:551,198-13
4 Oct 2026, 03:311,211no change
27 Sept 2026, 18:401,211-27
15 Sept 2026, 11:011,238-11
11 Sept 2026, 12:021,249+1
7 Sept 2026, 01:171,248-18
2 Sept 2026, 05:481,266+2
30 Aug 2026, 14:081,264+7
27 Aug 2026, 20:041,257+1
24 Aug 2026, 21:551,256first 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“N2” (@moskva_kvartiri2), 1,188 members as measured 6 November 2026. Telegram Register, tgregister.com/channel/moskva_kvartiri2.

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.