LoRa APRS Track Direct

☰

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1761503951: DG3EAJ-12>APLRG1,TCPIP*,qAC,T2CZECH:!/4QKhP1c+_ G.../...g...t056h61b10070LoRa 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:

Maintained by I8FUC, based on APRS Track Direct