APRS Packet Errors for WD1O-15 (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
20260208183130WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@183130h4358.60N/06915.36W/APRS-IS for Win32
20260208190131WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@190130h4358.60N/06915.36W/APRS-IS for Win32
20260208193132WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@193131h4358.60N/06915.36W/APRS-IS for Win32
20260208200133WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@200132h4358.60N/06915.36W/APRS-IS for Win32
20260208203133WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@203133h4358.60N/06915.36W/APRS-IS for Win32
20260208210133WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@210133h4358.60N/06915.36W/APRS-IS for Win32
20260208213134WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@213134h4358.60N/06915.36W/APRS-IS for Win32
20260208220134WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@220134h4358.60N/06915.36W/APRS-IS for Win32
20260208223135WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@223134h4358.60N/06915.36W/APRS-IS for Win32
20260208230135WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@230135h4358.60N/06915.36W/APRS-IS for Win32
20260208233136WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@233136h4358.60N/06915.36W/APRS-IS for Win32
20260209000137WD1O-15>APWW11,TCPIP*,qAC,T2ROMANIA:@000136h4358.60N/06915.36W/APRS-IS for Win32