APRS Packet Errors for LW2DHT-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
20260208130631LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,-?`C_b=1Q
20260208132132LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,7?`Cab=:Q
20260208133633LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,A?`C]b==Q
20260208135135LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,(?`C]b
20260208140635LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,T?`Cob
20260208142136LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,Y?`Ceb
20260208143637LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,m?`Ceb9YQ
20260208145432LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,{?`Cjb=QQ
20260208150932LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,r?`D-b;_Q
20260208152434LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,A?`Cob
20260208154033LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,c?`Cyb=4Q
20260208160019LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,2?`CNb?2Q
20260208161519LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,m?`Cjb=CQ
20260208163021LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,c?`Cob=tQTracker Heltec de Prueba modo Moto
20260208164522LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,c?`Ctb=+Q
20260208170022LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z,c?`Cob<-Q
20260208171523LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z-3?`DRb:nQ
20260208172537LW2DHT-7>APLRT1,WIDE1-1,qAR,LW2DHT-3:=/_z+j?`CDb9eQ