APRS Packet Errors for DB0HL (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
20260209091258DB0HL>APRX29,qAO,DL0DWL-10:!5352.40N/01037.83E#Linux-APRS-Digi in JO53HU VHF & Gateway
20260209092729DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209100009DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209103332DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209104830DB0HL>APRX29,qAO,DL0DWL-10:!5352.40N/01037.83E#Linux-APRS-Digi in JO53HU VHF & Gateway
20260209110536DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209113812DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209121527DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209123830DB0HL>APRX29,qAO,DL0DWL-10:!5352.40N/01037.83E#Linux-APRS-Digi in JO53HU VHF & Gateway
20260209125226DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209133110DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209140654DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi
20260209142050DB0HL>APRX29,qAO,DL0DWL-10:!5352.40N/01037.83E#Linux-APRS-Digi in JO53HU VHF & Gateway
20260209144417DB0HL>APRX29,TCPIP*,qAC,T2SYDNEY:!5352.40N/01037.83E#Luebeck-APRS-Digi