APRS Packet Errors for DB0CRE-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
20260208132232DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260208133414DB0CRE-12>APRSMC,TCPIP*,qAR,DF2OW-12:!5137.75N0715.56E-/B=100/A=000397
20260208135250DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260208142306DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/A=000397
20260208145321DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260208152336DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260208155351DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/A=000397
20260208162406DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260208165421DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260208172438DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260208175453DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/A=000397
20260208182508DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397
20260208185523DB0CRE-12>APRSGW,TCPIP*,qAR,DB0CRE-12:!5137.75N0715.56E-/B=100/A=000397