APRS Packet Errors for DL1MPK-1 (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
20260208160351DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4808.88N/01120.31E#Meshcom Mobil#Peter, C28/B=100/A=001736
20260208162022DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.32N/01121.54E#Meshcom Mobil#Peter, C28/B=100/A=001473
20260208165544DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.40N/01121.33E#Meshcom Mobil#Peter, C28/B=100/A=001709
20260208172714DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.40N/01121.34E#Meshcom Mobil#Peter, C28/B=100/A=001736
20260208173452DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.38N/01121.37E#Meshcom 4.0#Peter, C28/B=100/A=001647
20260208180511DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.39N/01121.34E#Meshcom 4.0#Peter, C28/B=100/A=001654
20260208182357DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.39N/01121.34E#Meshcom 4.0#Peter, C28/B=100/A=001604
20260208182616DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.38N/01121.36E#Meshcom 4.0#Peter, C28/B=100/A=001611
20260208183032DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.38N/01121.37E#Meshcom 4.0#Peter, C28/B=100/A=001591
20260208190049DL1MPK-1>APRSMC,TCPIP*,qAR,DL1MPK-12:!4810.39N/01121.33E#Meshcom 4.0#Peter, C28/B=100/A=001736