APRS Packet Errors for OH2BEA-9 (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
20260327181001OH2BEA-9>APAT81,WIDE2-1,qAR,ESAJ-3:!6021.34N/0R501.98E[084/°10/A=00°Q(0@ DMR TG244, R0T OH2RUF or Dapner
20260327182054OH2BEA-9>APAT81,WIDE2*,qAR,OH7JHF-1:!6011.34N/0251.98E[247/000/A=000000@ DMR TG244, RPT OH2RUF or Dapnet
20260327185338OH2BEA-9>APAT81,WIDE2-1,qAR,OH7JHF-1:!601.34N/02501.98E[248/000/A=000000@ DMR TG244, RPT OH2RUF or Dapnet
20260327205050OH2BEA-9>APAT81,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:!6011.34N/02501.9E[104/000/A=000000@ DMR TG244, RPT OH2RUF or Dapnet
20260327215611OH2BEA-9>APAT81,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:!6011.34N/2501.98E[142/002/A=000000@ DMR TG244, RPT OH2RUF or Dapnet
20260327220054OH2BEA-9>APAT81,WIDE2-1,qAR,OH7JHF-1:!011.34N/0250198E[153/000/A=000000@ DMR TG244, RPT OH2RUF or Dapnet
20260327230122OH2BEA-9>APAT81,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:!6011.34/02501.98E[303/000/A=000000@ DMR TG244, RPT OH2RUF or Dapnet
20260327232001OH2BEA-9>APAT81,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:!601.34N/02501.98E[106/000/A=000000@ DMR TG244, RPT OH2RUF or Dapnet
20260327232440OH2BEA-9>APAT81,OH2RDK-7,WIDE2*,qAR,OH7JHF-1:!6011.34N/02501.8E[106/000/A=000000@ DMR TG244, RPT OH2RUF or Dapnet