APRS Packet Errors for BG1NZR-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
20260208132810BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208135813BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208142815BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208145818BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208152821BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208155754BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208162758BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208165800BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208172803BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208175805BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208182808BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO
20260208185810BG1NZR-15>APFMO2,TCPIP*,qAC,T2HK:=4003.75N/11617.50EIHello FMO