APRS Packet Errors for DL2NEQ-1 (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
20260209091032DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209094047DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209101102DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209104121DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209111136DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209114147DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209121202DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209124217DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209131232DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209134247DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209141302DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427
20260209144317DL2NEQ-1>APRSGW,TCPIP*,qAR,DL2NEQ-1:!4932.21N/01046.39E#/B=100/A=001427