Channel
@vships_vacancies_UA
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
4,172subscribers
+58 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001967835701 |
|---|---|
| Type | Channel |
| Username | @vships_vacancies_UA |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/vships_vacancies_UA |
Job listings — 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 13 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 11:37 | 4,172 | +16 |
| 14 Sept 2026, 02:59 | 4,156 | +6 |
| 10 Sept 2026, 09:21 | 4,150 | +5 |
| 5 Sept 2026, 09:20 | 4,145 | -1 |
| 1 Sept 2026, 21:14 | 4,146 | +11 |
| 29 Aug 2026, 16:34 | 4,135 | +1 |
| 27 Aug 2026, 01:37 | 4,134 | +5 |
| 24 Aug 2026, 06:39 | 4,129 | +11 |
| 20 Aug 2026, 17:25 | 4,118 | -1 |
| 14 Aug 2026, 21:14 | 4,119 | +3 |
| 11 Aug 2026, 11:04 | 4,116 | -1 |
| 8 Aug 2026, 01:54 | 4,117 | +3 |
| 7 Aug 2026, 13:03 | 4,114 | no change |
| 7 Aug 2026, 12:54 | 4,114 | first reading |
14 posts held, back to 5 June 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 4 pages 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 14 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
87 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 37.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 33 | 37.9% | |
| ❤ | 27 | 31.0% | |
| 🥴 | 9 | 10.3% | |
| 👎 | 8 | 9.20% | |
| 🔥 | 5 | 5.75% | |
| 🤔 | 4 | 4.60% | |
| 🤝 | 1 | 1.15% |
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 14 of the 14 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 87 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 5 June 2026 to 29 July 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.
🌟 V.Ships Vacancy – Messman (Bulk Carrier, 2012) We are currently hiring a Messman to join a Bulk Carrier built in 2012. ⚓️🛳 📩 Apply now: [email protected] OR Pinpoint 🔹 Vessel Type: Bulk Carrier (2012) 🔹 Date of Joining: Mid of Aug ’26 🔹 DWT: 81,500 t 🚢 🔹 Wage: 1,300–1,500 USD/month 💰 🔹 Contract Duration: 6 ± 1 Months 🔹 Crew Onboard: Mixed 👥 🌐 Follow us for more updates: Telegram | LinkedIn | Instagr
👎2
𝗙𝗹𝗲𝗲𝘁 𝗢𝗽𝗽𝗼𝗿𝘁𝘂𝗻𝗶𝘁𝗶𝗲𝘀 𝘄𝗶𝘁𝗵 𝗖𝗼𝘀𝘁𝗮𝗺𝗮𝗿𝗲 | 𝗪𝗲 𝗔𝗿𝗲 𝗛𝗶𝗿𝗶𝗻𝗴 V.Ships Ukraine is looking for experienced Chief Engineer and 3rd Engineer to join Container Vessels operated by Costamare. This is an opportunity to become part of a respected global fleet, work with professional multinational crews, and contribute your expertise onboard some of the world's most active container ships. ✅ Vessel Type: Container Ship ✅ Ranks: Chief…
❤3👍3
🚢 𝗢𝘂𝗿 𝗙𝗹𝗲𝗲𝘁 𝗜𝘀 𝗘𝘅𝗽𝗮𝗻𝗱𝗶𝗻𝗴 — 𝗝𝗼𝗶𝗻 𝗨𝘀! 𝘉𝘪𝘨 𝘰𝘱𝘱𝘰𝘳𝘵𝘶𝘯𝘪𝘵𝘪𝘦𝘴 𝘢𝘳𝘦 𝘰𝘯 𝘵𝘩𝘦 𝘩𝘰𝘳𝘪𝘻𝘰𝘯! We are pleased to announce the upcoming addition of two Self-Unloader Bulk Carriers to our fleet. As we prepare for delivery and commissioning, we are looking for talented seafarers ready to join us on this exciting journey. 𝘠𝘰𝘶𝘳 𝘯𝘦𝘹𝘵 𝘤𝘰𝘯𝘵𝘳𝘢𝘤𝘵 𝘤𝘰𝘶𝘭𝘥 𝘴𝘵𝘢𝘳𝘵 𝘩𝘦𝘳𝘦 💚 📩 Send your application today and become part of our expanding fleet. Apply via…
👍4🥴3❤1
🚢 COSTAMARE FLEET OPPORTUNITIES V.Ships Ukraine is looking for experienced Officers and Engineers to join Costamare-managed container vessels. ⚓️🌊 Why apply with V.Ships Ukraine? ✅ Stable employment with a world-leading Greek shipowner ✅ Transparent contract conditions ✅ Fast recruitment process for urgent joining dates ✅ Professional support from application to embarkation ✅ Long-term career opportunities at sea …
👍5🥴5👎2❤1
‼️We are still hiring!‼️ If you are interested — apply via link! Or send your CV to: [email protected] (please include "Self-Unloader" in the subject line).
❤7
Open positions: 🔹 Chief Engineer | Container Ship (2024) DWT: 38,500 | DOJ: ASAP | Contract: 4+1 months | Mixed crew Wage: 10, 500 USD 👉 Apply: [email protected] OR Pinpoint 🔹 2nd Engineer | Container Ship (2014) DWT: 70,500 | DOJ: ASAP | Contract: 4+1 months | Mixed crew Wage: 8, 300 USD 👉 Apply: [email protected] OR Pinpoint 🔹 3rd Engineer | Bulk Carrier (2009) DWT: 179,200 | DOJ: ASAP | Cont…
❤4🤔2
⚓️ Day of the Seafarer 🌍 Today, we honour the seafarers who keep global trade moving and the world connected. Working in challenging and often unpredictable conditions, they demonstrate resilience, professionalism, and dedication every day. This year’s theme, “Carrying world trade. Carrying the risks,” highlights the realities of life at sea and the challenges faced by maritime professionals worldwide. At V.Ships U…
❤5👍3🔥1
🚢 We are pleased to announce that we are recruiting Senior and Junior Officers for a Self-Unloading Bulk Carrier. • 𝗦𝗲𝗻𝗶𝗼𝗿 𝗢𝗳𝗳𝗶𝗰𝗲𝗿𝘀: Experience on this type of vessel is mandatory. • 𝗝𝘂𝗻𝗶𝗼𝗿 𝗢𝗳𝗳𝗶𝗰𝗲𝗿𝘀: Experience on this type of vessel is preferred, but not mandatory. This is an excellent opportunity for you to expand your knowledge and gain experience on these types of vessels. 📩 𝗛𝗼𝘄 𝘁𝗼 𝗮𝗽𝗽𝗹𝘆: Easy apply via Pinpoi…
🔥4👍2👎1
Open positions: 🔹 𝟮𝗻𝗱 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 | 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗦𝗵𝗶𝗽 (𝟮𝟬𝟭𝟰) DWT: 70,500 | DOJ: ASAP | Contract: 4±1 months | Mixed crew Wage: 8300 USD 👉 Apply: [email protected] OR Pinpoint 🔹 𝗖𝗵𝗶𝗲𝗳 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 | 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗦𝗵𝗶𝗽 (𝟮𝟬𝟮𝟰) DWT: 38,500 | DOJ: ASAP | Contract: 4+1 months | Mixed crew Wage: 10500 USD 👉 Apply: [email protected] OR Pinpoint 🔹 𝟮𝗻𝗱 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 | 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗦𝗵𝗶𝗽 (𝟮𝟬𝟭𝟭) DWT: 52,700 | DOJ: Beginning of Ju…
❤2👍1🤔1🥴1
Open positions: 🔹 𝗘𝗹𝗲𝗰𝘁𝗿𝗼-𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗢𝗳𝗳𝗶𝗰𝗲𝗿 | 𝗣𝗖𝗧𝗖 (𝟮𝟬𝟮𝟱) DWT: 18,000 | DOJ: Mid of July 2026 | Contract: 4±1 months | Mixed crew Wage: negotiable 👉 Apply: [email protected] OR Pinpoint 🔹 𝗘𝗹𝗲𝗰𝘁𝗿𝗼-𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗢𝗳𝗳𝗶𝗰𝗲𝗿 | 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗦𝗵𝗶𝗽 (𝟮𝟬𝟬𝟰) DWT: 81,171 | DOJ: Mid of July 2026 | Contract: 6±1 months | Mixed crew Wage: 6750 USD 👉 Apply: [email protected] OR Pinpoint 🌐 Follow us for more updates: Teleg
👍2❤1
🌟 V.Ships Vacancy – 2nd Engineer (Container Ship, 2011) We are currently hiring a 2nd Engineer to join a Container Ship built in 2011. ⚓️🛳 📩 Apply now: [email protected] OR Pinpoint 🔹 Vessel Type: Container Ship (2011) 🔹 Date of Joining: ASAP 🔹 DWT: 53,000 t 🚢 🔹 Wage: 8,300 USD/month 💰 🔹 Contract Duration: 4 ± 1 Months 🔹 Crew Onboard: Mixed 👥 🌐 Follow us for more updates: Telegram | LinkedIn | Instagram
👍4
🌟 V.Ships Vacancy – Chief Engineer (Container Ship, 2002) We are currently hiring a Chief Engineer to join a Container Ship built in 2002. ⚓️🛳 📩 Apply now: [email protected] OR Pinpoint 🔹 Vessel Type: Container Ship (2002) 🔹 Date of Joining: Mid of June ’26 🔹 DWT: 67,164 t 🚢 🔹 Wage: 10,500 USD/month 💰 🔹 Contract Duration: 4 ± 1 Months 🔹 Crew Onboard: Mixed 👥 🌐 Follow us for more updates: Telegram | Link…
👍4👎2❤1
Showing the 12 most recent of 14 posts we hold for @vships_vacancies_UA. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“V.Ships (Ukraine)” (@vships_vacancies_UA), 4,172 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/vships_vacancies_UA.
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.