APRS Packet Errors for DO2SCH-9 (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
20260208132859	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208135914	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208142929	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208145944	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208152957	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208160008	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208163023	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208170038	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208173053	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208180108	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208183127	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348
20260208190142	DO2SCH-9>APRSGW,TCPIP*,qAR,DO2SCH-9:!5056.31N/00658.72E#/B=095/A=000348