APRS Packet Errors for DO3HUM-12 (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
20260208132515	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208135516	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208142517	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208145518	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208152519	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208155520	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208162521	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208165522	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208172523	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208175524	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208182525	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate
20260208185526	DO3HUM-12>APX216,TCPIP*,qAC,T2ERFURT:=5129.40N/01202.58E-Xastir auf RPi4 + LoRa-Igate