Telegram RegisterThe public register of Telegram
Telegram profile photo for DiamondTravel

Channel

DiamondTravel

@Diamond_Travels

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

8subscribers

+0 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002364579120
TypeChannel
Username@Diamond_Travels
Descriptionhttps://t.me/Discount_Almaz - основной канал Переходник на все наши проекты - https://t.me/Perehodnik_Diamond
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live3 October 2026
Measurements held2
On Telegramt.me/Diamond_Travels

Growth

811 Aug 2026, 11:16 — 8 subscribers12 Aug 2026, 14:18 — 8 subscribers11 Aug 2026, 11:1612 Aug 2026, 14:18
2 measurements spanning 1 day. 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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 14:188no change
11 Aug 2026, 11:168first reading

Engagement

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

What this channel posts

Photos
28
Links
12

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

19 May 2025, 10:14 UTC422 viewsread 12 August 2026
Photo

✈️ Ozon Travel Скидки на отели до 60%🩵 Промокод➡️ MANIA

18 May 2025, 16:08 UTC523 viewsread 12 August 2026
Photo

🌎 Яндекс маркет Поймали скидки на отели и квартиры до 40%! 🔥 Для тех, кто планирует отпуск заранее и не хочет переплачивать. Собрали в одном месте варианты со скидками за раннее бронирование на лето и добавили промокод ZARANEE20, с которым максимальная скидка может доходить до 40%. Двойная выгода и никакой головной боли в последний момент — кажется, мы нашли идеальную формулу отпуска!

18 May 2025, 09:13 UTC420 viewsread 12 August 2026
Photo

🌎 Яндекс путешествия Если туризм, то почему бы не винный? 🍇 Показываем винодельни из топа-10 по версии путеводителя 50 Best Tastes of Russia. Ну а чтобы попасть на экскурсию и дегустацию, срочно хватайте ж/д билеты до Краснодара и Ростова!

16 May 2025, 06:37 UTC318 viewsread 12 August 2026
Photo

🌎 Яндекс путешествия История вкусов: гастротур по Стамбулу 🖤 Кадыкёй — модный район Стамбула с отличными ресторанами. Так что — всё совпало. Подобрали места, где можно поесть разнообразно и вкусно. Промокод 🍃LOOKUM Скидка 20% не более 2000₽ действует при бронировании в разделе "Отели" Срок действия промокода до 31.07 Подборка отелей 🌍

15 May 2025, 07:26 UTC389 viewsread 12 August 2026
Photo

🌎 Яндекс путешествия Прислушиваетесь к отзывам путешественников? Тогда вам сюда — REKOMENDUEM отели с высоким рейтингом! 💜 Выбирайте из множества вариантов — они собрали сотни отличных отзывов, а ещё их можно забронировать со скидкой до 20% по промокоду 🔵REKOMENDUEM Тык на ссылку 🌏

13 May 2025, 05:03 UTC26 viewsread 12 August 2026
Photo

Ну или за 243₽ Сочи на две ночи✨

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

“DiamondTravel” (@Diamond_Travels), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Diamond_Travels.

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.