APRS Packet Errors for BH5HYR-15 (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
20260208134018	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208140950	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208143951	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208150952	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208153953	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208160954	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208163955	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208170956	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208173957	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208180958	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208183959	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR
20260208191000	BH5HYR-15>APFMO2,TCPIP*,qAC,T2FZ:=3026.47N/12018.91EIBH5HYR