APRS Packet Errors for DB0WAI-11 (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
20260208133153DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208140157DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208143202DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208150207DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208153207DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208153834DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208160837DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208163837DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208170842DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208173847DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208180847DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208183852DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate
20260208190852DB0WAI-11>APOTW1,TCPIP*,qAC,T2CSNGRAD:!4806.89NL01133.37E&PHG0000Lora iGate