APRS Packet Errors for VK5LEX (last 24 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
20260429221337VK5LEX>APRS,TCPIP*,qAC,T2TAS:;VK5ARC *221337z3507.02S/13828.40EY
20260429221338VK5LEX>APRS,TCPIP*,qAC,T2TAS:;VK5RSV *221337z3515.59S/13836.77EREvery Wednesday night club net starting at 8pm on 80m 3.620mhz and then over to the 2M Net on FM 146.675 -600k T91.5 linked to Victor Habor VK5RVH 438.525 -5 T91.5
20260429222913VK5LEX>APRS,TCPIP*,qAC,T2TAS:;VK5ARC *292229z3507.02S/13828.40EY
20260429223322VK5LEX>APRS,TCPIP*,qAC,T2SYDNEY:;VK5ARC *292233z3507.02S/13828.40EY
20260429223426VK5LEX>APRS,TCPIP*,qAC,T2SYDNEY:;VK5ARC *292234z3507.02S/13828.40EY