APRS Packet Errors for YO5ZQ-10 (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
20260615062908YO5ZQ-10>APRS,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00W>226 77 30 307 44
20260615063913YO5ZQ-10>APRS,WIDE2-1,qAO,SV2HNH:!0000.00N/00000.00W>222 83 29 309 44
20260615073944YO5ZQ-10>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>189 73 33 306 44
20260615074950YO5ZQ-10>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>189 76 32 312 44
20260615085021YO5ZQ-10>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>211 66 39 304 44 m318 M141 r250
20260615090026YO5ZQ-10>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>209 66 40 299 44
20260615100100YO5ZQ-10>APRS,SV3GCB-11,WIDE2*,qAR,SV3GCB-3:!0000.00N/00000.00W>238 59 46 294 44
20260615101111YO5ZQ-10>APRS,WIDE2-1,qAR,YM1KTC-11:!0000.00N/00000.00W>216 59 46 294 44
20260615111218YO5ZQ-10>APRS,WIDE2-1,qAR,YM1KTC-11:!0000.00N/00000.00W>174 61 42 303 44
20260615112223YO5ZQ-10>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>193 61 42 303 44