APRS Packet Errors for R3KEE-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
20250530014914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d21:06:27
20250530015914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d21:16:27
20250530020914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d21:26:27
20250530021914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d21:36:27
20250530022914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d21:46:27
20250530023914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d21:56:27
20250530024914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d22:06:27
20250530025914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d22:16:27
20250530030914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d22:26:27
20250530031914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d22:36:27
20250530032914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d22:46:27
20250530033914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d22:56:27
20250530034914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d23:06:27
20250530035914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d23:16:27
20250530040914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d23:26:27
20250530041914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d23:36:27
20250530042914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d23:46:27
20250530043914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w2d23:56:27
20250530044914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d00:06:27
20250530045914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d00:16:27
20250530050914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d00:26:27
20250530051914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d00:36:27
20250530052914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d00:46:27
20250530053914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d00:56:27
20250530054914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d01:06:27
20250530055914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d01:16:27
20250530060914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d01:26:27
20250530061914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d01:36:27
20250530062914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d01:46:27
20250530063914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d01:56:27
20250530064914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d02:06:27
20250530065914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d02:16:27
20250530070914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d02:26:27
20250530071914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d02:36:27
20250530072914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d02:46:27
20250530073914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 25w3d02:56:27