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
20260208145152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208150152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208151151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208152154BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208153152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208154152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208155152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208160152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208161151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208162151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208163152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208164152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208165151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208170152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208171151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208172151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208173151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208174151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208175152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208180151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208181151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208182151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208183151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208184151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208185151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208190309BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208191152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208192151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208193151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208194151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208195152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208200152BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208201151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208202151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208203151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨
20260208204151BG5DAY-15>APFMO2,TCPIP*,qAC,T2HK:=2944.39N/12010.25EI浙江诸暨