APRS Packet Errors for SN0PEK-10 (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
20260309152843SN0PEK-10>APLFLC,NOHUB,qAR,AF6UA-10:/152840h0000.00N/00000.00EO000/000/A=000000/P1S0O10F5R1
20260309153333SN0PEK-10>APLFLC,NOHUB,qAR,N6SUN-10:/153330h0000.00N/00000.00EO000/000/A=000000/P2S0O12F5R1
20260309153820SN0PEK-10>APLFLC,NOHUB,qAR,N6SUN-10:/153819h0000.00N/00000.00EO000/000/A=000000/P3S0O14F5R1
20260309170226SN0PEK-10>APLFLC,NOHUB,qAR,N6SUN-10:/170225h0000.00N/00000.00EO000/000/A=000000/P21S0O20F5R1
20260309170716SN0PEK-10>APLFLC,NOHUB,qAR,N6SUN-10:/170715h0000.00N/00000.00EO000/000/A=000000/P22S0O20F5R1
20260309180434SN0PEK-10>APLFLC,NOHUB,qAO,W6SLO-6:/180432h0000.00N/00000.00EO000/000/A=000000/P34S0O20F5R1
20260309180920SN0PEK-10>APLFLC,NOHUB,qAO,W6SLO-6:/180919h0000.00N/00000.00EO000/000/A=000000/P35S0O20F5R1
20260309181410SN0PEK-10>APLFLC,NOHUB,qAO,W6SLO-6:/181409h0000.00N/00000.00EO000/000/A=000000/P36S0O20F5R1