APRS Packet Errors for SV2JT-2 (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
20261011122954	SV2JT-2>APLRG1,TCPIP*,qAC,T2SPAIN:!/9z`PT<)4_ G.../...g...t076h58b10087LoRa APRS WX N. Krini
20261011124454	SV2JT-2>APLRG1,TCPIP*,qAC,T2SPAIN:!/9z`PT<)4_ G.../...g...t076h57b10085LoRa APRS WX N. Krini
20261011125954	SV2JT-2>APLRG1,TCPIP*,qAC,T2SPAIN:!/9z`PT<)4_ G.../...g...t076h58b10088LoRa APRS WX N. Krini
20261011131454	SV2JT-2>APLRG1,TCPIP*,qAC,T2SPAIN:!/9z`PT<)4_ G.../...g...t076h57b10084LoRa APRS WX N. Krini
20261011132954	SV2JT-2>APLRG1,TCPIP*,qAC,T2SPAIN:!/9z`PT<)4_ G.../...g...t076h57b10083LoRa APRS WX N. Krini
20261011134454	SV2JT-2>APLRG1,TCPIP*,qAC,T2SPAIN:!/9z`PT<)4_ G.../...g...t076h57b10083LoRa APRS WX N. Krini
20261011135954	SV2JT-2>APLRG1,TCPIP*,qAC,T2SPAIN:!/9z`PT<)4_ G.../...g...t075h58b10084LoRa APRS WX N. Krini
20261011141509	SV2JT-2>APLRG1,TCPIP*,qAC,T2SPAIN:!/9z`PT<)4_ G.../...g...t075h58b10084LoRa APRS WX N. Krini
20261011180328	SV2JT-2>APLRG1,TCPIP*,qAC,T2TAS:!/9z`PT<)4_ G.../...g...t075h57b10085LoRa APRS WX N. Krini