APRS Packet Errors for N0GPS-2 (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
20260908074458N0GPS-2>APAT81-1,KF6ILA-10*,WIDE2-2,qAO,KD6LPA:!3248.20N/1±609.09W|049/000/A=000318AnyTone878UV
20260908074459N0GPS-2>APAT81-1,KF6ILA-10*,N6EX-4,qAR,KK6CKK-1:!3248.20N/1±609.09W|049/000/A=000318AnyTone878UV
20260908080126N0GPS-2>APAT81-1,KF6ILA-10*,WIDE2-2,qAO,KD6LPA:!3248-20N/11709.09W|049/000/A=000318AnyTone 878UV
20260908081854N0GPS-2>APAT81-1,KF6ILA-10*,WIDE2-2,qAR,KF6NXQ-15:!3248.20N/11709.0:W|229/000/A
20260908082604N0GPS-2>APAT81-1,KF6ILA-10*,WIDE2-2,qAO,KD6LPA:!3248"20N/11709.09W|032/000/A=000305AnyTone 878UV
20260908095009N0GPS-2>APAT81-1,WIDE1-1,WIDE2-2,qAR,KD6DCN-5:!0000.00N/00000.00W&329/000/A=000000
20260908095042N0GPS-2>APAT81-1,WIDE1-1,WIDE2-2,qAR,KD6DCN-5:!0000.00N/00000.00W&329/000/A=000000
20260908095148N0GPS-2>APAT81-1,WIDE1-1,WIDE2-2,qAR,KD6DCN-5:!0000.00N/00000.00W&329/000/A=000000
20260908102241N0GPS-2>APAT81-1,KF6ILA-10*,WIDE2-2,qAO,KD6LPA:!3248"20N/11709.09W&151/000/A=000337