APRS Packet Errors for DG4XW-12 (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
20260209133356DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209140412DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209143430DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209150445DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209153500DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209160515DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209163533DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209170548DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209173603DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209180618DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209183636DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260209190651DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030