APRS Packet Errors for S56LLB-2 (last 24 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
20241121182512S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@182510h4634.87N1607.200)124/000Testiram DMR APRS cr
20241121183849S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@183847h434.882N1607.21E)124/000Testiram DMR APRS cr
20241121184034S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@184032h44.8784N1607.21E)000/000Testiram DMR APRS cr
20241121184915S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@184913h44.8797N1607.20E)000/000Testiram DMR APRS cr
20241121185021S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@185019h4634.871607.20E)000/000Testiram DMR APRS cr
20241121201042S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@201040h4634.90N1607.210)124/028Testiram DMR APRS cr
20241121212607S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@212605h4634.89N17.2222E)331/000Testiram DMR APRS cr
20241121220004S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@220002h46.6223N1607.34E)144/000Testiram DMR APRS cr
20241122174325S56LLB-2>APBM1D,S55DLE,DMR*,qAR,S55DLE:@174323h4634.870E0)124/145Testiram DMR APRS cr