APRS Packet Errors for YO5BRE-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
20250314191616YO5BRE-10>APLOX1,HA0HP-10*,WIDE2-2,qAO,HA9OZD-18:=470.32BL02154.90E&hE]F=))IR<3WR2o͐
20250314191616YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90X/ 0` %F]E{+|.$(WUYb2
20250314195816YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90F-3&D%Hi֬zƔ5cK:NNN
20250314200416YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-21:=4703.32NL02154.9!|a`baL4s7m.6gB,alt;tifD5`d%,:F
20250314201616YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAO,HA9OZD-18:=4703.32NL02154.90U
20250314201617YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90U MRRR@(%b,De {M1jyNNN
20250314212818YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=470?2L254.905Ha~i 8d9vNNNa_hNu4<;;DTpRb4
20250314222218YO5BRE-10>APLOX1,HA9OZD-20*,TIDE2-2,qAO,HA9OZD-18:=4703.32NL02154.90Ģ||OX lq01ZDGkv54j DvvR(
20250314222218YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90##|muGXq#2koKmHJGJN>uC DV<.U