APRS Packet Errors for DB0WT-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
20260209121530	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209124535	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209131536	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209134540	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209141545	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209144550	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209151550	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209154555	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209161600	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209164600	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209171605	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate
20260209174606	DB0WT-10>APOTW1,TCPIP*,qAC,T2SPAIN:!4747.01NL00828.37E&PHG0000Lora iGate