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
20250715204936	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=970
20250715212000	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=969
20250715215024	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=970
20250715222048	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=969
20250715225112	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=970
20250715232136	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=970
20250715235200	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=970
20250716002224	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=969
20250716005248	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=969
20250716012311	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=969
20250716015335	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=43% P=969
20250716022359	YO8RBY-1>AESPG4,TCPIP*,qAC,T2ROMANIA:=4657.59N/02623.20E_8266/NANO T=30° H=42% P=969