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
20251114192909	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=28° H=39% P=974
20251114195933	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=28° H=38% P=974
20251114202957	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=28° H=38% P=974
20251114210021	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=28° H=38% P=974
20251114213044	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=27° H=38% P=974
20251114220108	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=27° H=38% P=973
20251114223132	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=27° H=39% P=973
20251114230156	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=39% P=973
20251114233220	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=39% P=973
20251115000244	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=39% P=972
20251115003308	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=39% P=972
20251115010332	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=39% P=972