Telegram RegisterThe public register of Telegram
Telegram profile photo for Job Offers For Seafarers | Вакансии для Моряков

Channel

Job Offers For Seafarers | Вакансии для Моряков

@jobfor_seamen

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

8,953subscribers

+32 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001884696688
TypeChannel
Username@jobfor_seamen
DescriptionJob for Seafarers Offshore Fleet | Merchant Fleet Cooperation ➡️ @Owner_Oleg
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 August 2026
On Telegramt.me/jobfor_seamen

Topic

Job listings — 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 11 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 why it has no browse page of its own yet.

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 word for word 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.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@jobs_seafarers/28526 Aug 2026, 07:57 UTC@jobfor_seamen/11998 · this entry6 Aug 2026, 08:19 UTC1.0022 minutes
@jobs_seafarers/28536 Aug 2026, 07:57 UTC@jobfor_seamen/11999 · this entry6 Aug 2026, 08:19 UTC1.0022 minutes
@jobs_seafarers/28546 Aug 2026, 08:01 UTC@jobfor_seamen/12000 · this entry6 Aug 2026, 08:19 UTC1.0018 minutes
@jobs_seafarers/28556 Aug 2026, 08:02 UTC@jobfor_seamen/12001 · this entry6 Aug 2026, 08:19 UTC1.0017 minutes
@jobs_seafarers/28567 Aug 2026, 06:37 UTC@jobfor_seamen/12013 · this entry7 Aug 2026, 09:45 UTC1.003.1 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@jobs_seafarers5 (5/5 hand-verifiable sample passed)1.0022 minutes@jobs_seafarers (50)

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. 5 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 19 comparable posts for this entry, running 5 August 2026 to 7 August 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).

Across the whole group of 2, the earliest publisher we hold is @jobs_seafarers. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

8,9218,9538,9377 August 2026 — 8,921 subscribers7 August 2026 — 8,921 subscribers7 August 2026 — 8,928 subscribers10 August 2026 — 8,929 subscribers12 August 2026 — 8,942 subscribers16 August 2026 — 8,948 subscribers19 August 2026 — 8,953 subscribers7 August 202619 August 2026
7 measurements spanning 12 days, net +32. 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 8,916–8,958 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 03:348,953+5
16 Aug 2026, 07:138,948+6
12 Aug 2026, 19:548,942+13
10 Aug 2026, 06:048,929+1
7 Aug 2026, 15:508,928+7
7 Aug 2026, 11:308,921no change
7 Aug 2026, 11:298,921first reading

Engagement

90 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
4.70%
avg views ÷ 8,953 subscribers
Avg views / post
421
90 posts measured
Reaction rate
0.19%
reactions ÷ views · ER floor
Posts in window
90
of 90 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 20 of 90 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 19 August 2026
Posts held90 (5 August 202619 August 2026)
Views total37,848
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 05:22 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
999
Videos
69
Links
10,800

Lifetime counters from Telegram’s own channel header, read 20 August 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

19 reactions across 16 posts, in 2 distinct kinds. The most used accounts for 94.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1894.7%
😱15.26%

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 20 of the 90 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 19reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 90 most recent posts we hold, published 5 August 2026 to 19 August 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.

Recent posts

19 Aug 2026, 14:29 UTC290 viewsread 20 August 2026

🚢 𝗔𝗟𝗣𝗛𝗔 𝗖𝗥𝗘𝗪 𝗚𝗥𝗢𝗨𝗣 𝗜𝗦 𝗨𝗥𝗚𝗘𝗡𝗧𝗟𝗬 𝗟𝗢𝗢𝗞𝗜𝗡𝗚 𝗙𝗢𝗥: ✅TOP URGENT - 3E - BULK CARRIER ( Transhipper vessel) - 4000 USD/m Position: 3E Vessel: BULK CARRIER ( Transhipper vessel) Salary: 4000 USD/m Joining: ASAP Duration: 5+-1 months Requirements: - Good rank experience on similar vessel type - Good English - COVID Vaccination ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ 👉To apply for this position follow this link: https://my.alphacrew.com/job/14037

19 Aug 2026, 13:53 UTC269 viewsread 20 August 2026

🚢 𝗔𝗟𝗣𝗛𝗔 𝗖𝗥𝗘𝗪 𝗚𝗥𝗢𝗨𝗣 𝗜𝗦 𝗨𝗥𝗚𝗘𝗡𝗧𝗟𝗬 𝗟𝗢𝗢𝗞𝗜𝗡𝗚 𝗙𝗢𝗥: ✅ TOP URGENT - 2O - AHTS DP1 - 130 - 150 USD p/d Position: 2O Vessel: AHTS DP1 Salary: 130 - 150 USD p/d Joining: ASAP Duration: 2 months on/off Requirements: - Experience on AHTS / ASD - Static towing & towing over the bow - CO Ticket preferred ➖➖➖➖➖➖➖➖➖➖➖➖➖ 👉To apply for this position, follow this link: https://my.alphacrew.com/job/14104 ✉️ Send your CV to cv@alphacrew

19 Aug 2026, 13:30 UTC277 viewsread 20 August 2026

🔥URGENTLY🔥 3rd Engineer on General Cargo Ship 🔥Ukrainian ONLY 💸Salary: 3500 USD 🗓 Join: ASAP, Moldova 📑Details: 🔸 Vessel: DWT 3700 / 2007 y.b. 🔸 Duration: 4+/-1 months 🔸 Area: Mediterranean Sea, Black Sea (no Ukr or Rus. ports) 🔸 Crew: Montenegro, Ukraine, Egypt Requirements: 🔹 ASAP embarkation 🔹 Good English 🔹Ukrainian candidate ONLY 🔹 Experience in the Rank 12 months 📩 Send your CV to info@uviscompany.

19 Aug 2026, 08:52 UTC324 viewsread 20 August 2026

🚢 START Chief Engineer - 9800-11000$ 2nd Engineer - 8000$ Type: Container Contract : 4 Embarkation: September 📧 [email protected] 📞 Contact number: +380936995198 Oleksandra

19 Aug 2026, 07:35 UTC314 viewsread 20 August 2026

Urgently searching for Cook for Barge. Start asap, duration 3 weeks, salary 170-180 euro pd. Location: Europe. Previous experience on similar vessels. Good English level. Please contact with us in any additional information. +38 (048) 737 33 81 +38 (098) 025 34 78 All applications forwarded as soon as possible to: [email protected]

19 Aug 2026, 07:32 UTC305 viewsread 20 August 2026

🚢 𝗔𝗟𝗣𝗛𝗔 𝗖𝗥𝗘𝗪 𝗚𝗥𝗢𝗨𝗣 𝗜𝗦 𝗨𝗥𝗚𝗘𝗡𝗧𝗟𝗬 𝗟𝗢𝗢𝗞𝗜𝗡𝗚 𝗙𝗢𝗥: ✅ TOP URGENT - MASTER - PATROL VESSEL - 9000 GBP Position: MASTER Vessel: PATROL VESSEL Salary: 9000 GBP Joining: ASAP Duration: 4 months Requirements: - Good rank experience on similar vessels, workboats; - Unlimited Master license. ➖➖➖➖➖➖➖➖➖➖➖➖➖ 👉To apply for this position follow this link: https://my.alphacrew.com/job/14057 ✉️ Send your CV to [email protected] 📞 +38097

19 Aug 2026, 07:04 UTC272 viewsread 20 August 2026

JOB OFFER Vessel type: RO-RO Position: CH OFF Salary: 7000 USD Duration: 2 months + 4 [email protected] +380 99 255 20 05 (Only messages) Viber, Telegram, Whatsup

19 Aug 2026, 07:04 UTC247 viewsread 20 August 2026

JOB OFFER Vessel type: RO-RO Position: AB Salary: 1875 USD + lashing bonus Duration: 2 months + 4 [email protected] +380 99 255 20 05 (Only messages) Viber, Telegram, Whatsup

19 Aug 2026, 07:04 UTC246 viewsread 20 August 2026

JOB OFFER Vessel type: RO-RO Position: OS Salary: 1300 USD + lashing bonus Duration: 2 months + 4 [email protected] +380 99 255 20 05 (Only messages) Viber, Telegram, Whatsup

19 Aug 2026, 06:55 UTC244 views1 reactionsread 20 August 2026

“YCrewing”, maritime agency, rendering services for seafarers employment 🔎📝 🚢 Chemical/Oil Products Tanker 🔸Master -9200$ 🔸Chief Officer -6800$ 🔸2nd Officer -3000$ 🔸3rd Officer -2000$ 🔸Сhief Engineer -9500$ 🔸2nd Engineer -6800$ 🔸3rd Engineer -3500$ 🔥Boarding: ASAP❗️ ❗️POSSIBLE START❗️ ⬇️SEND YOUR CV:⬇️ 📩 [email protected] ☎️Telegram, WhatsApp +380 95 895 5317 +995 55 766 6459

1

19 Aug 2026, 06:55 UTC212 viewsread 20 August 2026

“YCrewing”, maritime agency, rendering services for seafarers employment 🔎📝 🚢 Bulk Carrier 🔸Chief Engineer -10000$ 🔸Chief officer -7700$ 🔸2nd Engineer -7700$ 🔸3rd Engineer -4000$ 🔥Boarding: ASAP❗️ ❗️POSSIBLE START❗️ ⬇️SEND YOUR CV:⬇️ 📩 [email protected] ☎️Telegram, WhatsApp +375 33 625-00-10 +995 579 06 73 16

19 Aug 2026, 06:38 UTC219 viewsread 20 August 2026
Photo

📋VACANCY: SECOND ENGINEER 💰 Salary: 6800-8000 USD ⠀ 🚢 Vessel: Bulk Carrier 📅 Built: 2004 ⚓ DWT: 34000 🔧 Engine: MAN BW 6S46MC-C 6300KW ⠀ CONDITIONS: 📆 Contract: 5+/-1 🕓 Joining: 8-9th August ⠀ REQUIREMENTS: ✅ English: Good working level ✅ Documents: Valid for at least 1 year ⠀ 📩 CONTACTS: Telegram: @anastasiaChRayMarine Email: [email protected] Vacancies: https://t.me/Ukrainianseafarers ⠀ Отправить Вашу анкет

Showing the 12 most recent of 90 posts we hold for @jobfor_seamen. 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.

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

“Job Offers For Seafarers | Вакансии для Моряков” (@jobfor_seamen), 8,953 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/jobfor_seamen.

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.