APRS Packet Errors for EA4E-10 (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
20260208171821EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208174822EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208180322EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208181822EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208183322EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208184821EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208190322EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208191822EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208193321EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208194822EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208200322EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208211822EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208213322EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208220322EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo
20260208223322EA4E-10>APLRG1,WIDE3-3,qAR,EA4AAH-10:=L:530MSxj& !GBoLoRa APRS Toledo