APRS Packet Errors for SN0PEK-5 (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
20260126041609SN0PEK-5>APLFLC,NOHUB,qAO,BG3ISR-9:/041607h0000.00N/00000.00EO000/000/A=000000/P26S0O20F7R1
20260126042056SN0PEK-5>APLFLC,NOHUB,qAO,BI3TVW-15:/042054h0000.00N/00000.00EO000/000/A=000000/P27S0O20F7R1
20260126042545SN0PEK-5>APLFLC,NOHUB,qAO,BI3TVW-15:/042544h0000.00N/00000.00EO000/000/A=000000/P28S0O20F7R1
20260126044002SN0PEK-5>APLFLC,NOHUB,qAO,BI3TVW-15:/044000h0000.00N/00000.00EO000/000/A=000000/P31S0O20F7R1
20260126044908SN0PEK-5>APLFLC,NOHUB,qAO,BI3TVW-15:/044906h0000.00N/00000.00EO000/000/A=000000/P33S0O20F7R1
20260126045359SN0PEK-5>APLFLC,NOHUB,qAO,BI3TVW-15:/045357h0000.00N/00000.00EO000/000/A=000000/P34S0O20F7R1
20260126045846SN0PEK-5>APLFLC,NOHUB,qAO,BI3TVW-15:/045844h0000.00N/00000.00EO000/000/A=000000/P35S0O20F7R1
20260126050335SN0PEK-5>APLFLC,NOHUB,qAO,BI3TVW-15:/050333h0000.00N/00000.00EO000/000/A=000000/P36S0O20F7R1
20260126053501SN0PEK-5>APLFLC,NOHUB,qAO,BI3TVW-15:/053459h0000.00N/00000.00EO000/000/A=000000/P43S0O20F7R1