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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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