Telegram RegisterThe public register of Telegram
Telegram profile photo for ДНЕПР АРЕНДА ПРОДАЖА ДНЕПР

Supergroup

ДНЕПР АРЕНДА ПРОДАЖА ДНЕПР

@rieltorDnepro

Has discussion group

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

2,565members

+427 since we began measuring on 7 August 2026

140 online right now

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

Register entry

Telegram ID-1001471815201
TypeSupergroup
Username@rieltorDnepro
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 September 2026
Last confirmed live1 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/rieltorDnepro

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 17 September 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

2,1382,5652,351.57 August 2026 — 2,138 members10 August 2026 — 2,146 members14 August 2026 — 2,186 members17 August 2026 — 2,198 members20 August 2026 — 2,224 members24 August 2026 — 2,223 members28 August 2026 — 2,244 members31 August 2026 — 2,235 members3 September 2026 — 2,253 members8 September 2026 — 2,251 members13 September 2026 — 2,284 members17 September 2026 — 2,310 members17 September 2026 — 2,310 members26 September 2026 — 2,358 members4 October 2026 — 2,403 members10 October 2026 — 2,438 members14 October 2026 — 2,464 members17 October 2026 — 2,469 members20 October 2026 — 2,462 members23 October 2026 — 2,490 members26 October 2026 — 2,515 members29 October 2026 — 2,539 members1 November 2026 — 2,565 members7 August 20261 November 2026
23 measurements spanning 86 days, net +427. 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,074–2,629 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
1 Nov 2026, 10:192,565+26
29 Oct 2026, 14:142,539+24
26 Oct 2026, 19:272,515+25
23 Oct 2026, 10:202,490+28
20 Oct 2026, 01:192,462-7
17 Oct 2026, 03:482,469+5
14 Oct 2026, 05:362,464+26
10 Oct 2026, 15:412,438+35
4 Oct 2026, 23:002,403+45
26 Sept 2026, 02:362,358+48
17 Sept 2026, 15:062,310no change
17 Sept 2026, 00:182,310+26
13 Sept 2026, 04:202,284+33
8 Sept 2026, 20:582,251-2
3 Sept 2026, 15:582,253+18
31 Aug 2026, 08:522,235-9
28 Aug 2026, 00:032,244+21
24 Aug 2026, 14:272,223-1
20 Aug 2026, 20:132,224+26
17 Aug 2026, 18:372,198first 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 1 November 2026 — this entry's latest reading, not the date you are reading this.

“ДНЕПР АРЕНДА ПРОДАЖА ДНЕПР” (@rieltorDnepro), 2,565 members as measured 1 November 2026. Telegram Register, tgregister.com/channel/rieltorDnepro.

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.