OMVAC REDES
ServiceDredger or underwater operationsSpain
Identity
- Name
- OMVAC REDES
- MMSI
- 224229670
- IMO number
- Not reported
- Call sign
- Not reported
- Flag state
- Spain (MID 224)
- Station type
- Ship station
Classification & hull
- AIS type code
- 33
- Type
- Dredger or underwater operations
- Category
- Service
- Length overall
- Not reported
- Beam
- Not reported
- Draught
- Not reported
Length is the sum of the two AIS reference-point dimensions fore and aft; beam is the sum of the port and starboard pair. Both come from the vessel's own static report.
Voyage & motion
- Destination
- Not reported
- ETA
- Not reported
- Navigational status
- Not reported
- Speed over ground
- 0.1 kn
- Course over ground
- 178°
- True heading
- 93°
Destination, ETA and navigational status are typed in on the bridge, not measured. Speed, course and heading come from the vessel's instruments.
Last known position
- Latitude
- 35° 53.189' N
- Longitude
- 5° 30.569' W
- Decimal
- 35.88648, -5.50949
- Received
- 2 min ago
- Reported by ship
- Not reported
- Source feed
- AISStream.io
This is the latest position our store holds, not a live fix. The vessel has been free to move for the whole of the age shown above.
Basemap © OpenStreetMap contributors
Only one position is held for this vessel, so no track can be drawn.
Nearby
Other vessels near this one
Everything else our snapshot holds within 25 nm of OMVAC REDES's last known position, straight-line distance and true bearing — not a route either vessel is following.
| Vessel | Type | Distance | Bearing from OMVAC REDES |
|---|---|---|---|
| OMVAC ARES | Dredger or underwater operations | 0.1 nm | 357° N |
| VOLCAN DE TAMASITE | Passenger ship | 0.4 nm | 228° SW |
| SVR VENUS | Cargo ship | 0.4 nm | 43° NE |
| WASA EXPRESS | Passenger ship | 0.5 nm | 219° SW |
| RCC PRESTIGE | Cargo ship | 0.5 nm | 60° ENE |
| EMERALD JINTANG | Cargo ship | 0.5 nm | 43° NE |
| MOSEL ACE | Cargo ship | 0.5 nm | 54° NE |
| NAPOLES | Passenger ship, no additional information | 0.6 nm | 222° SW |
| KATTEGAT | Passenger ship | 0.7 nm | 227° SW |
| SVITZER CHEFCHAOUEN | Tug | 0.8 nm | 241° WSW |
| SVITZER TANGER | Tug | 0.8 nm | 240° WSW |
| SVITZER OUEZZANE | Tug | 0.8 nm | 245° WSW |
| SVITZER AL HOCEIMA | Tug | 0.8 nm | 240° WSW |
| SVITZER OUED RMEL | Pilot vessel | 0.8 nm | 237° WSW |
| SVITZER TETOUAN | Tug | 0.8 nm | 240° WSW |
Ranked by great-circle distance from OMVAC REDES's last known fix, both taken from the same snapshot moment. Neither vessel has necessarily stayed put since — see the age shown above for how stale each position may be. Also available as JSON: /api/nearby.
What this data means
Reading this record
Everything above comes from two different AIS transmissions. Position, speed, course and heading arrive in message 1, 2 or 3, broadcast every few seconds while under way — that is why the position age above can be very small. Name, MMSI, IMO number, call sign, type and dimensions arrive in a separate static report — message 5 for a Class A transponder, message 24 for Class B — sent only around once every six minutes. A vessel can therefore show a fresh position with an old or missing static report, or the reverse.
Nothing here is estimated, interpolated, or carried over from a previous ship at the same MMSI. Where the vessel did not transmit a field, or transmitted a value the standard defines as "not available", we print “Not reported” rather than guess.
How AIS works →Navigational status codes →Ship type codes →Reading an MMSI →
Data for this page comes from AISStream.io under Free for any use. Field meanings are explained in the reference guides. Nothing on this page is derived, estimated or filled in — where a field is empty, we print “Not reported”.