APRS Packet Errors for YH3NPX-9 (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
20251008220033	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251008223033	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251008224033	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251008235032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009000032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009003032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009011032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009021032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009024032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009025032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009030032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009033032	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater
20251009034031	YH3NPX-9>AP3BVG,DAPRS1*,qAR,YH3NPX-4:!8.0950S/114.2180E#BANYUWANGI Digipeater