APRS Packet Errors for DB0TGO-10 (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
20260208150324DB0TGO-10>APRX29,WIDE1-1,qAO,DB0TA-L:!5234.18NT01313.92E&144.8/432.5/433.775MHz X-Band-iGate.APRX
20260208150331DB0TGO-10>WXTGOL,WIDE1-1,qAO,DB0TA-L:@081503z5234.18N/01313.92E_022/003g006t033r000p002P000h94b10144GLÄTTE FROST
20260208155306DB0TGO-10>APRX29,WIDE1-1,qAO,DB0TA-L:!5234.18NT01313.92E&144.8/432.5/433.775MHz X-Band-iGate.APRX
20260208165014DB0TGO-10>APRX29,WIDE1-1,qAO,DB0AVH-10:!5234.18NT01313.92E&144.8/432.5/433.775MHz X-Band-iGate.APRX
20260208165021DB0TGO-10>WXTGOL,WIDE1-1,qAO,DB0TA-L:@081650z5234.18N/01313.92E_000/000g001t032r000p000P000h97b10150GLÄTTE FROST
20260208173749DB0TGO-10>APRX29,WIDE1-1,qAO,DB0TA-L:!5234.18NT01313.92E&144.8/432.5/433.775MHz X-Band-iGate.APRX
20260208183614DB0TGO-10>APRX29,WIDE1-1,qAO,DB0TA-L:!5234.18NT01313.92E&144.8/432.5/433.775MHz X-Band-iGate.APRX
20260208192726DB0TGO-10>WXTGOL,WIDE1-1,qAO,DD6VD-10:@081927z5234.18N/01313.92E_022/001g002t032r000p000P000h98b10154GLÄTTE FROST
20260208201619DB0TGO-10>APRX29,WIDE1-1,qAO,DD6VD-10:!5234.18NT01313.92E&144.8/432.5/433.775MHz X-Band-iGate.APRX
20260208201626DB0TGO-10>WXTGOL,WIDE1-1,qAO,DD6VD-10:@082016z5234.18N/01313.92E_090/002g005t032r000p000P000h96b10154GLÄTTE FROST