APRS Packet Errors for DG0OL-99 (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
20260208132036DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=023/A=001142
20260208135054DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=071/A=001142
20260208142109DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=008/A=001142
20260208145124DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=068/A=001142
20260208152139DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=051/A=001142
20260208155157DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=100/A=001142
20260208162212DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=100/A=001142
20260208165227DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=010/A=001142
20260208172242DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=100/A=001142
20260208175301DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=100/A=001142
20260208182316DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=100/A=001142
20260208185331DG0OL-99>APRSGW,TCPIP*,qAR,DG0OL-99:!5051.38N/01112.15E#Meshcom GW#Tom/B=068/A=001142