APRS Packet Errors for OH7JHF-1 (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
20260208134514OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208141515OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208144516OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208151517OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208154518OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208161519OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208164520OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208171521OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208174522OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208181523OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208184524OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase
20260208191525OH7JHF-1>APX216,TCPIP*,qAC,FIRST:=6010.38N/02501.40E-PHG3230 OH7JHF homebase