🇷🇺 -> 🇩🇪🇰🇷 Услуги по перестановке денежных средств Москва -> Германия: 🇪🇺 EUR/EUR - 2.25 % комиссия 🇷🇺 RUB/EUR - 93.72 🇺🇸 USD/EUR - 1.1555 синие / 1.1714 белые Москва -> Корея: 🇷🇺 RUB/KRW - 16.67 🇺🇸 USD/KRW - 1352.17 синие / 1333.83 белые Покупка за USDT 🇦🇶 USDT/EUR - 1.1604 🇦🇶 USDT/KRW - 1345 Прием заявок: @kut_exchange 📍Москва, Центр 🕒Пн - Вс 10:00-22:00 Дата: 26.05.2025

Channel
Обмен КУТ
@kutexchange
On this record: Topic · Growth · Engagement · Posts · Cite this entry
59subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002186597426 |
|---|---|
| Type | Channel |
| Username | @kutexchange |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 10 October 2026 |
| On Telegram | t.me/kutexchange |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 30 Sept 2026, 08:38 | 59 | -1 |
| 29 Aug 2026, 04:07 | 60 | -1 |
| 10 Aug 2026, 04:46 | 61 | no change |
| 7 Aug 2026, 12:54 | 61 | first reading |
Engagement
20 posts held, back to 18 April 2025 — 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 20 posts for this entry, the most recent from 26 May 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
#КурсЦБ 🌐 💸 Обмен КУТ
#КурсЦБ 🌐 💸 Обмен КУТ
#КурсЦБ 🌐 💸 Обмен КУТ
#КурсЦБ 🌐 💸 Обмен КУТ
#КурсЦБ 🌐 💸 Обмен КУТ
#КурсЦБ 🌐 💸 Обмен КУТ
#КурсЦБ 🌐 💸 Обмен КУТ
🇷🇺 -> 🇩🇪🇰🇷 Услуги по перестановке денежных средств Москва -> Германия: 🇪🇺 EUR/EUR - 1.64 % комиссия 🇷🇺 RUB/EUR - 96.38 🇺🇸 USD/EUR - 1.1501 синие / 1.1654 белые Москва -> Корея: 🇷🇺 RUB/KRW - 16.66 🇺🇸 USD/KRW - 1396.38 синие / 1378.05 белые Покупка за USDT 🇦🇶 USDT/EUR - 1.1488 🇦🇶 USDT/KRW - 1397 Прием заявок: @kut_exchange 📍Москва, Центр 🕒Пн - Вс 10:00-22:00 Дата: 01.05.2025
#КурсЦБ 🌐 💸 Обмен КУТ
#КурсЦБ 🌐 💸 Обмен КУТ
#КурсЦБ 🌐 💸 Обмен КУТ
Showing the 12 most recent of 20 posts we hold for @kutexchange. 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 30 September 2026 — this entry's latest reading, not the date you are reading this.
“Обмен КУТ” (@kutexchange), 59 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/kutexchange.
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.