Channel
🇺🇦НА ЩИТІ🇺🇦 Рівненщина
@cimik_rivne
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,334subscribers
-36 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001840791995 |
|---|---|
| Type | Channel |
| Username | @cimik_rivne |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/cimik_rivne |
Topic
Other / unclassifiable — 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 58% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 06:25 | 2,334 | -7 |
| 1 Nov 2026, 09:26 | 2,341 | -4 |
| 26 Oct 2026, 20:18 | 2,345 | -5 |
| 24 Oct 2026, 04:11 | 2,350 | -4 |
| 21 Oct 2026, 02:09 | 2,354 | -5 |
| 17 Oct 2026, 20:30 | 2,359 | -2 |
| 14 Oct 2026, 23:58 | 2,361 | -6 |
| 11 Oct 2026, 11:20 | 2,367 | +1 |
| 5 Oct 2026, 05:21 | 2,366 | +4 |
| 27 Sept 2026, 01:37 | 2,362 | -3 |
| 18 Sept 2026, 06:18 | 2,365 | -7 |
| 17 Sept 2026, 00:14 | 2,372 | no change |
| 10 Sept 2026, 13:18 | 2,372 | -5 |
| 5 Sept 2026, 19:20 | 2,377 | +2 |
| 1 Sept 2026, 21:05 | 2,375 | -1 |
| 29 Aug 2026, 20:59 | 2,376 | +8 |
| 26 Aug 2026, 10:53 | 2,368 | +1 |
| 23 Aug 2026, 02:36 | 2,367 | -3 |
| 21 Aug 2026, 16:30 | 2,370 | 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.
@tretyakoleksandr · 24,426
Telegram ranks this channel #21 of 78 here — alongside 77 others — read 13 September 2026
@tv0e_rivne · 75,505
Telegram ranks this channel #34 of 80 here — alongside 79 others — read 21 August 2026
@ODA_RV · 23,176
Telegram ranks this channel #36 of 88 here — alongside 87 others — read 20 September 2026
@tipove_sarny · 22,000
Telegram ranks this channel #48 of 79 here — alongside 78 others — read 5 October 2026
@rivne_insider · 23,754
Telegram ranks this channel #60 of 86 here — alongside 85 others — read 15 September 2026
This channel appears in 5 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“🇺🇦НА ЩИТІ🇺🇦 Рівненщина” (@cimik_rivne), 2,334 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/cimik_rivne.
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.