APRS Packet Errors for SM0RVV-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
20260209101211SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=087/A=000180
20260209104226SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=070/A=000180
20260209111241SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=070/A=000180
20260209114256SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=079/A=000180
20260209121311SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=077/A=000180
20260209124324SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=087/A=000180
20260209131339SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=067/A=000180
20260209134354SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=069/A=000180
20260209141409SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=073/A=000180
20260209144424SM0RVV-2>APRSGW,TCPIP*,qAR,SM0RVV-2:!5923.98N/01752.20E#MeshComm 4.0#SM0RVV MC GW/B=086/A=000180