APRS Direct - APRS Tracker

My position 11:23:59 AM ☰

Leaflet © OpenStreetMap contributors

Connected

40º 36' 35'' N 23º 3' 20'' E
40.60983, 23.05567
KN10MO

reset

Time Travel Active

reset

SV2F-B Raw Packets

A total of 72 recevied packets have been found for station/object SV2F-B from the past 24 hours. This took 0.121 seconds to find in our database.

If you compare the raw packets with similar data from other websites it may differ (especially the path), the reason is that we are not collecting packets from the same APRS-IS servers. Each APRS-IS server performes duplicate filtering, and which packet that is considered to be a duplicate may differ depending on which APRS-IS server you receive your data from.

Displaying 1 - 25 of 72 packets.

06/09/2025 11:18:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 10:58:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 10:38:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 10:18:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 9:58:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 9:38:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 9:18:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 8:58:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 8:38:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 8:18:44 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 7:58:34 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 7:38:34 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 7:18:34 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 6:58:34 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 6:38:34 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 6:18:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 5:58:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 5:38:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 5:18:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 4:58:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 4:38:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 4:18:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 3:58:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 3:38:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz

06/09/2025 3:18:33 AM+00:00: SV2F-B>APDG02,TCPIP*,qAC,SV2F-BS:!4036.59ND02303.34E&RNG0025 440 Voice 439.42500MHz -7.6000MHz