APRS Packet Errors for VK2XSO-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
20260209104336VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209111318VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209114301VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209121242VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209124225VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209131207VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209134149VK2XSO-3>APNU3B,VK2RAP-3*,WIDE2-1,qAO,VK4VS-1:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209141131VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209144115VK2XSO-3>APNU3B,VK2QJ-1*,WIDE2-1,qAO,VK2VU-1:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209151055VK2XSO-3>APNU3B,VK2RAP-3*,WIDE2-1,qAO,VK4VS-1:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209152007VK2XSO-3>APNU3B,qAO,VK4VS-1:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209154038VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND
20260209161020VK2XSO-3>APNU3B,VK2RNW-1*,qAR,VK2YGV-5:!3000.48S/15141.63E# APRS DIGI BEN LOMOND