APRS Packet Errors for PI6SHB (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
20260208144220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208151220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208154220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208161220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208164220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208171220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208174220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208181220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208184220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208191220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208194220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800
20260208201220PD9BG-10>APDW17,qAS,PD9BG:;PI6SHB *111111z5141.98N/00520.84ErA42.350MHz T071 +2800