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
20260208130443DF9EG-1>APRSMC,TCPIP*,qAR,DC1BEL-99:!5136.51N/00713.15Eb#df9eg-2/B=100/A=000187
20260208133504DF9EG-1>APRSMC,TCPIP*,qAR,DF8DL-11:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000299
20260208140510DF9EG-1>APRSMC,TCPIP*,qAR,DF8DL-11:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000272
20260208143525DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.16Eb#df9eg-2/B=100/A=000377
20260208150540DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000240
20260208153556DF9EG-1>APRSMC,TCPIP*,qAR,DC1BEL-99:!5136.53N/00713.16Eb#df9eg-2/B=100/A=000262
20260208154924DF9EG-1>APRSMC,TCPIP*,qAR,DL2EGS-15:!5136.53N/00713.16Eb#df9eg-2/B=100/A=000262
20260208160610DF9EG-1>APRSMC,TCPIP*,qAR,DC1BEL-99:!5136.53N/00713.18Eb#df9eg-2/B=100/A=000279
20260208163625DF9EG-1>APRSMC,TCPIP*,qAR,DC1BEL-99:!5136.54N/00713.18Eb#df9eg-2/B=100/A=000256
20260208170644DF9EG-1>APRSMC,TCPIP*,qAR,DF2OW-12:!5136.53N/00713.18Eb#df9eg-2/B=100/A=000256
20260208173655DF9EG-1>APRSMC,TCPIP*,qAR,DC1BEL-99:!5136.52N/00713.16Eb#df9eg-2/B=100/A=000338
20260208180712DF9EG-1>APRSMC,TCPIP*,qAR,DO1CMH-3:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000269
20260208183735DF9EG-1>APRSMC,TCPIP*,qAR,DC1BEL-99:!5136.53N/00713.17Eb#df9eg-2/B=100/A=000256