APRS Packet Errors for DG3EAJ-12 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20260715232256DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t082h34b10209LoRa iGATE Duisburg-Sued, VFDB Z40
20260715235257DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t082h35b10210LoRa iGATE Duisburg-Sued, VFDB Z40
20260716002257DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t081h35b10208LoRa iGATE Duisburg-Sued, VFDB Z40
20260716005257DG3EAJ-12>APLRG1,TCPIP*,qAC,T2PRT:!/4QKhP1c+_ G.../...g...t081h36b10207LoRa iGATE Duisburg-Sued, VFDB Z40
20260716015257DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t081h37b10205LoRa iGATE Duisburg-Sued, VFDB Z40
20260716022258DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t081h38b10205LoRa iGATE Duisburg-Sued, VFDB Z40
20260716025258DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t081h39b10201LoRa iGATE Duisburg-Sued, VFDB Z40
20260716032258DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t081h38b10201LoRa iGATE Duisburg-Sued, VFDB Z40
20260716035259DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t080h41b10200LoRa iGATE Duisburg-Sued, VFDB Z40
20260716042300DG3EAJ-12>APLRG1,TCPIP*,qAC,T2LAUSITZ:!/4QKhP1c+_ G.../...g...t080h40b10200LoRa iGATE Duisburg-Sued, VFDB Z40