Telegram RegisterThe public register of Telegram
Telegram profile photo for Дубайский борщ | Дубиззл | Авито | Дубай

Supergroup

Дубайский борщ | Дубиззл | Авито | Дубай

@dubaiborsch

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

1,863members

+136 since we began measuring on 7 August 2026

18 online right now

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

Register entry

Telegram ID-1002099159392
TypeSupergroup
Username@dubaiborsch
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 September 2026
Last confirmed live3 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/dubaiborsch

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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,7191,8631,7917 August 2026 — 1,727 members8 August 2026 — 1,725 members11 August 2026 — 1,719 members14 August 2026 — 1,725 members17 August 2026 — 1,729 members20 August 2026 — 1,734 members23 August 2026 — 1,730 members27 August 2026 — 1,735 members30 August 2026 — 1,740 members2 September 2026 — 1,748 members7 September 2026 — 1,754 members11 September 2026 — 1,765 members15 September 2026 — 1,774 members23 September 2026 — 1,774 members28 September 2026 — 1,787 members5 October 2026 — 1,806 members12 October 2026 — 1,808 members18 October 2026 — 1,816 members22 October 2026 — 1,819 members25 October 2026 — 1,836 members28 October 2026 — 1,850 members31 October 2026 — 1,851 members3 November 2026 — 1,863 members7 August 20263 November 2026
23 measurements spanning 88 days, net +136. 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,697–1,885 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
3 Nov 2026, 01:301,863+12
31 Oct 2026, 06:291,851+1
28 Oct 2026, 15:401,850+14
25 Oct 2026, 08:081,836+17
22 Oct 2026, 03:291,819+3
18 Oct 2026, 22:361,816+8
12 Oct 2026, 12:401,808+2
5 Oct 2026, 15:591,806+19
28 Sept 2026, 03:571,787+13
23 Sept 2026, 22:231,774no change
15 Sept 2026, 13:371,774+9
11 Sept 2026, 22:151,765+11
7 Sept 2026, 08:001,754+6
2 Sept 2026, 19:171,748+8
30 Aug 2026, 12:171,740+5
27 Aug 2026, 08:061,735+5
23 Aug 2026, 22:541,730-4
20 Aug 2026, 09:141,734+5
17 Aug 2026, 19:471,729+4
14 Aug 2026, 15:391,725first 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“Дубайский борщ | Дубиззл | Авито | Дубай” (@dubaiborsch), 1,863 members as measured 3 November 2026. Telegram Register, tgregister.com/channel/dubaiborsch.

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.