APRS Track Direct

My position About ☰

reset

DG3EAJ-12 Raw Packets

This is the latest recevied packets stored in our database for station/object DG3EAJ-12. If no packets are shown the sender has not sent any packets the latest 24 hours.

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.

<< 1 2 3 >>

1765500634: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10228LoRa iGATE Duisburg-Sued, VFDB Z40

1765498833: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h65b10230LoRa iGATE Duisburg-Sued, VFDB Z40

1765497032: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h65b10233LoRa iGATE Duisburg-Sued, VFDB Z40

1765495232: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10234LoRa iGATE Duisburg-Sued, VFDB Z40

1765493432: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10237LoRa iGATE Duisburg-Sued, VFDB Z40

1765491632: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10236LoRa iGATE Duisburg-Sued, VFDB Z40

1765489831: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10235LoRa iGATE Duisburg-Sued, VFDB Z40

1765488030: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10234LoRa iGATE Duisburg-Sued, VFDB Z40

1765486231: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10235LoRa iGATE Duisburg-Sued, VFDB Z40

1765484430: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10236LoRa iGATE Duisburg-Sued, VFDB Z40

1765482630: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ G.../...g...t055h64b10236LoRa iGATE Duisburg-Sued, VFDB Z40

1765480830: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:>https://github.com/richonguzman/LoRa_APRS_iGate 2025.03.20

1765480828: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2HUN:!/4QKhP1c+_ GDG3EAJ-12>APLRG1,WIDE1-1LoRa iGATE Duisburg-Sued, VFDB Z40

1765479031: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h64b10233LoRa iGATE Duisburg-Sued, VFDB Z40

1765477231: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h64b10235LoRa iGATE Duisburg-Sued, VFDB Z40

1765475431: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h64b10236LoRa iGATE Duisburg-Sued, VFDB Z40

1765473630: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h64b10236LoRa iGATE Duisburg-Sued, VFDB Z40

1765471830: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h64b10237LoRa iGATE Duisburg-Sued, VFDB Z40

1765470029: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h64b10236LoRa iGATE Duisburg-Sued, VFDB Z40

1765468229: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h64b10237LoRa iGATE Duisburg-Sued, VFDB Z40

1765466429: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h64b10237LoRa iGATE Duisburg-Sued, VFDB Z40

1765464629: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h65b10239LoRa iGATE Duisburg-Sued, VFDB Z40

1765462828: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t056h65b10241LoRa iGATE Duisburg-Sued, VFDB Z40

1765461028: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t057h65b10244LoRa iGATE Duisburg-Sued, VFDB Z40

1765459229: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:>https://github.com/richonguzman/LoRa_APRS_iGate 2025.03.20

Select date and time to show map data for (enter time for your locale time zone). The regular time length select box can still be used to select how old data that should be shown (relative to selected date and time).

*Note that the heatmap will still based on data from the latest hour (not the selected date and time).

Date and time: