APRS Packet Errors for DF9EG-1 (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
20260209161547DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.18Eb#df9eg-2/B=100/A=000272
20260209164551DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.18Eb#df9eg-2/B=100/A=000226
20260209171606DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000240
20260209173425DF9EG-1>APRSMC,TCPIP*,qAR,DO1CMH-3:!5136.53N/00713.18Eb#df9eg-2/B=100/A=000361
20260209173553DF9EG-1>APRSMC,TCPIP*,qAR,DO1CMH-3:!5136.50N/00713.15Eb#df9eg-2/B=100/A=000348
20260209180608DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.16Eb#df9eg-2/B=100/A=000295
20260209183623DF9EG-1>APRSMC,TCPIP*,qAR,DO1CMH-3:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000269
20260209190648DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000292
20260209193650DF9EG-1>APRSMC,TCPIP*,qAR,DC1BEL-99:!5136.53N/00713.18Eb#df9eg-2/B=100/A=000210
20260209200705DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000289
20260209204840DF9EG-1>APRSMC,TCPIP*,qAR,DO0FFE-12:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000285
20260209210737DF9EG-1>APRSMC,TCPIP*,qAR,DC1BEL-99:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000292
20260209213750DF9EG-1>APRSMC,TCPIP*,qAR,DO1CMH-3:!5136.53N/00713.18Eb#df9eg-2/B=100/A=000259