APRS Packet Errors for YO2LIS-13 (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
20260209092229	YO2LIS-13>APLOX1,TCPIP*,qAC,T2ROMANIA:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.71V,
20260209092529	YO2LIS-13>APLOX1,WIDE1-1,WIDE2-2,qAR,YO2B-10:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.71V,
20260209102229	YO2LIS-13>APLOX1,TCPIP*,qAC,T2ROMANIA:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.65V,
20260209103043	YO2LIS-13>APLOX1,WIDE1-1,WIDE2-2,qAR,YO2B-10:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.65V,
20260209112230	YO2LIS-13>APLOX1,TCPIP*,qAC,T2ROMANIA:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.68V,
20260209122230	YO2LIS-13>APLOX1,TCPIP*,qAC,T2ROMANIA:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.58V,
20260209132230	YO2LIS-13>APLOX1,TCPIP*,qAC,T2ROMANIA:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.48V,
20260209132330	YO2LIS-13>APLOX1,WIDE1-1,WIDE2-2,qAR,YO2B-10:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.48V,
20260209142230	YO2LIS-13>APLOX1,TCPIP*,qAC,T2ROMANIA:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.75V,
20260209143953	YO2LIS-13>APLOX1,WIDE1-1,WIDE2-2,qAR,YO2MD-11:=4601.24NL02122.00E&0.1w ant.5db alt.12m Firiteaz Batt=4.56V,