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
20260529130806	SV2JT-2>APLRG1,TCPIP*,qAC,T2CHILE:!/9z`PT<)4_ G.../...g...t083h34b10174LoRa APRS WX N. Krini
20260529132306	SV2JT-2>APLRG1,TCPIP*,qAC,T2CHILE:!/9z`PT<)4_ G.../...g...t083h35b10173LoRa APRS WX N. Krini
20260529133806	SV2JT-2>APLRG1,TCPIP*,qAC,T2CHILE:!/9z`PT<)4_ G.../...g...t083h37b10174LoRa APRS WX N. Krini
20260529150806	SV2JT-2>APLRG1,TCPIP*,qAC,T2CHILE:!/9z`PT<)4_ G.../...g...t082h43b10176LoRa APRS WX N. Krini
20260529152306	SV2JT-2>APLRG1,TCPIP*,qAC,T2CHILE:!/9z`PT<)4_ G.../...g...t082h43b10177LoRa APRS WX N. Krini