APRS Packet Errors for ON4MAX (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
20250715200923ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250715204002ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250715211041ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250715214120ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250715221159ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250715224237ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250715231315ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250715234355ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250716001218ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz
20250716004252ON4MAX>APZDMR,QTH,TCPIP*,qAU,T2STRAS:)ON4MAX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FRANCE 3 MMDVM 439.9500 MHz