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
20260524171712YO5BRE-10>APLOX1,WIDE1-1,WIDE2-2,qAR,HA9OZD-17:=4703.32NL0r550j90EfIate Lma,W%ant.5dB&alt 33m,Oradea Batt=4.29V,
20260524175917YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90t*&NNNA`aRRRn`_ a79E͕k0I?NNNr
20260524181717YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90>7m5d
20260524182917YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90[7>ͪ0L$(Ƌ`qׂq&W%
20260524184718YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90]2|#<zzFef[)sjGטWb#+
20260524192318YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90_6M>Ƞċ RFHs؝ׂ>.G %,V[SVi
20260524192918YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90RRRRRR`pRȠ`lNB4&~@c5.M :3w^KJxrNNNC
20260524194719YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90[>>,Ċdn$ ƪOq=w!NNN3&d%%~ەRi
20260524195919YO5BRE-10>APLOX1,HA9OZD-20*,WIDE2-2,qAR,HA9OZD-17:=4703.32NL02154.90FU;d왹>Zn|bitOh|b`ya