APRS Packet Errors for DD8XX-3 (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
20260405113755DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6MbOQ
20260405114756DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mb>Q
20260405115757DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mb.Q
20260405120757DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6MarQ
20260405121759DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mb+Q
20260405122757DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6MauQ
20260405123758DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mb6Q
20260405131504DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6MbXQ
20260405132502DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mb[Q_KuQ.../...g...t075h..b10294
20260405133502DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6McOQ
20260405135903DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mb0Q
20260405140904DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mb.Q
20260405141906DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mb9Q
20260405150206DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Mc>Q
20260405152157DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6MawQ
20260405153157DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6Ma{Q
20260405154156DD8XX-3>APLRT1,WIDE1-1,qAR,DD8XX-10:=/6MaoQ