APRS Packet Errors for YO4ESB-4 (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
20260208150812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208153812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208160812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208163812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208170812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208173812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208180812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208183812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208190812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208193812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208200812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR
20260208203812	YO4ESB-4>APDW14,TCPIP*,qAC,T2KOBLENZ:!4412.09NS02837.48E#PHG0440RPi4 UHF igate via SDR