APRS Packet Errors for OE5HWN-12 (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
20260209132329OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209135344OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209142359OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209145418OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209152433OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209155448OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209162503OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209165521OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209172536OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209175551OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209182606OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899
20260209185625OE5HWN-12>APRSGW,TCPIP*,qAR,OE5HWN-12:!4814.87N/01415.45E#OE5HWN GW#Helmut/B=100/A=000899