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
20260208132122DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208135140DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208142155DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208145211DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208152226DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208155244DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208162259DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208165314DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208172329DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208175347DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208182402DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030
20260208185417DG4XW-12>APRSGW,TCPIP*,qAR,DG4XW-12:!5328.37N/00941.70E#under test#Pepe/B=100/A=000030