APRS Packet Errors for DG1KWA-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
20260209092535DG1KWA-10>APLRG1,WIDE1-1,qAO,DB0UHC-L4:=L45eP6R*& !GLoRa iGATE & Digi, DG1KWA Monheim am Rhein Batt=4.18V
20260209094035DG1KWA-10>APLRG1,WIDE1-1,qAO,DD4EB-10:=L45eP6R*& !GLoRa iGATE & Digi, DG1KWA Monheim am Rhein Batt=4.18V
20260209095535DG1KWA-10>APLRG1,WIDE1-1,qAO,DB0UHC-L4:=L45eP6R*& !GLoRa iGATE & Digi, DG1KWA Monheim am Rhein Batt=4.19V
20260209102535DG1KWA-10>APLRG1,WIDE1-1,qAO,DB0UHC-L4:=L45eP6R*& !GLoRa iGATE & Digi, DG1KWA Monheim am Rhein Batt=4.19V
20260209122537DG1KWA-10>APLRG1,WIDE1-1,qAO,DB0UHC-L4:=L45eP6R*& !GLoRa iGATE & Digi, DG1KWA Monheim am Rhein Batt=4.17V
20260209124037DG1KWA-10>APLRG1,WIDE1-1,qAO,DB0UHC-L4:=L45eP6R*& !GLoRa iGATE & Digi, DG1KWA Monheim am Rhein Batt=4.17V
20260209132537DG1KWA-10>APLRG1,WIDE1-1,qAO,DB0UHC-L4:=L45eP6R*& !GLoRa iGATE & Digi, DG1KWA Monheim am Rhein Batt=4.20V