APRS Packet Errors for EW8838 (last 168 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
20261028023122	EW8838>APRS,TCPXX*,qAX,CWOP-3:@280231z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31
20261028024122	EW8838>APRS,TCPXX*,qAX,CWOP-6:@280241z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31
20261028025122	EW8838>APRS,TCPXX*,qAX,CWOP-6:@280251z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31
20261028030122	EW8838>APRS,TCPXX*,qAX,CWOP-5:@280301z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31
20261028031122	EW8838>APRS,TCPXX*,qAX,CWOP-6:@280311z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31
20261028032122	EW8838>APRS,TCPXX*,qAX,CWOP-3:@280321z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31
20261028033143	EW8838>APRS,TCPXX*,qAX,CWOP-5:@280331z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31
20261028034143	EW8838>APRS,TCPXX*,qAX,CWOP-7:@280341z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31
20261028035143	EW8838>APRS,TCPXX*,qAX,CWOP-7:@280351z3735.59N/12229.13W_327/NaNg000t058r000p000P000h80b10176 VISR3933 31