APRS Packet Errors for SV3EXY (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
20260208131904SV3EXY>APDR16,TCPIP*,qAC,T2LAUSITZ:=3812.36N2209.29E- 438.600 Mhz
20260208133911SV3EXY>APDR16,TCPIP*,qAC,T2LAUSITZ:=3812.36N2209.29E- 438.600 Mhz
20260208135911SV3EXY>APDR16,TCPIP*,qAC,T2LAUSITZ:=3812.36N2209.29E- 438.600 Mhz
20260208143330SV3EXY>APDR16,TCPIP*,qAC,T2LAUSITZ:=3812.36N2209.29E- 438.600 Mhz
20260208145330SV3EXY>APDR16,TCPIP*,qAC,T2LAUSITZ:=3812.36N2209.29E- 438.600 Mhz
20260208152811SV3EXY>APDR16,TCPIP*,qAC,T2LAUSITZ:=3812.36N2209.29E- 438.600 Mhz
20260208153509SV3EXY>APDR16,TCPIP*,qAC,T2BELGIUM:=3812.36N2209.29E- 438.600 Mhz