Channel
Кропивницький КИТ Group
@obmenka_kropyvnytskyi
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,025subscribers
+22 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 | -1001268185018 |
|---|---|
| Type | Channel |
| Username | @obmenka_kropyvnytskyi |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/obmenka_kropyvnytskyi |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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, 21:21 | 2,025 | -1 |
| 1 Nov 2026, 15:05 | 2,026 | -2 |
| 29 Oct 2026, 20:46 | 2,028 | +7 |
| 26 Oct 2026, 14:10 | 2,021 | +4 |
| 24 Oct 2026, 00:09 | 2,017 | -3 |
| 18 Oct 2026, 13:29 | 2,020 | -6 |
| 15 Oct 2026, 04:06 | 2,026 | -2 |
| 12 Oct 2026, 04:59 | 2,028 | -6 |
| 5 Oct 2026, 19:56 | 2,034 | -4 |
| 27 Sept 2026, 23:38 | 2,038 | +14 |
| 20 Sept 2026, 22:00 | 2,024 | no change |
| 18 Sept 2026, 22:20 | 2,024 | +4 |
| 14 Sept 2026, 16:59 | 2,020 | -1 |
| 11 Sept 2026, 06:35 | 2,021 | +6 |
| 6 Sept 2026, 11:01 | 2,015 | -3 |
| 2 Sept 2026, 09:33 | 2,018 | -5 |
| 30 Aug 2026, 18:58 | 2,023 | +4 |
| 27 Aug 2026, 15:37 | 2,019 | -2 |
| 24 Aug 2026, 20:27 | 2,021 | +8 |
| 20 Aug 2026, 21:53 | 2,013 | 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.
@SvitloKropyvnytskyiMisto · 89,510
Telegram ranks this channel #30 of 70 here — alongside 69 others — read 18 August 2026
@surenakrop · 52,695
Telegram ranks this channel #55 of 60 here — alongside 59 others — read 24 August 2026
@kirovograd_official · 78,094
Telegram ranks this channel #65 of 68 here — alongside 67 others — read 19 August 2026
This channel appears in 3 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.
“Кропивницький КИТ Group” (@obmenka_kropyvnytskyi), 2,025 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/obmenka_kropyvnytskyi.
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.