vukodlak.bsky.social
@vukodlak.bsky.social
The sawfish was present already at 2011 when she was called FINEX. So you can rule out the emblem being deliberately painted on just to give us a giant middle finger, but the existing emblem could have been a factor in RISS picking this ship to conduct sabotage.
January 3, 2026 at 1:15 PM
The sawfish was present already at 2011 when she was called FINEX. So you can rule out the emblem being deliberately painted on just to give us a giant middle finger, but the existing emblem could have been a factor in RISS picking this ship to conduct sabotage.
I don't think it can be anything else.
December 31, 2025 at 11:44 AM
I don't think it can be anything else.
Also a criminal investigation has been opened, with same criminal charges as with EAGLE S previously: grievous sabotage, grievous attempt of sabotage and grievous disturbance of telecommunication.
December 31, 2025 at 11:42 AM
Also a criminal investigation has been opened, with same criminal charges as with EAGLE S previously: grievous sabotage, grievous attempt of sabotage and grievous disturbance of telecommunication.
Rough summary of the Finnish Police announcement:
- Suspected cable break in Estonian EEZ
- Vessel was intercepted in Finnish EEZ by Finnish Border Guard patrol ship and helo. The suspected vessel was ordered to raise it's anchor and move to an anchorage in the Finnish terr. waters.
- Suspected cable break in Estonian EEZ
- Vessel was intercepted in Finnish EEZ by Finnish Border Guard patrol ship and helo. The suspected vessel was ordered to raise it's anchor and move to an anchorage in the Finnish terr. waters.
December 31, 2025 at 11:40 AM
Rough summary of the Finnish Police announcement:
- Suspected cable break in Estonian EEZ
- Vessel was intercepted in Finnish EEZ by Finnish Border Guard patrol ship and helo. The suspected vessel was ordered to raise it's anchor and move to an anchorage in the Finnish terr. waters.
- Suspected cable break in Estonian EEZ
- Vessel was intercepted in Finnish EEZ by Finnish Border Guard patrol ship and helo. The suspected vessel was ordered to raise it's anchor and move to an anchorage in the Finnish terr. waters.
According to the just published information by the Finnish Police, the incident occured early in Wednesday morning. The vessel was instructed to raise it's anchor and move to an anchorage in Finnish territorial waters. So it's most likely Fitburg (IMO 9250397).
December 31, 2025 at 11:19 AM
According to the just published information by the Finnish Police, the incident occured early in Wednesday morning. The vessel was instructed to raise it's anchor and move to an anchorage in Finnish territorial waters. So it's most likely Fitburg (IMO 9250397).
www.hs.fi/suomi/art-20...
According to most recent reporting, Finnish authorities have seized a vessel (not named) suspected of damaging a cable with an anchor. According to the reporting, Finnish Border Guard observed the vessel with it's anchor in the water.
According to most recent reporting, Finnish authorities have seized a vessel (not named) suspected of damaging a cable with an anchor. According to the reporting, Finnish Border Guard observed the vessel with it's anchor in the water.
Merikaapelit | Aluksen epäillään vaurioittaneen Elisan merikaapelia Suomenlahdella
Poliisin tiedotteen mukaan Rajavartiolaitos paikansi aluksen, jonka epäillään aiheuttaneen kaapelin vaurioitumisen. Alus on otettu haltuun.
www.hs.fi
December 31, 2025 at 11:12 AM
www.hs.fi/suomi/art-20...
According to most recent reporting, Finnish authorities have seized a vessel (not named) suspected of damaging a cable with an anchor. According to the reporting, Finnish Border Guard observed the vessel with it's anchor in the water.
According to most recent reporting, Finnish authorities have seized a vessel (not named) suspected of damaging a cable with an anchor. According to the reporting, Finnish Border Guard observed the vessel with it's anchor in the water.
Timing of the incident is elaborated to be "Wednesday morning".
December 31, 2025 at 10:44 AM
Timing of the incident is elaborated to be "Wednesday morning".
The more likely mechanism is propably the software that converts the RF AIS transmissions receives by the SDR and converts them to whatever format in which it is fed into the databases - intentional or unintentional manipulation in the software without actual RF component bwing broadcasted?
November 3, 2025 at 11:40 AM
The more likely mechanism is propably the software that converts the RF AIS transmissions receives by the SDR and converts them to whatever format in which it is fed into the databases - intentional or unintentional manipulation in the software without actual RF component bwing broadcasted?
I would find RF unlikely - mainly because it would require a transmitter close by and also because the AIS standard propably can’t support one reveiver provessing 17 000+ ships’ ais transmission during the same time
November 3, 2025 at 11:38 AM
I would find RF unlikely - mainly because it would require a transmitter close by and also because the AIS standard propably can’t support one reveiver provessing 17 000+ ships’ ais transmission during the same time
As of now (06:33 UTC) vesselfinder seems to have cleaned up the false tracks, whereas marinetraffic still has quite a lot of them.
November 3, 2025 at 6:35 AM
As of now (06:33 UTC) vesselfinder seems to have cleaned up the false tracks, whereas marinetraffic still has quite a lot of them.
At least vesselfinder runs a "become an AIS partner" program which seems to imply that they do gather data from amateur AIS stations including this one which seems to have caused these false tracks. That's my best guess at this point.
November 2, 2025 at 11:03 PM
At least vesselfinder runs a "become an AIS partner" program which seems to imply that they do gather data from amateur AIS stations including this one which seems to have caused these false tracks. That's my best guess at this point.
Although Vesselfinder also recognizes the same AIS station under name AIS station 5191, which exhibits the exact same symptoms. Mayhaps commercial AIS sites are incorporating these unofficial AIS receivers, and this one was either hacked or the owner of the station did a stupid thing for the lolz?
November 2, 2025 at 10:49 PM
Although Vesselfinder also recognizes the same AIS station under name AIS station 5191, which exhibits the exact same symptoms. Mayhaps commercial AIS sites are incorporating these unofficial AIS receivers, and this one was either hacked or the owner of the station did a stupid thing for the lolz?
So a working hypothesis might be that false AIS tracks were burst transmitted where this station could hear it - same transmissions being picked up by some "official" AIS base station and pushed into marinetraffic, vesselfinder etc.?
November 2, 2025 at 10:40 PM
So a working hypothesis might be that false AIS tracks were burst transmitted where this station could hear it - same transmissions being picked up by some "official" AIS base station and pushed into marinetraffic, vesselfinder etc.?
This is a station located in Pargas, Finland. If I understand correctly these are not "official" AIS base stations but rather AIS receivers maintained by amateurs and running open-source software. There's another station "MUSTFINN" in the same city with no anomalies 🤨
November 2, 2025 at 10:37 PM
This is a station located in Pargas, Finland. If I understand correctly these are not "official" AIS base stations but rather AIS receivers maintained by amateurs and running open-source software. There's another station "MUSTFINN" in the same city with no anomalies 🤨
The false tracks in Lake Ladoga all seem to be vessels which at some point in time could have plausibly been in Lake Ladoga (tugs, passenger ships, cargo ships designed for inland waterways). This leads me to think that the false tracks are snapshots of different time periods in history
November 2, 2025 at 10:00 PM
The false tracks in Lake Ladoga all seem to be vessels which at some point in time could have plausibly been in Lake Ladoga (tugs, passenger ships, cargo ships designed for inland waterways). This leads me to think that the false tracks are snapshots of different time periods in history
Also noteworthy: all fake tracks are in logical spots, with courses and speeds correlating with shipping lanes, i.e. not completely randomized. Also they all seem to be west/southwest-bound, haven't seen any going the opposing direction. The false tracks range from GoF all the way to Bornholm.
November 2, 2025 at 9:47 PM
Also noteworthy: all fake tracks are in logical spots, with courses and speeds correlating with shipping lanes, i.e. not completely randomized. Also they all seem to be west/southwest-bound, haven't seen any going the opposing direction. The false tracks range from GoF all the way to Bornholm.
www.mdpi.com/2076-3417/11...
Something similar, albeit more strictly limited to one AIS receiver was observed 2019 in the Med. Some similarities but many dissimilarities, probably linked to naval EW exercise by this study.
Something similar, albeit more strictly limited to one AIS receiver was observed 2019 in the Med. Some similarities but many dissimilarities, probably linked to naval EW exercise by this study.
November 2, 2025 at 9:31 PM
www.mdpi.com/2076-3417/11...
Something similar, albeit more strictly limited to one AIS receiver was observed 2019 in the Med. Some similarities but many dissimilarities, probably linked to naval EW exercise by this study.
Something similar, albeit more strictly limited to one AIS receiver was observed 2019 in the Med. Some similarities but many dissimilarities, probably linked to naval EW exercise by this study.
Looks like roughly 9 hours ago a huge amount of random ships' AIS positions were updated to northern Baltic Sea, seemingly almost all of them ships with destination and last ports nowhere close to the Baltic Sea.
Someone trying to obfuscate the RMP in the Baltic?
Someone trying to obfuscate the RMP in the Baltic?
November 2, 2025 at 8:35 PM
Looks like roughly 9 hours ago a huge amount of random ships' AIS positions were updated to northern Baltic Sea, seemingly almost all of them ships with destination and last ports nowhere close to the Baltic Sea.
Someone trying to obfuscate the RMP in the Baltic?
Someone trying to obfuscate the RMP in the Baltic?
www.fontanka.ru/2025/07/04/7...
Peskov: "We'll inform you in good time about which actions will take place regarding Navy Day celebrations" --> smells like Fontanka has the gist of it about the cancellation.
Peskov: "We'll inform you in good time about which actions will take place regarding Navy Day celebrations" --> smells like Fontanka has the gist of it about the cancellation.
Песков об отмене парада в Петербурге: Кремль сообщит, какие мероприятия пройдут на День ВМФ
В Кремле проинформируют о графике Владимира Путина и о мероприятиях на День ВМФ в свое время.
www.fontanka.ru
July 4, 2025 at 11:18 AM
www.fontanka.ru/2025/07/04/7...
Peskov: "We'll inform you in good time about which actions will take place regarding Navy Day celebrations" --> smells like Fontanka has the gist of it about the cancellation.
Peskov: "We'll inform you in good time about which actions will take place regarding Navy Day celebrations" --> smells like Fontanka has the gist of it about the cancellation.
According to local telegram channels seems to be infactual. I would be wary with the news concerning Severomorsk.
June 1, 2025 at 4:30 PM
According to local telegram channels seems to be infactual. I would be wary with the news concerning Severomorsk.
www.rpsonline.com.sg/proceedings/...
This study into anchor drag incidents by Rawson and Brito touches on this subject, and one of their results was that "...larger drag distances are significantly less likely than shorter drag distances". I'm not data analysis-savvy enough to judge but looks legit
This study into anchor drag incidents by Rawson and Brito touches on this subject, and one of their results was that "...larger drag distances are significantly less likely than shorter drag distances". I'm not data analysis-savvy enough to judge but looks legit
www.rpsonline.com.sg
January 26, 2025 at 5:53 PM
www.rpsonline.com.sg/proceedings/...
This study into anchor drag incidents by Rawson and Brito touches on this subject, and one of their results was that "...larger drag distances are significantly less likely than shorter drag distances". I'm not data analysis-savvy enough to judge but looks legit
This study into anchor drag incidents by Rawson and Brito touches on this subject, and one of their results was that "...larger drag distances are significantly less likely than shorter drag distances". I'm not data analysis-savvy enough to judge but looks legit
Statistical improbability does not equal attribution to RUS sabotage. Changed pattern of ship traffic (Shadow fleet) certainly would increase the probability of accidents even without nefarious intent. However the "Anchor drags happen globally all the time" argument is completely braindead.
January 26, 2025 at 5:46 PM
Statistical improbability does not equal attribution to RUS sabotage. Changed pattern of ship traffic (Shadow fleet) certainly would increase the probability of accidents even without nefarious intent. However the "Anchor drags happen globally all the time" argument is completely braindead.
Furthermore, a ship just plowing through multiple cables, dragging her anchor for 10's or 100's of kilometers without noticing anything is exceedingly rare. Usual anchor drag cases mostly involve bad weather & rough sea state, which is not the case with these except new new polar bear.
January 26, 2025 at 5:42 PM
Furthermore, a ship just plowing through multiple cables, dragging her anchor for 10's or 100's of kilometers without noticing anything is exceedingly rare. Usual anchor drag cases mostly involve bad weather & rough sea state, which is not the case with these except new new polar bear.