APRS Packet Errors for DO7TW-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
20260209121111DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=007/A=001444
20260209131141DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=008/A=001444
20260209134156DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=010/A=001444
20260209141214DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=009/A=001444
20260209144229DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=018/A=001444
20260209151244DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=019/A=001444
20260209154259DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=007/A=001444
20260209161345DO7TW-1>APRSMC,TCPIP*,qAR,DO1MH-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=097/A=001444
20260209164333DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=100/A=001444
20260209171348DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=008/A=001444
20260209174404DO7TW-1>APRSMC,TCPIP*,qAR,DB0FHR-12:!4751.90N/01207.91E-MeshCom Rosenheim#Thomas/B=023/A=001444