Telegram RegisterThe public register of Telegram
Telegram profile photo for South_travel Турагентство

Channel

South_travel Турагентство

@south_travel

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

146subscribers

+0 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-1001988667496
TypeChannel
Username@south_travel
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/south_travel

Growth

146147146.57 August 2026 — 146 subscribers8 August 2026 — 146 subscribers30 August 2026 — 147 subscribers16 September 2026 — 146 subscribers7 August 202616 September 2026
4 measurements spanning 40 days. 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 146–147 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 04:58146-1
30 Aug 2026, 10:44147+1
8 Aug 2026, 20:47146no change
7 Aug 2026, 09:29146first reading

Engagement

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

What this channel posts

Video runtime
6s
Average length
6s

Measured directly from 1 video 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.

Reaction mix

17 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 41.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
741.2%
🔥423.5%
custom 5276153777362055748317.6%
🍓15.88%
👍15.88%
🤗15.88%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 4 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 4 most recent posts we hold, published 5 May 2026 to 15 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

15 Jul 2026, 07:19 UTC61 views2 reactionsread 8 August 2026
Photo

#ГОРЯЩИЕТУРЫ #ДОСТУПНЫЙОТПУСК #ВЫГОДНЫЕПУТЕВКИ #ЕГИПЕТ #РАННЕЕБРОНИРОВАНИЕ Как насчет осеннего #ШармЭльШейха ? 🍁☀️ 10 полных дней по #НЕВЕРОЯТНОЙЦЕНЕ 😉😇 Туроператоры активно привлекают на начало "#высокогосезона " и приглашают нас окунуться в воды #красногоморя , со всей его теплотой и красотой 🥭, увидить многочисленных рыбок, на красивейших рифах 🐠🐟🐠 ✈️Вылеты 18 или 25 сентября #Внуково #vko 10 полных дней отдыха

1🔥1

10 Jul 2026, 08:44 UTC74 views5 reactionsread 8 August 2026
Photo

#ГОРЯЩИЕТУРЫ #ВЬЕТНАМ #ОТДЫХПОНИЗКИМЦЕНАМ #ДОСТУПНЫЙОТПУСК #НЕДОРОГИЕПУТЕВКИ ✨️Дорогие мои в последнее время постов , не много , потому что по-прежнему , считаю, что публиковать надо, только НАСТОЯЩИЕ ТУРЫ СО СКИДКАМИ 🤪 📀Все вы знаете, мы на связи практически 24/7☎️ Сегодня расскажу, про жемчужину сезона #Дананг 🦪 Чистый, просторный, размеренный город. Здесь широкие проспекты, современные отели и один из лучших пл

2custom 52761537773620557482🔥1

6 Jun 2026, 14:47 UTC102 views4 reactionsread 8 August 2026
Photo

#ГОРЯЩИЕТУРЫ #ОТПУСКНЕДОРОГО #СНИЖЕНИЕЦЕНЫ #ТУРЦИЯ #Эгейскоеморе 🌊 Отличные цены на отдых в любимой Турции 🫶 Проведи последние дни, первого месяца лета на живописных пляжах с историческими достопримечательностями и развитой инфраструктурой🍸🍻🍱 ✈️Вылет из Москвы 20 июня (#Внуково) 8 ночей отпуска (без потери дней) 2 взрослых🤴👸 Прямой перелет с багажом 🧳🎒 Все включено Групповой трансфер🚍 ✨️Хорошие отели на выбор , с

2👍1🤗1

5 May 2026, 07:44 UTC148 views6 reactionsread 8 August 2026
Photo

#ГОРЯЩИЕТУРЫ #НЕВЕРОЯТНАЯЦЕНА #ДОСТУПНЫЙОТДЫХ #ПУТЕВКИНЕДОРОГО #АЗЕРБАЙДЖАН ⚡️Снова доступны к бронированию короткие туры в #Баку , ПРОШЛОГОДНИЕ ЦЕНЫ 😻 Лидер бронирования лета 2025 года 😜, слетайте кто не был , слетайте повторно , есть что посмотреть или хотя бы привезти 46 кг запрещенки 🤪🤪🤪 ✈️Вылет 12 июня в 12:45 #Домодедово 2 взрослых Прямой перелет @AzerbaijanAirlines багаж 23кг на каждого 3 ночи в отеле (15 ию

2🔥2🍓1custom 52761537773620557481

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“South_travel Турагентство” (@south_travel), 146 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/south_travel.

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.