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
20251123013507	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10220.29N/0006.55E>000/123/A=00851 384.01V -88dBm 7.5dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251123034622	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10220.29N/0006.55E>000/019/A=00854 384.01V -86dBm 7.0dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251123034724	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10220.29N/0006.55E>000/019/A=00854 384.01V -86dBm 7.5dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251123034828	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10140.97N/0006.55E>000/019/A=00854 384.01V -89dBm -2.5dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251123034930	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10220.29N/0006.55E>000/019/A=00854 384.01V -87dBm 10.0dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251123035033	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10140.97N/0006.55E>000/019/A=00854 384.01V -87dBm 7.3dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251123035551	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10220.29N/0006.55E>000/004/A=00854 384.01V -89dBm 9.3dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc
20251123050605	ZS6RVC-27>APZLRW,TCPIP*,qAS,ZS6RVC:=10220.29N/0006.55E>000/003/A=00854 384.01V -83dBm 7.0dB SF7 LoRaWAN Tracker mami-co-za-jhb-nc