Telegram RegisterThe public register of Telegram
Telegram profile photo for ЖК Фестиваль Парк. Open chat

Supergroup

ЖК Фестиваль Парк. Open chat

@FestivalPark

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

2,646members

+14 since we began measuring on 7 August 2026

114 online right now

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

Register entry

Telegram ID-1001362480176
TypeSupergroup
Username@FestivalPark
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live2 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/FestivalPark

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 15 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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

2,6102,6632,636.57 August 2026 — 2,632 members10 August 2026 — 2,633 members12 August 2026 — 2,628 members16 August 2026 — 2,634 members19 August 2026 — 2,662 members23 August 2026 — 2,663 members26 August 2026 — 2,646 members29 August 2026 — 2,643 members1 September 2026 — 2,630 members4 September 2026 — 2,631 members10 September 2026 — 2,629 members14 September 2026 — 2,619 members14 September 2026 — 2,619 members17 September 2026 — 2,647 members27 September 2026 — 2,635 members5 October 2026 — 2,642 members12 October 2026 — 2,633 members15 October 2026 — 2,627 members18 October 2026 — 2,610 members21 October 2026 — 2,626 members24 October 2026 — 2,631 members27 October 2026 — 2,628 members30 October 2026 — 2,649 members2 November 2026 — 2,646 members2,6467 August 20262 November 2026
24 measurements spanning 87 days, net +14. 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 2,602–2,671 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 24
Measured (UTC)MembersChange
2 Nov 2026, 05:062,646-3
30 Oct 2026, 02:002,649+21
27 Oct 2026, 06:342,628-3
24 Oct 2026, 04:082,631+5
21 Oct 2026, 13:462,626+16
18 Oct 2026, 16:402,610-17
15 Oct 2026, 07:052,627-6
12 Oct 2026, 13:192,633-9
5 Oct 2026, 11:192,642+7
27 Sept 2026, 18:192,635-12
17 Sept 2026, 23:372,647+28
14 Sept 2026, 14:592,619no change
14 Sept 2026, 01:002,619-10
10 Sept 2026, 05:402,629-2
4 Sept 2026, 15:582,631+1
1 Sept 2026, 09:552,630-13
29 Aug 2026, 08:232,643-3
26 Aug 2026, 14:572,646-17
23 Aug 2026, 07:462,663+1
19 Aug 2026, 17:032,662first 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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“ЖК Фестиваль Парк. Open chat” (@FestivalPark), 2,646 members as measured 2 November 2026. Telegram Register, tgregister.com/channel/FestivalPark.

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.