APRS Packet Errors for DV7RAR-7 (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
20250707061556DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707061651DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707063604DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707063659DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707065612DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707065707DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707071710DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707071800DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707073717DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707073807DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707075724DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707075814DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707081731DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707081821DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707083737DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707083828DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707085744DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707085835DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707091751DV7RAR-7>APBPQ1,TCPIP*,qAC,T2HK:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707091842DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707094821DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707094911DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707100829DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TAIPEI:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707100920DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707102910DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TAIPEI:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City
20250707103021DV7RAR-7>APBPQ1,TCPIP*,qAC,T2TOKYO:!09018.7NW023017.4EaBBS & RMS on 144.390 in Dumaguete City