APRS Packet Errors for N4RRS-1 (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
20260208164842N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.45WZ/A=000565PinPoint v2.1
20260208171842N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.45WZ/A=000568PinPoint v2.1
20260208174843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.44WZ/A=000569PinPoint v2.1
20260208181843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.45WZ/A=000531PinPoint v2.1
20260208184843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.45WZ/A=000548PinPoint v2.1
20260208191843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.45WZ/A=000571PinPoint v2.1
20260208194843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.45WZ/A=000559PinPoint v2.1
20260208201843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.61N/08727.45WZ/A=000554PinPoint v2.1
20260208204843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.45WZ/A=000557PinPoint v2.1
20260208211843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.45WZ/A=000546PinPoint v2.1
20260208214843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.60N/08727.44WZ/A=000572PinPoint v2.1
20260208221843N4RRS-1>APIN21,TCPIP*,qAC,T2USANE:!3637.61N/08727.44WZ/A=000558PinPoint v2.1