APRS Packet Errors for DL2MT-13 (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
20220928160604DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t059r002p...P...h55b09993LoRa WX in Norden
20220928161119DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t059r002p...P...h55b09994LoRa WX in Norden
20220928162149DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t059r002p...P...h57b09994LoRa WX in Norden
20220928162705DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t059r002p...P...h57b09994LoRa WX in Norden
20220928163736DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t058r002p...P...h59b09996LoRa WX in Norden
20220928170352DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t057r000p...P...h63b09997LoRa WX in Norden
20220928170908DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t056r000p...P...h65b09997LoRa WX in Norden
20220928171939DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t056r001p...P...h65b09997LoRa WX in Norden
20220928173525DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t056r001p...P...h66b09997LoRa WX in Norden
20220928175111DL2MT-13>APRS,qAO,DC6BV-10:!5335.13N/00712.99E_.../00 g...t055r001p...P...h68b09997LoRa WX in Norden