APRS Packet Errors for DL1RI-15 (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
20260209133521DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209140532DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209143547DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209150602DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209153619DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209160634DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209163649DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209170704DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209173723DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209180738DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209183749DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440
20260209190804DL1RI-15>APRSGW,TCPIP*,qAR,DL1RI-15:!5040.60N/00913.65E&EmCom-LoRa-Mesh/B=100/A=001440