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
20260109140750SR3WXA>APTT4,SR3NPB*,WIDE2-1,qAR,SR3DPN:@0973Ҿ§p1rp p6.0fS[
20260109150213SR3WXA>APTT4,SR3NPB*,WIDE2-1,qAR,SR3DPN:@091MN?6?352/&0&00P000+0047L00sVP
20260109151828SR3WXA>APTT4,qAR,SR3DPN:=5224.78N/01>53>MG3n SsL O
20260109153304SR3WXA>APTT4,WIDE2-2,qAR,SR3DPN:@0NL224.78 M&>p0L0>.0L09L0L0.Dw^p
20260109155316SR3WXA>APTT4,SR3NPB*,WIDE2-1,qAR,SR3DPN:@p9LM2~ 3ןQ0p0pg0`0.03f18
20260109163242SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAO,SQ3A-2:@0NL224.w8^16=3.52z00Lw|B3f00?00LC
20260109165151SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAR,SR3NPB:@0NLS224.?p1S2z:000>0LZ&0r">
20260109165708SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAR,SR3NPB:@091650z5224?8/0Lӗ>}00/0&>L0pph97Ř
20260109170706SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAR,SR3NPB:@091700z5&r01653.=2_0/p00g00pt0񓂂00p00h&LL`L~
20260109171206SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAR,SR3NPB:@09170224.78N/013>}L~zɘp|00B3|ppj
20260109171846SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAR,SR3NPB:=5224.78N/0LSr*}A!2Kna SP3V
20260109172651SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAR,SR3NPB:@09L&Ғrr/0?6&}000/00g0p0|01>P00̂5|000.
20260109174150SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAR,SR3NPB:@091735z5224.78N 53*}00?0p&00p0L0&~p
20260109175234SR3WXA>APTT4,SR3DPN*,WIDE2-1,qAO,SQ3A-2:@091745z522<7N/01>>~g00&6000p00PN2ú0