APRS Packet Errors for DB0CRE-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
20260209114331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091143z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209115831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091158z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209121331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091213z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209122831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091228z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209124331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091243z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209125831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091258z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209131331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091313z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209131936DB0CRE-1>APMI06,DC4ML-7*,qAR,DB0SEP-1:@091258z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209132831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091328z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209134331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091343z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209135831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091358z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209141331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091413z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209142338DB0CRE-1>APMI06,DC4ML-7*,qAR,DB0SEP-1:@091358z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209142831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091428z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209144331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091443z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209145831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091458z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209151331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091513z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209152737DB0CRE-1>APMI06,DC4ML-7*,qAR,DB0SEP-1:@091458z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209152831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091528z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209154331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091543z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209155831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091558z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209161331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091613z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209162831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091628z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209164331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091643z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209165831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091658z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209171331DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091713z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm
20260209172831DB0CRE-1>APMI06,TCPIP*,qAS,DB0CRE:@091728z5137.75N/00715.56E-APRS Digi N18 LoRa und MeshCom 2m / 70cm