APRS Packet Errors for SR3PN (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
20260204020257SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5:s0.3rN/01615.26E+DIGIU9%]e
20260204020257SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!230>32N r*t
20260204022753SR3pN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230>3& 6LMIE?DyGH PNEU
20260204033252SR3PN>APMI03,SR7NJE*,qAR,SQ3RCH-3:!5230.&&ꒊr*DIGI(w1RUe
20260204034753SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.32N Sr*DZV%QNIEWY
20260204041258SR3PN>APMi03,SR3NJE-4*,qAR,SQ3RCH-3:!5230.32N/01615.26UdVV9%]e
20260204042755SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.32N/01615.2>E$TT) PNIEWY
20260204050258SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.32N/0161526G#DIGI W1 PNIEWY
20260204050259SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5r30.32No016q5.>6E#DIGI W1 PNIEW
20260204050802SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.32N r*DIGI W1 *]}
20260204061302SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.?2 r*DIGɐ_%WY
20260204061810SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.32N/01>1M*DIGI W1 PNIE_Y
20260204065805SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!523ir01615.26E#ET)9%]e
20260204065806SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!523r01615.26E#IGI U %]e
20260204071305SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!m30.3& r*DR PNIEWY