4 Sept 2025, 18:57 UTCviews —
Posted without readable text
Channel
Трансфер KMV-ELBRUS
@Transfer_kmv_elbrus
On this record: Topic · Growth · Engagement · Posts · Cite this entry
20subscribers
+1 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 | -1002970021484 |
|---|---|
| Type | Channel |
| Username | @Transfer_kmv_elbrus |
| Created | 28 August 2025 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/Transfer_kmv_elbrus |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 37% 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 |
|---|---|---|
| 2 Oct 2026, 18:59 | 20 | -1 |
| 17 Sept 2026, 12:58 | 21 | +1 |
| 15 Aug 2026, 20:27 | 20 | +1 |
| 11 Aug 2026, 17:01 | 19 | no change |
| 7 Aug 2026, 17:28 | 19 | first reading |
Engagement
5 posts held, back to 28 August 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 5 posts for this entry, the most recent from 4 September 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
4 Sept 2025, 12:14 UTCviews —
Трансфер KMV-ELBRUS pinned «Повторные заказы - это выгодно! Если вы уже пользовались нашим трансфером, то забронировав обратный путь у нас получаете скидку 500 рублей, также скидку можно получить при рекомендации нас 5 друзьям, и ваши друзья тоже получат скидку на поездки Отправьте скриншот…»
28 Aug 2025, 19:55 UTCviews —
Channel name was changed to «Трансфер KMV-ELBRUS»
28 Aug 2025, 19:32 UTC187 viewsread 11 August 2026
Повторные заказы - это выгодно! Если вы уже пользовались нашим трансфером, то забронировав обратный путь у нас получаете скидку 500 рублей, также скидку можно получить при рекомендации нас 5 друзьям, и ваши друзья тоже получат скидку на поездки Отправьте скриншот рекомендации, проверив, мы подарим вам скидку! Не упустите возможность сэкономить и сделать ваше путешествие безопасным,комфортным и запоминающимся! По вопр…
28 Aug 2025, 19:28 UTCviews —
Channel created
Showing the 5 most recent of 5 posts we hold for @Transfer_kmv_elbrus. 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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“Трансфер KMV-ELBRUS” (@Transfer_kmv_elbrus), 20 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/Transfer_kmv_elbrus.
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.