APRS Packet Errors for DG3FBL-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
20251215132301	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%8%S\|
20251215143803	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%=%S\|
20251215152306	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%@%S\|
20251215153804	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%A%S\|
20251215155306	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%B%S\|
20251215160805	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%C%S\|
20251215162306	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%D%S\|
20251215163805	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%E%S\|
20251215165306	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%F%S\|
20251215170806	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%G%S\|
20251215172306	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%H%S\|
20251215173806	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%I%S\|
20251215180807	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%K%S\|
20251215182307	DG3FBL-15>APLRG1,TCPIP*,qAC,T2PERTH:!Jochen Z05 (im Bus)\|%L%S\|