APRS Packet Errors for PD1JRN-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
20260208144918PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208150326PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208151618PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208152823PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208154130PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208155401PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208160703PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208162128PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208163531PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208164903PD1JRN-10>APRX29,TCPIP*,qAC,T2CSNGRAD:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208165029PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208170424PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208171724PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208172924PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208174154PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208175404PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208180751PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208182233PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208183602PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208184838PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208190049PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208191328PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208192815PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208194123PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208195539PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208201028PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208202305PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden
20260208203659PD1JRN-10>APRX29,TCPIP*,qAC,T2NL:!5207.95NR00525.92E&PHG11300/RX iGate Leusden