APRS Packet Errors for ZS6RVC-27 (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
20251215145219	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10022.33N/0006.55E>000/003/A=00854 384.01V -78dBm 7.8dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251215145425	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10022.33N/0006.55E>000/018/A=00854 384.01V -81dBm 8.0dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251215145743	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10022.33N/0006.55E>000/123/A=00851 384.01V -81dBm 9.3dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251215145845	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10022.33N/0006.55E>000/123/A=00851 384.01V -78dBm 7.0dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251215145947	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10022.33N/0006.55E>000/123/A=00851 384.01V -81dBm 9.8dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251215180702	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10022.33N/0006.55E>000/123/A=00851 384.01V -88dBm 9.5dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251215180805	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10022.33N/0006.55E>000/123/A=00851 384.01V -89dBm 9.0dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251215180907	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10022.33N/0006.55E>000/123/A=00851 384.01V -87dBm 10.0dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc