Telegram RegisterThe public register of Telegram
Telegram profile photo for На чемоданах - туры, билеты, горящие путевки, путешествия

Channel

На чемоданах - туры, билеты, горящие путевки, путешествия

@nachemodanah

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

67,702subscribers

+19 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001093136575
TypeChannel
Username@nachemodanah
DescriptionКанал выгодных туров, билетов и предложений для путешествий. Наш бот для поиска билетов - @BilettoBot Канал предложений только для Санкт-Петербурга https://t.me/nachemodanahspb
Created17 April 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/nachemodanah

Topic

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@nachemodanah/47914 · this entry11 Aug 2026, 10:36 UTC@travel_2027/419011 Aug 2026, 10:37 UTC1.002 minutes
@nachemodanah/47963 · this entry13 Aug 2026, 07:47 UTC@travel_2027/420213 Aug 2026, 08:21 UTC1.0035 minutes
@nachemodanah/48083 · this entry18 Aug 2026, 12:07 UTC@travel_2027/422318 Aug 2026, 12:08 UTC1.0072 seconds
@nachemodanah/48145 · this entry20 Aug 2026, 19:04 UTC@travel_2027/424020 Aug 2026, 23:31 UTC1.004.5 hours
@nachemodanah/48288 · this entry26 Aug 2026, 06:25 UTC@travel_2027/426526 Aug 2026, 06:58 UTC1.0033 minutes
@nachemodanah/49863 · this entry28 Oct 2026, 13:33 UTC@travel_2027/449328 Oct 2026, 13:35 UTC1.002 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@travel_202740 (8/8 hand-verifiable sample passed)1.0031 minutesthis entry (40–0)
@nachemodanahspb10 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (10–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 1,333 comparable posts for this entry, running 5 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @nachemodanah — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

67,67967,86967,77467,7026 August 202614 November 2026
64 measurements spanning 101 days, net +19. 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 67,651–67,898 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
14 Nov 2026, 13:1667,702-25
11 Nov 2026, 11:1167,727+2
9 Nov 2026, 14:4667,725-17
8 Nov 2026, 06:0067,742-4
6 Nov 2026, 22:1867,746-5
5 Nov 2026, 21:5767,751-6
4 Nov 2026, 20:3867,757-1
3 Nov 2026, 22:3067,758-3
2 Nov 2026, 22:1767,761-2
1 Nov 2026, 23:4967,763-10
1 Nov 2026, 02:4667,773+3
31 Oct 2026, 00:1867,770-10
30 Oct 2026, 02:3167,780-16
29 Oct 2026, 00:3167,796-27
27 Oct 2026, 22:2967,823+5
27 Oct 2026, 00:3967,818-2
26 Oct 2026, 03:0767,820-3
25 Oct 2026, 02:5667,823-5
24 Oct 2026, 01:2667,828-19
23 Oct 2026, 03:0667,847first reading

Engagement

2,089 posts held, back to 5 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 234 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.58%
avg views ÷ 67,702 subscribers
Avg views / post
1,750
597 posts measured
Reaction rate
0.127%
reactions ÷ views · ER floor
Posts in window
597
of 2,089 held

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. It is computed over the 150 of 597 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held2,089 (5 August 2026 – 16 November 2026)
Views total1,043,009
Reactions total341
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 20:57 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.

What this channel posts

Photos
≈2,460
Videos
≈2
Links
≈26,100

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

576 reactions across 253 posts, in 19 distinct kinds. The most used accounts for 25.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍14925.9%
🔥13824.0%
🍓11620.1%
🐳5810.1%
🎉203.47%
🤯162.78%
🥰122.08%
⚡111.91%
🍾91.56%
🍌81.39%
👎81.39%
🤡81.39%
❤‍🔥61.04%
👏61.04%
😢30.521%
🦄30.521%
💘20.347%
🤗20.347%
😐10.174%

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 265 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 576 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 29 September 2026 to 16 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 1,000 we hold a reading for · 0.1%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nachemodanah. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 29 September 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 82 of 597 posts held from the last 30 days (13.7%) 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).

16 Nov 2026, 14:42 UTC≈1,190 viewsread 16 November 2026

⚡️Туры в Таиланд из Екатеринбурга на 6 ночей от 70.800 руб/чел, виза не нужна ➡️ https://level.tpx.lu/w8QDa4Nn Скидка 2.000 руб на бронирование от 100.000 руб ➡️ https://level.tpx.lu/vVCIWcPv

16 Nov 2026, 14:40 UTC≈1,210 viewsread 16 November 2026

✈️Горят билеты на прямые рейсы из Владивостока в Бангкок за 19.800 руб туда-обратно ➡️ https://aviasales.tpx.lu/AYXmh9d4

16 Nov 2026, 14:17 UTC≈1,360 viewsread 16 November 2026

✈️Прямые рейсы из Екатеринбурга на Пхукет за 64.200 руб туда-обратно в ноябре-декабре, багаж включен ▶️ https://aviasales.tpx.lu/uOKchi4s

16 Nov 2026, 14:15 UTC≈1,380 viewsread 16 November 2026

✈️Из Стамбула в Лос-Анджелес за 42.800 руб туда-обратно в феврале-марте, стыковки в Касабланке ⏩ https://aviasales.tpx.lu/igYIl9uO ⏩ https://aviasales.tpx.lu/lhJKPHmK

16 Nov 2026, 14:04 UTC≈1,370 views2 reactionsread 16 November 2026

✈️Из Москвы в Анталью с возвратом 1 января за 14.300 руб туда-обратно, рейсы прямые ➡️ https://aviasales.tpx.lu/kVQzNM38 Экскурсии в Анталье ➡️ https://tripster.tpx.lu/Ri7yNkTP

👍2

16 Nov 2026, 13:11 UTC≈1,450 viewsread 16 November 2026

🏖Туры на Шри-Ланку из Москвы на 11 ночей с 20 ноября от 75.300 руб/чел, виза не нужна ➡️ https://level.tpx.lu/RR6XKbxs Скидка 2.000 руб на бронирование от 100.000 руб ➡️ https://level.tpx.lu/vVCIWcPv

16 Nov 2026, 12:38 UTC≈1,570 views4 reactionsread 16 November 2026

🎄Турция на Новый год турами из Москвы на 6 ночей с 27 декабря от 44.200 руб/чел, виза не нужна ➡️ https://level.tpx.lu/Zg39hXFL

🔥3🎉1

16 Nov 2026, 12:36 UTC≈1,550 views4 reactionsread 16 November 2026

🌷Туры в Стамбул на неделю из Москвы с 26 ноября от 32.200 руб/чел, виза не нужна ➡️ https://level.tpx.lu/A16RAj20

🍓2👍2

16 Nov 2026, 12:34 UTC≈1,520 views3 reactionsread 16 November 2026

✈️Праздничные выходные в Турции. Прямые рейсы из Москвы в феврале и марте туда-обратно В Измир от 21.900 руб ➡️ https://aviasales.tpx.lu/DxRATqCT ➡️ https://aviasales.tpx.lu/cV4eOZ22 В Анкару от 20.600 руб ➡️ https://aviasales.tpx.lu/IV3BeOl6 ➡️ https://aviasales.tpx.lu/Fa9jktJk

👍2🎉1

16 Nov 2026, 12:15 UTC≈1,450 views3 reactionsread 16 November 2026

✈️Подборка новогодних дат. Рейсы туда-обратно: Москва - Пхукет 67.500 руб, стыковки в Тегеране ▶️ https://aviasales.tpx.lu/metL6kL2 Москва - Бангкок 76.600 руб, стыковки в Тегеране ▶️ https://aviasales.tpx.lu/nKH5ysAR Новосибирск - Пхукет 68.400 руб, стыковка во Владивостоке ▶️ https://aviasales.tpx.lu/f5cbvxnI Новосибирск - Мальдивы 69.200 руб ▶️ https://aviasales.tpx.lu/ONiSEsK8 Сочи - Танзания 86.800 руб, сты…

🦄2🍾1

16 Nov 2026, 12:08 UTC≈1,290 viewsread 16 November 2026

🏖Туры на Шри-Ланку из Тюмени на 11 ночей с 27 ноября от 64.000 руб/чел, виза не нужна ➡️ https://level.tpx.lu/lVS7LvIR Скидка 2.000 руб на бронирование от 100.000 руб ➡️ https://level.tpx.lu/vVCIWcPv

16 Nov 2026, 12:07 UTC≈1,290 views2 reactionsread 16 November 2026

✈️Прямые рейсы туда-обратно на Пхукет с багажом. Даты с ноября по февраль: Из Красноярска 60.600 руб ➡️ https://aviasales.tpx.lu/5y5fGQT1 Из Казани 61.100 руб ➡️ https://aviasales.tpx.lu/t5vvTWW5 Из Екб 75.800 руб ➡️ https://aviasales.tpx.lu/PxLleYEc

🍓2

Showing the 12 most recent of 2,089 posts we hold for @nachemodanah. 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.

Posts edited after publishing

@nachemodanah edited 20 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.

First edit seen
18 August 2026
Most recent edit
14 October 2026

Posts recorded as deleted after publishing

We recorded 33 posts on @nachemodanah as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
16 August 2026
Most recent seen missing
13 November 2026
Median time before seen missing
18 hours
Seen missing in the last 30 days
8

Forward network

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.

Mentions

Named by 5 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.

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

“На чемоданах - туры, билеты, горящие путевки, путешествия” (@nachemodanah), 67,702 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/nachemodanah.

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.