APRS Packet Errors for DB0NMS-S (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
20250830192020	DB0NMS-S>APJIO4,TCPIP,qAC,DB0NMS-GS:;DB0NMS B 292036z . ND . EaRNG0012 440 Voice 439.750 -9.40 MHz
20250830194020	DB0NMS-S>APJIO4,TCPIP,qAC,DB0NMS-GS:;DB0NMS B 292036z . ND . EaRNG0012 440 Voice 439.750 -9.40 MHz
20250830222020	DB0NMS-S>APJIO4,TCPIP,qAC,DB0NMS-GS:;DB0NMS B 292036z . ND . EaRNG0012 440 Voice 439.750 -9.40 MHz
20250830224020	DB0NMS-S>APJIO4,TCPIP,qAC,DB0NMS-GS:;DB0NMS B 292036z . ND . EaRNG0012 440 Voice 439.750 -9.40 MHz
20250830230020	DB0NMS-S>APJIO4,TCPIP,qAC,DB0NMS-GS:;DB0NMS B 292036z . ND . EaRNG0012 440 Voice 439.750 -9.40 MHz