APRS Packet Errors for 2E0DNW (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
20250728212948	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250728215949	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250728222948	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250728225949	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250728232949	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250728235949	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250729002949	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250729005949	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250729012950	2E0DNW>BEACON,TCPIP*,qAC,SEVENTH:!0000.00S/00000.00E&73. IGATE2 App.
20250729015950	2E0DNW>BEACON,TCPIP*,qAC,NINTH:!0000.00S/00000.00E&73. IGATE2 App.
20250729022950	2E0DNW>BEACON,TCPIP*,qAC,NINTH:!0000.00S/00000.00E&73. IGATE2 App.
20250729025950	2E0DNW>BEACON,TCPIP*,qAC,NINTH:!0000.00S/00000.00E&73. IGATE2 App.