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 >>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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: