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
20251213025033	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t054h64b10276LoRa iGATE Duisburg-Sued, VFDB Z40
20251213032034	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t054h64b10274LoRa iGATE Duisburg-Sued, VFDB Z40
20251213035034	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t054h64b10276LoRa iGATE Duisburg-Sued, VFDB Z40
20251213042035	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t054h63b10277LoRa iGATE Duisburg-Sued, VFDB Z40
20251213045036	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t055h64b10278LoRa iGATE Duisburg-Sued, VFDB Z40
20251213052037	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t055h64b10280LoRa iGATE Duisburg-Sued, VFDB Z40
20251213055037	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t055h65b10282LoRa iGATE Duisburg-Sued, VFDB Z40
20251213062037	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t055h64b10284LoRa iGATE Duisburg-Sued, VFDB Z40
20251213065038	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2DENMARK:!/4QKhP1c+_ G.../...g...t055h64b10283LoRa iGATE Duisburg-Sued, VFDB Z40
20251213075035	DG3EAJ-12>APLRG1,TCPIP*,qAC,T2UKRAINE:!/4QKhP1c+_ G.../...g...t055h64b10291LoRa iGATE Duisburg-Sued, VFDB Z40