APRS Packet Errors for SR3NJE (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
20260111170703SR3NJE>APNX02,SR3NJE*,qAR,SQ1KSM-10:!5220.51*r*PԲ,SPn NY+ *Q
20260111180716SR3NJE>APNX02,SR3NJE*,qAR,SQ1KSM-10:!5220.51NS0?576.4LQ$60 W&iAJemiolw &
20260111183713SR3NJE>APNX02,SR3NJE*,qAR,SQ1KSM-10:!5220.51NS01=76LWr630 W3
20260111183714SR3NJE>APNX02,SR3NJE*,qAR,SQ3XZ-2:!5220.51NS015̓*#PHG3630 W3,SP Je_Zop. S&Q*
20260111190720SR3NJE>APNX02,SR3NJE*,qAR,SQ3XZ-2:!5220.7N01ML*PHG3630 W?,WPn JY_Z݁ >5F>
20260111205720SR3NJE>APNX02,qAR,SR3NNV:!5220.59Ns:1516.41E#PHG3630"W3SPn Jemiolow X-Dig
20260111214224SR3NJE>APNX02,qAR,SR3NNV:;438.75p-J*111111z5220.51N/015l*ɍ79 K0k SR3ZJ
20260111214248SR3NJE>APNX02,qAR,SR3NNV:;4387=0-J*111111z5220.51N/01516.4Erc079K0 r70k sRsZJ
20260111215225SR3NJE>APNX02,qAR,SR3NNV:;438.7=0-J*111111z5260~01u16.41Erc0?9- 0k S&+9
20260111215306SR3NJE>APNX02,qAR,SR3NNV:;43:>?50-J*111111z522.=1N/q1516.41Erc079(-(1758!R70k SR3ZJ
20260111220240SR3NJE>APNX02,qAR,SR3NNV:;43:.7u0-J*111111z5220.7N r*ɍ79- 170 R70k SR3ZJp
20260111220729SR3NJE>APNX02,SP3-3,qAR,SR3NNV:!5220.51NS01u16.41E#PHG3630 W3,*T R݁op. SP3DFR