APRS Packet Errors for DL4OCE-3 (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
20260208163104DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.19E#Meshcom v4.35k#DL4OCE-3/B=013/A=000364
20260208170115DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.18E#Meshcom v4.35k#DL4OCE-3/B=100/A=000381
20260208173130DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.18E#Meshcom v4.35k#DL4OCE-3/B=094/A=000374
20260208180145DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.18E#Meshcom v4.35k#DL4OCE-3/B=006/A=000371
20260208183202DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.19E#Meshcom v4.35k#DL4OCE-3/B=008/A=000367
20260208190217DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.18E#Meshcom v4.35k#DL4OCE-3/B=047/A=000381
20260208193232DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.18E#Meshcom v4.35k#DL4OCE-3/B=003/A=000374
20260208200247DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.18E#Meshcom v4.35k#DL4OCE-3/A=000374
20260208203301DL4OCE-3>APRSGW,TCPIP*,qAR,DL4OCE-3:!5213.42N/01015.18E#Meshcom v4.35k#DL4OCE-3/B=009/A=000397