APRS Packet Errors for IU2VSE-7 (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
20260228181643	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228181745	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228181845	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228181946	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228182047	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228182148	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228182249	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228182350	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228182451	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228182704	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228190005	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000
20260228190110	IU2VSE-7>APAT81,WIDE1-1,qAO,IW2EJH-12:!0000.00N/00000.00E//A=000000