APRS Packet Errors for DK4ARL (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
20260209130740DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09712selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209132235DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09711selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209133730DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09710selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209135225DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09709selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209140710DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09708selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209142205DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09707selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209143700DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t039r000p000P000h..b09707selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209145155DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t039r000p000P000h..b09706selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209150650DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09706selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209152144DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t039r000p000P000h..b09706selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209153638DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t039r000p000P000h..b09706selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209155133DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09706selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209160627DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t040r000p000P000h..b09706selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209162121DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t039r000p000P000h..b09705selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209163615DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t038r000p000P000h..b09705selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209165108DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t037r000p000P000h..b09704selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209172054DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t037r000p000P000h..b09702selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209175037DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t037r000p000P000h..b09701selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209180528DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t037r000p000P000h..b09700selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209182019DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t036r000p000P000h..b09699selfmade using TTGO LoRa32 with MCP9801 and BMP280
20260209184959DK4ARL>APRS,WIDE1-1,qAR,DK4ARL-10:!4900.36N/00930.46E_.../...g...t034r000p000P000h..b09697selfmade using TTGO LoRa32 with MCP9801 and BMP280