Telegram RegisterThe public register of Telegram
Telegram profile photo for Офис продаж Даг-Тур

Channel

Офис продаж Даг-Тур

@DagTour05

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

492subscribers

-6 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-1001725689504
TypeChannel
Username@DagTour05
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live4 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/DagTour05

Topic

Travel — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

4924984957 August 2026 — 498 subscribers8 August 2026 — 498 subscribers16 August 2026 — 497 subscribers24 August 2026 — 496 subscribers10 September 2026 — 495 subscribers4 October 2026 — 492 subscribers7 August 20264 October 2026
6 measurements spanning 57 days, net -6. 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 491–499 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 01:01492-3
10 Sept 2026, 06:41495-1
24 Aug 2026, 16:16496-1
16 Aug 2026, 14:37497-1
8 Aug 2026, 04:19498no change
7 Aug 2026, 20:46498first reading

Engagement

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

What this channel posts

Video runtime
14s
Average length
14s

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

7 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥457.1%
❤342.9%

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 3 of the 7 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 16 February 2026 to 19 May 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

19 May 2026, 09:28 UTC114 viewsread 8 August 2026

Добрый день☀️Выезды экскурсий: 19.05 🔹ХУНЗАХ 🔹КАХИБ-ГООР 🔹ЧЕЧНЯ:ГРОЗНЫЙ/ШАЛИ/АРГУН ➖➖➖➖➖➖➖➖➖➖ 20.05 🔹ДЕРБЕНТ 🔹КАХИБ-ГООР ➖➖➖➖➖➖➖➖➖➖ 23.05 🔹СУЛАК СТАНДАРТ 🔹ЧЕЧНЯ:ГРОЗНЫЙ/ШАЛИ/АРГУН ➖➖➖➖➖➖➖➖➖➖ 25.05 🔹СУЛАК ПРЕМИУМ ➖➖➖➖➖➖➖➖➖➖ 26.05 🔹КАХИБ-ГООР ➖➖➖➖➖➖➖➖➖➖ 👉 Ближайшая дата: напишите нам @managerdagtor - и мы подберём удобный день и место старта.

1 May 2026, 04:37 UTC184 viewsread 8 August 2026
Photo

Добрый день ☀️‼️ Ближайшие даты - однодневные экскурсии‼️ 〰️〰️〰️〰️ 📍 Дербент+Лунь: ✅03.05 〰️〰️〰️〰️ 📍 Сулакский каньон: ✅02.05✅06.05 премиум 〰️〰️〰️〰️〰️ 📍Грозный: ✅02.05✅04.05 ✅05.05 вечерний✅ 〰️〰️〰️〰️〰️ ГАМСУТЛЬ: ✅15.05 〰️〰️〰️〰️〰️ 📍ГУНИБ: ✅15.05 〰️〰️〰️〰️〰️ 📍Хучни из Дербента: ✅05.05 〰️〰️〰️

29 Apr 2026, 05:57 UTC152 viewsread 8 August 2026
Video

Обстановка в Сулакском каньоне ‼️ В каньоне все прекрасно❤️ 👉 Ближайшая дата: напишите нам @managerdagtor - и мы подберём удобный день и место старта.

5 Apr 2026, 06:24 UTC217 views2 reactionsread 8 August 2026
Photo

🚤 Сулакский каньон с купанием! Представьте: вы несетесь на катере по бирюзовой глади, а над вами взмывают скалы на высоту 1,9 км. Это не просто экскурсия - это приключение, которое помнят всю жизнь. Почему это «Эксклюзив»? ✅ 1,5 часа на катере - полное погружение в каньон. ✅ Купание! Прямо с катера на острове «Лазурный берег» (освежает и заряжает). ✅ Пещеры «Нохъо» и подвесной мост на высоте 60 метров - для тех, кт…

❤2

29 Mar 2026, 09:10 UTC257 views1 reactionsread 8 August 2026
Photo

«А что я получу за 50 000 ₽?» — спросите вы. Вот что ждёт вас в туре «Кавказская сказка» (7 дней, по вторникам). 🏞 Маршрут: Две республики за одну поездку — Чечня и Дагестан. Аргунское ущелье, озеро Кезеной-Ам, Сулакский каньон, аул-призрак Гамсутль, древний Дербент и крепость Нарын-Кала. 🏡 Проживание и питание: 6 ночей в отелях (Грозный — 2 ночи, Махачкала — 1 ночь, Дербент — 3 ночи). Включено: завтраки и обеды…

❤1

16 Feb 2026, 05:17 UTC465 views4 reactionsread 8 August 2026
Photo

Кавказская Сказка: «от Чечни до Дагестана» | 7 ДНЕЙ Заезды на сезон 2026 (по вторникам) МАРШРУТ: Аргунское ущелье — Нихалойские водопады — Шали — озеро Кезеной-Ам — Грозный— Сулакский каньон — катание на катере — Гамсутль — Гуниб — Дербент — крепость Нарын-Кала — Хучни Стоимость тура на 1 человека: При двух-трехместном 50 000 При одноместном 68 000 Детям до 12 лет 45 000

🔥4

Showing the 7 most recent of 7 posts we hold for @DagTour05. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.

“Офис продаж Даг-Тур” (@DagTour05), 492 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/DagTour05.

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.