APRS Packet Errors for E20VSH-7 (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
20260209103400E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1357.06N10031.86EP048/001Park
20260209103559E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1357.07N/10031.88E>070/012
20260209103815E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1356.53N/10032.57E>027/027
20260209103856E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1356.84N/10032.73E>026/032
20260209103927E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1357.’rqÅ0032.83EP027/002Park
20260209104000E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1357.03N/10032.83E>119/004
20260209104032E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1356.91N/10032.78E>143/004E20VSH IndyTracker 2.3f
20260209104120E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1356.88N10032.86E@104/001Park
20260209104149E20VSH-7>AESPT2-3,WIDE0-1,qAR,E22UMT-1:=1356.85N/10032.90E>144/009
20260209110002E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1356.89N10032.78EP271/000Park
20260209110029E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1356.88N/10032.76E>206/004E20VSH IndyTracker 2.3f
20260209110105E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1356.79N10032.71EP205/002Park
20260209111905E20VSH-7>AESPT2-3,WIDE1-1,qAR,E22UMT-1:=1356.99N10031.76EP241/001Park