APRS Packet Errors for N2XP-2 (last 24 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
20180618111552N2XP-2>APTW14,TOMRVR,WIDE1*,WIDE2-1,qAR,W3OI:_06180717c@@`f@殒d@}WLNK-1>APWLK,TCPIP,W3OI*::AA3JY-2 :vice Mount Holly NJ 357 AM EDT Mon Jun 18 2018 SYNOPSIS... High{1629
20180618131200N2XP-2>APTW14,TOMRVR,WIDE1,K3TU,WIDE2*,qAR,W3OI:_061809=}440.106MHz Toff +500 South Region Medical Coordination Ce@c=4013.01NI07529.01W&PHG74604/SEPA DIGI FN20gf
20180618153710N2XP-2>APTW14,TOMRVR,WIDE1,KB2EAR-1,WIDE2*,qAR,W3OI:!3958.92N/0707421.51Ww>T+096F-013V053 FloodAdvisor -02
20180618212804N2XP-2>APTW14,TOMRVR,WIDE1,KB2EAR-1,WIDE2*,qAR,W3OI:_06181729c2@@殒d@NOBARC.org // K2LM@nycap.rr.com // N1ATP.com