APRS Packet Errors for ZL4DM (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
20190219085810ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191302z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219092809ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191402z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219095808ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191402z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219102807ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191502z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219105806ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191502z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219112805ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191602z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219115804ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191602z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219125802ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191702z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219132801ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191802z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219135800ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191802z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190219142759ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*191902z4553.81SO17023.70E&146.650MHz : NODE OFFLINE