APRS Packet Errors for DB0HSK-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
20260208150329DB0HSK-10>APGE01,qAR,DB0BI-10:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208153340DB0HSK-10>APGE01,TCPIP*,qAC,T2KA:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208160340DB0HSK-10>APGE01,TCPIP*,qAC,T2KA:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208163329DB0HSK-10>APGE01,qAR,DG4DAA-13:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208170340DB0HSK-10>APGE01,TCPIP*,qAC,T2KA:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208173340DB0HSK-10>APGE01,TCPIP*,qAC,T2KA:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208180329DB0HSK-10>APGE01,qAR,DB0BI-10:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208183329DB0HSK-10>APGE01,qAR,DB0BI-10:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208190329DB0HSK-10>APGE01,qAR,DB0BI-10:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208193329DB0HSK-10>APGE01,qAR,DB0BI-10:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208200329DB0HSK-10>APGE01,qAR,DB0BI-10:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm
20260208203329DB0HSK-10>APGE01,qAR,DB0BI-10:!5123.19N/00817.29E&DB0HSK RX-Only iGate Stimmstamm