Skip to content

Home
Vessels
AIS Events
- Top STS Facilitators
Terminals
News
Harmonization
About

Baltic (Neva Bay)

Terminals / Area / Baltic Sea /

Baltic (Neva Bay)

1 terminal

St. Petersburg

St. Petersburg

Regional / Secondary Port Baltic (Neva Bay) 18 calls (30d)

Type:

products terminals

Operator:

Port of St. Petersburg Authority

Capacity:

30,000,000 t/year

Status:

Active

View Details →

← Back to all terminals

FleetLeaks monitors sanctioned and suspect vessels globally, aggregating designations from US OFAC, UK OFSI, EU, and other jurisdictions. Updated daily.

Navigation

Intelligence Feed
Vessel Database
Sanctions Timeline
Resources

About

Resources
Methodology
Data Sources
Status
Contact

Legal

Privacy Policy
Terms of Use
Disclaimer

⚖️ Legal Disclaimer

FleetLeaks is an independent monitoring service. All vessel designations, sanctions data, and ownership information are sourced from official government publications and publicly available records. We aggregate and present this information for research and compliance purposes only.

Not legal advice: Information provided on this site does not constitute legal, financial, or compliance advice. Users should verify all data against official sanctions lists and consult qualified legal counsel before making business decisions. For authoritative sources, see our Data Sources section.

Accuracy notice: While we strive for accuracy, vessel information changes frequently. Sanctions designations, ownership structures, and vessel particulars may be updated by authorities without notice. Last data refresh:

© 2025 FleetLeaks. All rights reserved.

Monitoring maritime sanctions since 2024

Analytics? We use anonymized analytics to improve FleetLeaks. Accept or decline; the site still works.

Support FleetLeaks

Amount

$

Currency

Name (optional)

Message (optional)

Email (optional, for thank-you reply)

Make this monthly

Anonymous by default. Your info is only shared if you choose to appear on the supporter wall.

Secure payment via Stripe

❤️

Thank you!

Your support helps keep FleetLeaks running and independent.

⚠️

Something went wrong

Please try again later.