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
20190325185949ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260003z4553.81S/17023.70E-QTH
20190325190009ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260003z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325192948ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260003z4553.81S/17023.70E-QTH
20190325193008ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260003z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325195946ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260103z4553.81S/17023.70E-QTH
20190325200006ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260103z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325202945ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260103z4553.81S/17023.70E-QTH
20190325203005ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260103z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325205944ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260203z4553.81S/17023.70E-QTH
20190325210004ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260203z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325212943ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260203z4553.81S/17023.70E-QTH
20190325213003ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260203z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325215942ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260303z4553.81S/17023.70E-QTH
20190325220002ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260303z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325222941ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260303z4553.81S/17023.70E-QTH
20190325223001ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260303z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325225940ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260403z4553.81S/17023.70E-QTH
20190325230000ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260403z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325232940ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260403z4553.81S/17023.70E-QTH
20190325233000ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260403z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190325235939ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260503z4553.81S/17023.70E-QTH
20190325235959ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260503z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326002937ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/260503z4553.81S/17023.70E-QTH
20190326002957ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*260503z4553.81SO17023.70E&146.650MHz : NODE OFFLINE