Deployment
Seaeye Leopard at Gdansk
Electric work-class ROV with 11-thruster vectored configuration. Depth rating 3000m. Advanced manipulator and tooling capability for subsea construction and survey.
Seaeye Leopard by Saab Seaeye · Unverified
Machine-readable surfaces
- Markdown mirror: /deployments/saab-leopard-lotos-baltic.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/robots/72a4ce02-5eb4-4b1f-ad31-54596d8d0f65
- Data documentation: /data
- Query this programmatically: Deploy MCP
Saab Seaeye Leopard work-class ROV ordered in May 2023 by LOTOS Petrobaltic (part of multi-energy concern ORLEN) to service underwater infrastructure at Poland's B3 and B8 oil fields in the Baltic Sea. The B3 field hosts the Baltic Beta rig; the B8 field holds an estimated 3.5 million tonnes of oil. The Leopard was selected for its versatility and wide equipment options. Survey package includes multi-beam sonar, LIDAR, and pipetracker. Tasks include comprehensive inspection of underwater structures, construction cleaning, cutting, dredging, support for head installations, and diving support. LOTOS Petrobaltic prepared their supply vessel Bazalt II as the dedicated operational platform, adapting it for the LARS system and a custom control cabin.
Key facts
- Operator
- LOTOS Petrobaltic (ORLEN group), Poland
- Oil fields
- B3 (Baltic Beta rig) and B8, Polish sector Baltic Sea
- Host vessel
- Bazalt II supply vessel
- Survey package
- Multi-beam sonar, LIDAR, pipetracker
- ROV depth rating
- 3,000 m
Safety record
No incidents on record for Seaeye Leopard at Gdansk.
Only active incidents are counted. Retracted incidents are excluded from this summary but remain reachable at their canonical URLs.
- Trust tier
- Unverified
- Last updated
- 2026-06-28
- Model
- Seaeye Leopard
- Company
- Saab Seaeye
- Location
- Gdansk
- Status
- announced
- First seen
- 2023-05-01
- ID
72a4ce02-5eb4-4b1f-ad31-54596d8d0f65
Sources (2)
- Saab's Seaeye ROV finds work at Polish oil fields in Baltic Sea · https://www.offshore-energy.biz/saabs-seaeye-rov-finds-work-at-polish-oil-fields-in-baltic-sea/ · 2023-05-01
- LOTOS Choose Seaeye Leopard for Baltic Fields · https://www.saabseaeye.com/news/lotos-choose-seaeye-leopard-for-baltic-fields
Methodology: Unreviewed · 2 sources (no primary) · last reviewed 2026-06-28
Verification posture
Unreviewed
Low confidence
Review state
Stable
Last reviewed 2026-06-28
Maturity + lifecycle
Maturity stage: commercial
Lifecycle: active
Architectural position
Cohort: maritime
Sources by quality tier
- 2
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Seaeye Leopard at Gdansk.Common questions
- What is the Seaeye Leopard deployment at Gdansk?
- Seaeye Leopard, built by Saab Seaeye, is recorded as a deployment at Gdansk on the DEPLOY registry. Saab Seaeye operates the deployment directly.
- Who operates Seaeye Leopard at Gdansk?
- Saab Seaeye, the manufacturer of Seaeye Leopard, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.
- When did the Seaeye Leopard deployment at Gdansk go live?
- The deployment is recorded as starting May 1, 2023 on the DEPLOY registry. Earlier activity may exist but is not yet sourced.
- Is the Seaeye Leopard deployment at Gdansk still active?
- As of the most recent verification on the DEPLOY registry, this deployment is announced but not yet operating.
- Have there been incidents at the Seaeye Leopard deployment at Gdansk?
- No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.
- Is Seaeye Leopard at Gdansk safe?
- Seaeye Leopard at Gdansk has no incidents on record in the DEPLOY registry. This does not constitute a safety guarantee; it reflects the incidents DEPLOY has tracked and verified to date.
Deploy Watch
Track this deployment.
We notify you when status changes against primary-source evidence, contract events surface, or a related incident is filed.