Telegram RegisterThe public register of Telegram
Telegram profile photo for ProSvaneti Отзывы

Channel

ProSvaneti Отзывы

@prosvaneti_revue

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

5subscribers

+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-1003995759828
TypeChannel
Username@prosvaneti_revue
CreatedBetween 1 April 2026 and 18 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live19 September 2026
Measurements held3
Confirmed unchanged3 times, most recently 19 September 2026
On Telegramt.me/prosvaneti_revue

Growth

454.57 August 2026 — 4 subscribers13 August 2026 — 4 subscribers1 September 2026 — 5 subscribers7 August 20261 September 2026
3 measurements spanning 24 days, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 4–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 03:055+1
13 Aug 2026, 08:474no change
7 Aug 2026, 23:484first reading

Engagement

11 posts held, back to 18 July 2026the 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 11 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
15s
Average length
8s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

12 Aug 2026, 11:42 UTC3 viewsread 13 August 2026

оставил отзыв о трансфере куда_т Групповой трансфер на озера Корульди 12 августа. Поездкой остались довольны. Водитель приехал точно в назначенное время, на остановках по маршруту ожидал, сколько нужно. Вождение аккуратное, безопасное

7 Aug 2026, 17:30 UTC8 viewsread 13 August 2026
Photo

Озера Корульди - это почти рай 2500 тысячи вверх 🥰 и вы можете это увидеть своими глазами, спасибо большое за организацию, доставку и возможность все увидеть своими глазами ребятам, которые организуют туры по Сванети ♥️ спасибо вам за ваш труд и идеальное путешествие ♥️

1 Aug 2026, 14:03 UTC10 viewsread 13 August 2026
Video

Благодарю @xfoilx за поездку на водопады, очень красиво сейчас, и @Svaneti_transfer за содействие, погода оказалась прекрасной

31 Jul 2026, 19:23 UTC9 viewsread 13 August 2026

Спасибо Евгению и Ирине за поход к водопаду утром и закат на Тетнулди вечером! Отличная организация экскурсий! 💯

27 Jul 2026, 09:39 UTC13 viewsread 13 August 2026

Соль забрали, извиняюсь, что так получилось. Спасибо большое за хорошо организованные экскурсии и оперативную связь! 🫶🏼

26 Jul 2026, 15:42 UTC11 viewsread 13 August 2026

Спасибо за поездку на лошадях, очень понравилось 🙏❤️

26 Jul 2026, 07:36 UTC11 viewsread 13 August 2026
Photo

Привет всем! Хочу написать огромную благодарность команде СванетиПро! Ездили на Хишкили, Тетнульди с ними, всегда все четко организовано! Но поездка на Мхеер на рассвет вообще превзошла все ожидания!!! Это что-то невероятное - вид на 360°, восходящее солнце, Ушба, даже Эльбрус видно! Ранний подъем стоит того восторга от этого места! #отзыв

Showing the 11 most recent of 11 posts we hold for @prosvaneti_revue. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 1 September 2026 — this entry's latest reading, not the date you are reading this.

“ProSvaneti Отзывы” (@prosvaneti_revue), 5 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/prosvaneti_revue.

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.