APRS Packet Errors for M0EGG-2 (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
20260209115019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209120519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209122019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209123519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209125019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209130519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209132019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209133519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209135019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209140519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209142019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209143519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209145019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209150519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209152019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209153519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209155019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209160519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209162019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209163519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209165019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209170519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209172019M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE
20260209173519M0EGG-2>APDW19,TCPIP*,qAC,T2GB:!5135.11NR00029.79E&APRS iGate using DireWolf on RPi+RTL-SDR M0EGG/TA1XE