APRS Packet Errors for YO8RBY-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
20261120115903YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=37% P=958
20261120122927YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=37% P=959
20261120125951YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=37% P=959
20261120133014YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=37% P=960
20261120140038YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=37% P=961
20261120143102YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=37% P=961
20261120150126YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=38% P=961
20261120153150YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=38% P=962
20261120160214YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=38% P=962
20261120163238YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=25° H=39% P=962
20261120170302YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=37% P=963
20261120173326YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=37% P=963