APRS Packet Errors for PD1XAN-15 (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
20261019133959PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAS,PA3JT-10:!0000.00N/00000.00E>227/055/A=000000PD1XAN/P XANDER
20261019134401PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAS,PA3JT-10:!0000.00N/00000.00E>192/055/A=000000PD1XAN/P XANDER
20261019135041PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAR,PI8RSZ-10:!0000.00N/00000.00E>149/055/A=000000PD1XAN/P XANDER
20261019140303PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAO,PI2BOZ-10:!0000.00N/00000.00E>171/055/A=000000PD1XAN/P XANDER
20261019140504PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAO,PI2BOZ-10:!0000.00N/00000.00E>188/055/A=000000PD1XAN/P XANDER
20261019140705PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAO,PI2BOZ-10:!0000.00N/00000.00E>296/030/A=000000PD1XAN/P XANDER
20261019140917PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAO,PI2BOZ-10:!0000.00N/00000.00E>158/032/A=000000PD1XAN/P XANDER
20261019141118PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAO,PI2BOZ-10:!0000.00N/00000.00E>233/026/A=000000PD1XAN/P XANDER
20261019141525PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAO,PI2BOZ-10:!0000.00N/00000.00E>170/000/A=000000PD1XAN/P XANDER
20261019142329PD1XAN-15>APAT51-15,WIDE1-1,WIDE3-3,qAO,PI2BOZ-10:!0000.00N/00000.00E>055/017/A=000000PD1XAN/P XANDER