APRS Packet Errors for BG5DAY-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
20260209091154BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209092151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209093152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209094151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209095151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209100151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209101151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209102151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209103151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209104151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209105152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209110151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209111151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209112151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209113151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209114152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209115151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209120151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209121152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209122151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209123152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209124151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209125151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209130152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209131152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209132152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209133154BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209134152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209135152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209140152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209141152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209142152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209143152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209144159BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209145151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260209150151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨