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
20260220065901SR3NJE>APNX02,qAR,SQ3RCH-3:;438.750-J*111111z522.51N/01516.41Ezk0S"1?w0 R70k SR;Zj
20260220065902SR3NJE>APNX02,qAR,SQ3RCH-3:;438.7MjR111111z5660.5N/015Lɽ79`- ?70 R7}IZ
20260220070405SR3NJE>APNX02,qAR,SQ3RCH-3:!5220.51NSS.*PHG&ӂ,Spn Jmilow(X-Lmgi
20260220072406SR3NJE>APNX02,WIDE,qAR,SQ3RCH-3:!5220.51NS01516.41G#PHG3630 W3,SPn Jemiolow altoza=820
20260220073404SR3NJE>OPNX02,qAR,SQ3RCH-3:!5220.51jr*PHԲ`W&NemiolX-Dygi
20260220073903SR3NJE>APNX02,qAR,SQ3RCH-3:;438.750K)220.51N 6.4Lqlj?50 Z*ݥ
20260220073915SR3NJE>APNX02,qAR,SQ3RCH-3:;438.750-J*111113z5228.51N/015Ls*ɍ"jI0k*
20260220074904SR3NJE>APNX02,qAR,SQ3RCH-3:;438.750-J*111111z5220.] Srjɍju­MYZJ
20260220081418SR3NJE>APNX02,SR3NJE*,qAR,SR3NKI:!72&vNW0_.Lq !6?p Vp.
20260220084409SR3NJE>APNX02,SP3-3,qAR,SQ3RCH-3:!5220MLjr:XHG76;0Si5 JemZo. *;DFZ*
20260220085415SR3NJE>APNX02,WIDE,qAR,SQ3RCH-3:!522p.MLjrE#PH&3,SPn NeZX>HpO&
20260220090418SR3NJE>APNX02,qAR,SQ3RCH-3:!5220.51NS2951/4Q$&ӂ5bAj[[aDigZ
20260220091949SR3NJE>APNX02,qAR,SQ3RCH-3:;43x.??0*111111z5220.5N/095;6*%7 -"3?50`R72k SR&
20260220100925SR3NJE>APNX02,qAR,SQ3RCH-3:;48>SjR*11q331z=::n51Sr*ɟw;0["R7-*f/