APRS Packet Errors for DL6DBN-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
20260208155216DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.42N/00805.69E#/B=100/A=001375
20260208165241DL6DBN-12>APLT00-1,WIDE1-1,qAO,DB0EIS-10:=/4g$hPR1Y# P[
20260208165249DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.42N/00805.69E#/B=100/A=001375
20260208172301DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.42N/00805.69E#/A=001358
20260208175317DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.42N/00805.69E#/B=007/A=001352
20260208182332DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.43N/00805.69E#/B=100/A=001345
20260208185341DL6DBN-12>APLT00-1,WIDE1-1,qAO,DB0EIS-10:=/4g$hPR1Y# P[
20260208185354DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.42N/00805.69E#/B=004/A=001365
20260208192404DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.44N/00805.68E#/B=011/A=001329
20260208195645DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.42N/00805.69E#/B=001/A=001378
20260208202701DL6DBN-12>APRSMC,TCPIP*,qAR,DL6DBN-10:!5053.42N/00805.69E#/B=001/A=001339