APRS Packet Errors for N2VEN-10 (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
20260208150643N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208150646N2VEN-10>APX218,WIDE2-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208153644N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208153647N2VEN-10>APX218,WIDE1-1,qAR,KC2OKG-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208160645N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208160648N2VEN-10>APX218,WIDE2-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208163646N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208163649N2VEN-10>APX218,WIDE1-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208170647N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208170650N2VEN-10>APX218,WIDE2-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208173648N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208173651N2VEN-10>APX218,WIDE1-1,qAR,KC2OKG-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208180649N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208180652N2VEN-10>APX218,WIDE2-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208183650N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208183653N2VEN-10>APX218,WIDE1-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208190651N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208190654N2VEN-10>APX218,WIDE2-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208193652N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208193655N2VEN-10>APX218,WIDE1-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208200653N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208200656N2VEN-10>APX218,WIDE2-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR
20260208203654N2VEN-10>APX218,TCPIP*,qAC,T2TEXAS:=4050.34N7303.78WaLoRa_APRS_iGate-armingville
20260208203657N2VEN-10>APX218,WIDE1-1,qAR,KA2UGZ-10:=4050.34N7303.78WaLoRa_APRS_iGate-armingvilleRRR