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
20260220045446SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230iNo016q5.26M#DIGy W7 QU
20260220045521SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.72Nop1615.26E#DIg)U&9%W]m!
20260220050513SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.32N0163526E#DIGI0Wq5]e
20260220051006SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!523irʲr*5"%"U
20260220051007SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5r30.32N/016q5.26E$T/UA9?]e
20260220052959SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!52&rr07615IQ$T%W1 *]e
20260220055504SR3PN>APMI03,SR3NJE-1*,qAR,SQ3RCH-3:!52s0.32N .26E#DIGI W1*]e
20260220065504SR3PN>APMI03,SR3NzE*,qAR,SQ3RCH-3:!5230.32N/Sr*T*
20260220065958SR3PN>APMI03,SR3WR,SR3NJE,WIDE2*,qAR,SQ3RCH-3:!5230>32N/01615.26Q$QRT
20260220071012SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.32N/01615n26E#DIGI W1 PNYEW
20260220072954SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.32N/01615.26McTiORPNIEWY
20260220073036SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!523032N/01S5.26E#|yGr pNOEU
20260220074955SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!72;p.rպʪr*5"%rŁ*_Y
20260220075510SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.;rNo21615.26E#DIV) PNIEWY
20260220084005SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!52sp.32No21617.26Q$T
20260220090009SR3PN>APMI03,SR3NJE*,qAR,SQ3RCH-3:!5230.&& S.26E#DIGM(W9 ZNiQUE