Санкт-Петербург — Шарм-эш-Шейх за 8500₽ в одну сторону. Pegasus Airlines, с пересадкой. Билеты → 09.12 • 8500₽
🔥4❤2🤬1

Channel
@travelradar
On this record: Topic · Previous handles · Observations · Growth · Engagement · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Cite this entry
253,692subscribers
+5,511 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001043585622 |
|---|---|
| Type | Channel |
| Username | @travelradar |
| Created | 10 March 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/travelradar |
Travel — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 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 the other topics.
Recorded in 2019 as “Travelradar — дешевые авиабилеты, туры, путешествия” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @samokatus/489495 Aug 2026, 08:48 UTC | @travelradar/53638 · this entry5 Aug 2026, 08:59 UTC | 1.00 | 10 minutes |
| @samokatus/4900312 Aug 2026, 08:46 UTC | @travelradar/53730 · this entry12 Aug 2026, 09:17 UTC | 1.00 | 31 minutes |
| @samokatus/4914226 Aug 2026, 08:27 UTC | @travelradar/54080 · this entry26 Aug 2026, 08:29 UTC | 1.00 | 2 minutes |
| @samokatus/492373 Sept 2026, 12:47 UTC | @travelradar/54286 · this entry3 Sept 2026, 12:50 UTC | 1.00 | 3 minutes |
| @samokatus/4985026 Oct 2026, 15:31 UTC | @travelradar/55337 · this entry28 Oct 2026, 08:59 UTC | 1.00 | 41 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @samokatus | 5 (5/5 hand-verifiable sample passed) | 1.00 | 10 minutes | @samokatus (5–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 4 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 1,513 comparable posts for this entry, running 4 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the key clone_copy, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 20:50 | 253,692 | +57 |
| 14 Nov 2026, 15:18 | 253,635 | +49 |
| 11 Nov 2026, 15:45 | 253,586 | +102 |
| 9 Nov 2026, 20:59 | 253,484 | +78 |
| 8 Nov 2026, 13:07 | 253,406 | +18 |
| 7 Nov 2026, 05:59 | 253,388 | -2 |
| 6 Nov 2026, 02:39 | 253,390 | +40 |
| 5 Nov 2026, 03:19 | 253,350 | +65 |
| 3 Nov 2026, 23:56 | 253,285 | +348 |
| 3 Nov 2026, 03:15 | 252,937 | +12 |
| 2 Nov 2026, 04:10 | 252,925 | -15 |
| 1 Nov 2026, 01:07 | 252,940 | +15 |
| 30 Oct 2026, 22:56 | 252,925 | -12 |
| 30 Oct 2026, 01:48 | 252,937 | -32 |
| 29 Oct 2026, 00:49 | 252,969 | -1 |
| 27 Oct 2026, 19:07 | 252,970 | -73 |
| 26 Oct 2026, 18:10 | 253,043 | -23 |
| 25 Oct 2026, 18:17 | 253,066 | +7 |
| 24 Oct 2026, 17:57 | 253,059 | +5 |
| 23 Oct 2026, 19:55 | 253,054 | first reading |
2,002 posts held, back to 4 August 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 209 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 2,002 (4 August 2026 – 17 November 2026) |
| Views total | 4,613,620 |
| Reactions total | 10,265 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 14:25 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
19,432 reactions across 996 posts, in 35 distinct kinds. The most used accounts for 35.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6,919 | 35.6% | |
| 😁 | 3,526 | 18.1% | |
| 🔥 | 2,497 | 12.8% | |
| 👍 | 1,144 | 5.89% | |
| 🤣 | 977 | 5.03% | |
| 🤬 | 944 | 4.86% | |
| 👏 | 793 | 4.08% | |
| 🥰 | 458 | 2.36% | |
| 💩 | 314 | 1.62% | |
| 😢 | 301 | 1.55% | |
| 🤡 | 273 | 1.40% | |
| 😱 | 266 | 1.37% | |
| 😍 | 156 | 0.803% | |
| 💯 | 111 | 0.571% | |
| 🤯 | 111 | 0.571% | |
| 😡 | 103 | 0.53% | |
| 👎 | 83 | 0.427% | |
| ❤🔥 | 78 | 0.401% | |
| 🦄 | 54 | 0.278% | |
| 🍾 | 43 | 0.221% | |
| 15 further kinds | 281 | 1.45% |
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 998 of the 1,000 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 19,432 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 21 September 2026 to 17 November 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqxB7mbJ | 167 | 24 September 2026 | 17 November 2026 |
| 2VtzqxXsbY8 | 64 | 21 September 2026 | 17 November 2026 |
| 2Vtzqv9nKfS | 21 | 23 September 2026 | 16 November 2026 |
| 2VtzqxCbkse | 2 | 13 November 2026 | 17 November 2026 |
| 2Vtzquo1sa6 | 1 | 11 November 2026 | 11 November 2026 |
| 2Vtzqv9fyx2 | 1 | 10 November 2026 | 10 November 2026 |
| 2VtzqwfX8Eg | 1 | 26 September 2026 | 26 September 2026 |
| 2VtzqwhAX9w | 1 | 23 October 2026 | 23 October 2026 |
| 2VtzqxTRdh6 | 1 | 17 November 2026 | 17 November 2026 |
| 2Vtzqxjbpgd | 1 | 16 October 2026 | 16 October 2026 |
| 2VtzqxmDV5E | 1 | 16 November 2026 | 16 November 2026 |
| 2W5zFJej68y | 1 | 5 October 2026 | 5 October 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 21 September 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 66 of 503 posts held from the last 30 days (13.1%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Москва — Маэ (Сейшелы) за 20500₽ в одну сторону. Аэрофлот, прямой рейс, вылет ночью. Инфа для тех, кто уже там и при этом по какой-то необъяснимой причине (a) читает эти строки на Сейшелах и (b) находится там без обратного билета. В Москву завтра за 15400, прямо на том же воздушном судне (хорошо бы сейшельские уборщики успели чипсы на полу под сиденьем убрать). Билеты здесь ↓ ✓ Маэ 18.11 • 20500₽ ✓ в Москву 18.11 …
😁9❤7
🇻🇳 Нячанг, Crown Nguyen Hoang Hotel 4★ из Москвы Стоимость за двоих: ~132.000₽ Вылет: 06.12.2026 В цену включено: • проживание — 9 ночей • питание — завтраки • перелёт: Аэрофлот, прямой, багаж • медицинская страховка • трансфер аэропорт ↔ отель Отзывы: LT: 9/10 (11). Смотреть → https://level.tpo.lv/iU8WSv0p?erid=2VtzqxXsbY8 Другие туры: Нячанг, 06.12, 9 ночей с перелётом — от дешёвых к дорогим
❤5
Санкт-Петербург — Шарм-эш-Шейх за 8500₽ в одну сторону. Pegasus Airlines, с пересадкой. Билеты → 09.12 • 8500₽
🔥4❤2🤬1
Москва — Казань за 3200₽ туда-обратно. Победа, прямой рейс. Билеты → 18.11-20.11 • 3200₽
👍4🤬2
Ташкент — Москва за 3600₽ в одну сторону. Победа, прямой рейс. Билеты → 21.11 • 3600₽
❤3🤬1
Шарм-эш-Шейх — Казань за 6600₽ в одну сторону. Прямой рейс. Билеты → 19.11 • 6600₽
❤4🤬1
Завтра в 10 утра у «Победы» снова распродажа. Предыдущая была, кажется, буквально на днях. При такой периодичности впору анонсировать не распродажи, а короткие промежутки между ними, когда билеты продаются по обычным ценам. Ну или сознаться, что распродажи так себе. Вообще, есть подозрение, что маркетологи «Победы» в ноябре открыли годовой план и обнаружили, что по количеству распродаж ещё есть куда расти. Особенно …
😁35❤4💯4👍1🤬1
Новосибирск — Коломбо (Шри-Ланка) за 32100₽ туда-обратно. Прямые рейсы. Билеты → 15.04-02.05 • 32100₽
❤9🔥2😢2🤬1
Москва — Нячанг за 18600₽ в одну сторону. Nordwind Airlines, прямой рейс. Билеты → 18.11 • 18600₽ Upd: Чисто сработано.
🔥20❤7😁7🤬1
Новые однодневные промокоды Я.Путешествий на отели с этой → страницы. • 20% для первых 100 пользователей • 10% для опоздавших Максимальная скидка 100к рублей, что само по себе недурственно. Только 17.11.2026 до 23:59 Еще разок: https://yandex.tpo.lv/D4czog2p?erid=2VtzqxCbkse
❤5👍2🔥2🤬1
Омск — Пхукет за 43000₽ туда-обратно. AZUR Air, прямой рейс. Билеты → 19.11-30.11 • 43000₽
🔥7❤2👍1🤬1
🇹🇷 Турция, Лара, Club Hotel Sera 5★ из Москвы Стоимость за двоих: ~113.000₽ Вылет: 11.12.2026 В цену включено: • проживание — 7 ночей • питание — Ultra All Inclusive • перелёт: Победа, прямой • медицинская страховка Отзывы: 9.1/10. Смотреть → https://onlinetours.tpo.lv/yf1U0wd5?erid=2VtzqxTRdh6
❤9🔥5👍1👏1🤬1🥰1
Showing the 12 most recent of 2,002 posts we hold for @travelradar. 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.
@travelradar edited 34 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 9 registered channels — 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.
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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“TravelRadar — дешевые авиабилеты, туры, путешествия” (@travelradar), 253,692 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/travelradar.
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.