APRS Packet Errors for YO5ZS-5 (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
20261121123057YO5ZS-5>APRS,WIDE2-1,qAR,EW1EM-9:!0000.00N/00000.00W>124 78 27 129 43 a2 d0 h4
20261121124956YO5ZS-5>APRS,WIDE2-1,qAR,EW1EM-9:!0000.00N/00000.00W>105 77 50 296 43 m321 M131 r208
20261121125530YO5ZS-5>APRS,WIDE2-1,qAR,EW1EM-9:!0000.00N/00000.00W>91 77 40 306 43 a1 d0 h4
20261121130104YO5ZS-5>APRS,WIDE2-1,qAR,EW1EM-9:!0000.00N/00000.00W>130 76 41 305 43 a2 d0 h4
20261121131958YO5ZS-5>APRS,WIDE2-1,qAR,4L0VE-12:!0000.00N/00000.00W>132 58 62 212 43 m321 M131 r209
20261121133254YO5ZS-5>APRS,WIDE2-1,qAR,4L0VE-12:!0000.00N/00000.00W>80 49 50 295 43 m321 M131 r209