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
20261014073914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d02:53:52
20261014074914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d03:03:52
20261014075914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d03:13:52
20261014081914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d03:33:52
20261014082913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d03:43:52
20261014083914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d03:53:52
20261014084914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d04:03:52
20261014085913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d04:13:52
20261014090914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d04:23:52
20261014091914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d04:33:52
20261014092913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d04:43:52
20261014093914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d04:53:52
20261014094913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d05:03:52
20261014095913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d05:13:52
20261014100914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d05:23:52
20261014101913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d05:33:52
20261014102913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d05:43:52
20261014103914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d05:53:52
20261014104914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d06:03:52
20261014105914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d06:13:52
20261014110914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d06:23:52
20261014111913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d06:33:52
20261014112914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d06:43:52
20261014113913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d06:53:52
20261014114913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d07:03:52
20261014115913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d07:13:52
20261014120913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d07:23:52
20261014121914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d07:33:52
20261014122914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d07:43:52
20261014123913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d07:53:52
20261014124913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d08:03:52
20261014125913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d08:13:52
20261014130914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d08:23:52
20261014131913	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d08:33:52
20261014132914	R3KEE-1>APRS,TCPIP,qAO,R3KEE:=5118.53N912.15E-145.500MHz \| http://r3kee.ru \| Mikrotik \| upTime 2w6d08:43:52