APRS Packet Errors for SR3WXA (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
20260220050424SR3WXA>APTT4,SR3NJE*,qAR,SQ3RCH-3:@20Sӓ224.78/01673>5Qz:002?r00&0000Ř.&V7
20260220054914SR3WXA>ApTT4,SR3NJE*,qAR,SQ3RCH-3:@2L224.78N?01>53*}z:000pP00L.q>
20260220055047SR3WXA>APTT4,SR3NJE*,qAR,SQ3RCH-3:=5224.78N/0165s52E_PHG3280"RoznXzx. SX3LYR Q=279
20260220060938SR3WXA>GPTT4,SR3NJE*,qAR,SQ3RCH-3:@200>03z5224.78N/01653.=2E_0p0/0pL0t00P00B1Ӧr"y?
20260220071638SR3WXA>APTT4,SR3NJE*,qAR,SQ3RCH-3:@200710z5224.78N/01653.52M_000/000g0rpt221r000x000P000hLN244.D.
20260220072647SR3WXA>APTT4,SR3NJE*,qAR,SQ3RCH-3:@200720z5224.78N/01653.52Sz:0t021r00802P000h8vb102S
20260220073138SR3WXA>APTT4,SR3NJE*,qAR,SQ3RCH-3:@200725z5224.78N/0LSr*}z:8t032r000pp00T022h:610274LsVP
20260220080530SR3WXA>APTT4,SR3NJE*,qAR,SQ3RCH-3:@20075z5224.7ISr*z:00t064r000zx8Pz40jx&’bN.2{VpC
20260220080531SR3WXA>CPTT4,SR3NJE*,qAR,SQ3RCH-3:@200758z522.78 5?.52E_000g000t024r0p0܂00h欂n9>sC
20260220084537SR3WXA>APTT4,SR3NNE*,qAR,SQ3RCH-3:@200x38z5224.78No0653.56E_00/L0f&}~p2?L~"Y