APRS Packet Errors for SP7TPC-7 (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
20260404151127SP7TPC-7>APAT81-1,SR9KFZ,WIDE1,SR5DRK*,qAR,SP5KAB-3:!504!8.29N/01908.89E[044/000/A=000931SR9CZE
20260404153705SP7TPC-7>APAT81-1,SR9KFZ,WIDE1,SR5DRK*,qAR,SR5NEB:!5048.249N/01908.90E[147/000/A=000508SR9CZE
20260404153914SP7TPC-7>APAT81-1,SR9KFZ,WIDE1,SR5DRK*,qAR,SP5KAB-3:!5048.29N/091908.91E[147/000/A=000377SR9CZE
20260404154027SP7TPC-7>APAT81-1,SR9KFZ,WIDE1,SR5DRK*,qAR,SP5KAB-3:!5048.029N/01908.90E[147/000/A=000715SR9CZE
20260404172321SP7TPC-7>APAT81-1,SR9KFZ,WIDE1,SR5DRK*,qAR,SR5NEB:!5048.28N./01908.88E[095/000/A=000754SR9CZE
20260404183213SP7TPC-7>APAT81-1,SR9KFZ,WIDE1,SR5DRK*,qAR,SR7U-1:!5048.29N/201908.90E[174/000/A=000856SR9CZE
20260404192055SP7TPC-7>APAT81-1,SR9KFZ,WIDE1,SR5DRK*,qAR,SR5NEB:!5048.29N/019008.90E[108/000/A=000935SR9CZE