APRS Packet Errors for SV2BBO-15 (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
20250806114104	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t080h35b10104LoRa APRS WX Plateia
20250806115605	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h38b10104LoRa APRS WX Plateia
20250806121105	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h41b10104LoRa APRS WX Plateia
20250806122605	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h41b10100LoRa APRS WX Plateia
20250806124105	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h42b10099LoRa APRS WX Plateia
20250806125605	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h42b10097LoRa APRS WX Plateia
20250806131105	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h42b10096LoRa APRS WX Plateia
20250806132605	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h43b10095LoRa APRS WX Plateia
20250806134105	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h43b10095LoRa APRS WX Plateia
20250806135605	SV2BBO-15>APLRG1,TCPIP*,qAC,T2CHILE:!/9wkFTD{=_ G.../...g...t082h43b10095LoRa APRS WX Plateia