Channel
Нерухомість Чернівці з Калинчук
@okseniablog
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,240subscribers
+179 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001328610142 |
|---|---|
| Type | Channel |
| Username | @okseniablog |
| Description | Ексклюзивні обʼєкти в оренді та продажу .Вигідні пропозиції для інвесторів .Цікаве про упакування нерухомості . 0954603201 Ксенія |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| On Telegram | t.me/okseniablog |
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 18 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 |
|---|---|---|
| 18 Sept 2026, 01:48 | 2,240 | no change |
| 17 Sept 2026, 22:41 | 2,240 | +26 |
| 13 Sept 2026, 15:42 | 2,214 | +15 |
| 9 Sept 2026, 17:42 | 2,199 | +38 |
| 4 Sept 2026, 04:15 | 2,161 | +10 |
| 31 Aug 2026, 07:24 | 2,151 | +15 |
| 28 Aug 2026, 13:02 | 2,136 | +6 |
| 25 Aug 2026, 18:08 | 2,130 | +16 |
| 22 Aug 2026, 14:48 | 2,114 | +26 |
| 19 Aug 2026, 09:24 | 2,088 | +16 |
| 16 Aug 2026, 02:05 | 2,072 | +11 |
| 14 Aug 2026, 20:45 | 2,061 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@pidrobitok_chernovci · 36,661
Telegram ranks this channel #46 of 60 here — alongside 59 others — read 2 September 2026
@ChernivtsiCityCouncil · 28,060
Telegram ranks this channel #69 of 79 here — alongside 78 others — read 10 September 2026
@chernivtsigram_chernivtsi24 · 22,592
Telegram ranks this channel #71 of 78 here — alongside 77 others — read 20 September 2026
@goodchernivtsi · 110,852
Telegram ranks this channel #76 of 84 here — alongside 83 others — read 14 August 2026
@chernivtsigram · 28,555
Telegram ranks this channel #79 of 82 here — alongside 81 others — read 9 September 2026
@chernivcitruexa · 97,893
Telegram ranks this channel #81 of 83 here — alongside 82 others — read 16 August 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Нерухомість Чернівці з Калинчук” (@okseniablog), 2,240 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/okseniablog.
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.