Channel
@exercitornavis
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
264subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002029197075 |
|---|---|
| Type | Channel |
| Username | @exercitornavis |
| Description | В 2021 г. я получил немецкую шкиперскую лицензию SBF. Сейчас начал тренинги для получения следующей категории - SKS. В этом канале-логбуке я восстанавливаю прежние теоретические знания, делюсь новыми и фиксирую пройденные морские мили. Автор - @asperner |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/exercitornavis |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 09:03 | 264 | no change |
| 7 Aug 2026, 13:05 | 264 | first reading |
7 posts held, back to 13 July 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 pageof 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 23 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
Measured directly from 4 videos 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.
129 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 55.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 71 | 55.0% | |
| 🔥 | 33 | 25.6% | |
| 👍 | 9 | 6.98% | |
| 🥰 | 5 | 3.88% | |
| 👏 | 3 | 2.33% | |
| 😁 | 2 | 1.55% | |
| 😍 | 2 | 1.55% | |
| 🤩 | 2 | 1.55% | |
| 🌚 | 1 | 0.775% | |
| 🤝 | 1 | 0.775% |
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 7 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 129reactions 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 13 July 2025 to 23 June 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.
⛵️⛵️⛵️ Выход в Северное море или Welkoam iip Lun Спустя целый год оказался наконец на борту парусной яхты. Большие – позитивные – изменения в жизни потребовали корректировки курса, но не смены направления (sic!). И вот я снова в море. В этот раз на Северном! План перехода с континентальной части Германии на остров Хельголанд (Helgoland) предполагал: ➡️ Выход из яхтенного порта в деревне Хоокзиль (Hooksiel), распол…
❤12🔥8🤝1🥰1
❗️❗️❗️❗️❗️Яхтенные обучающие комиксы в подарок! 😀Друзья, выкатил очередную нетленку — яхтенные обучающие комиксы 🚤 Всё как мы любим: легко, весело, но при этом про действительно важные вещи, без которых на воде быстро становится не до шуток. Для подписчиков канала «Про Яхты», конечно бесплатно. Первый выпуск можно забрать через бота, который раздаёт подарки. http://t.me/ryc_gift_bot Уже готово пять выпусков, и э…
❤6
Привет с Рейна 👋 Пора потихоньку возвращаться ⛵️
❤18🔥7🥰2
⚓️ Друзья, всем ahoy! Обычно говорят, summer bodies are made in the winter, но то же самое можно сказать и про полезные навыки! Поэтому приглашаю всех присоединиться к каналу «Катрин о французском» — это уютное и эффективное пространство для тех, кто хочет выучить и полюбить французский язык, открыть его живое звучание и поднять свои знания на новый уровень! Почему это важно? 🇫🇷 Франция — страна великих мореплава…
❤6👍2👏1🔥1
Разные поколения кораблей в Гамбурге 🤩
❤11👍3👏1🔥1
⛵️ Пожелаю всем хорошего четверга с классным видео, которое мне удалось снять на прошлых выходных! Ирония в том, что в то утро мне удалось около 2,5 часов порулить в одиночку, но именно тогда рядом проходили самые красивые парусные яхты! К сожалению, довелось снять не всё, потому что не объяснишь стоящей в метре от тебя капитану, что ты ещё и дурак блогер 🙈 В комментариях выложу другой кадр, который отлично иллюстр…
❤12👍2🔥2😁2😍2👏1🥰1
Segeltörn Rügen Наконец удалось выбраться в море и собрать морские мили для следующего этапа - получения Sportküstenschifferschein (новой категории капитанских прав)! На этот раз выходил опять в Балтийское море, но теперь вокруг острова Рюген. Маршрут начался в городе Штральзунд (Stralsund) в пятницу. Выходя из городского порта мы вместе с десятком других шкиперов и одной огромной БАРЖЕЙ ждали открытия автомобильн…
🔥14❤6👍2🤩2🌚1🥰1
Showing the 7 most recent of 7 posts we hold for @exercitornavis. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Капитан, улыбнитесь!” (@exercitornavis), 264 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/exercitornavis.
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.