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
20251223165020	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=39% P=976
20251223172043	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=976
20251223175107	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=976
20251223182131	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=976
20251223185155	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=977
20251223192219	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=977
20251223195243	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=977
20251223202307	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=977
20251223205331	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=977
20251223212355	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=977
20251223215419	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=977
20251223222443	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=26° H=40% P=977