Аренда! 2 хона 2/1/4 Чилонзор 21. Мулжал Идеал. Оила beriladi Пол Обстанофка. Нархи: 350$. Maklerskiy 50%+1 908710290 https://t.me/shoxakaarenda

Channel
Shox Aka Uylari Arenda
@shoxakaarenda
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,325subscribers
+204 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 | -1001754513507 |
|---|---|
| Type | Channel |
| Username | @shoxakaarenda |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/shoxakaarenda |
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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 05:37 | 1,325 | -14 |
| 5 Oct 2026, 01:17 | 1,339 | -11 |
| 26 Sept 2026, 11:38 | 1,350 | -62 |
| 17 Sept 2026, 05:59 | 1,412 | -51 |
| 13 Sept 2026, 07:17 | 1,463 | +7 |
| 9 Sept 2026, 01:36 | 1,456 | +104 |
| 3 Sept 2026, 18:41 | 1,352 | +61 |
| 31 Aug 2026, 19:17 | 1,291 | -15 |
| 29 Aug 2026, 03:25 | 1,306 | +28 |
| 26 Aug 2026, 11:16 | 1,278 | +55 |
| 23 Aug 2026, 11:36 | 1,223 | +6 |
| 19 Aug 2026, 16:45 | 1,217 | +26 |
| 16 Aug 2026, 08:16 | 1,191 | +68 |
| 12 Aug 2026, 22:45 | 1,123 | -6 |
| 10 Aug 2026, 06:02 | 1,129 | +9 |
| 7 Aug 2026, 11:04 | 1,120 | -1 |
| 7 Aug 2026, 05:16 | 1,121 | first reading |
Engagement
3 posts held, back to 6 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Arenda chilonzor 14 kv 2/4/4 Narxi 300$ Oilaga beriladi Maklerskiy 50%+1 🔑🔑🔑🔑🔑 908710290 https://t.me/shoxakaarenda
Arenda chilonzor 23 kv 2/3/5 Narxi 400$ Oilaga beriladi Maklerskiy 50%+1 🔑🔑🔑🔑🔑 908710290 https://t.me/shoxakaarenda
Showing the 3 most recent of 3 posts we hold for @shoxakaarenda. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Shox Aka Uylari Arenda” (@shoxakaarenda), 1,325 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/shoxakaarenda.
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.