APRS Packet Errors for DL3APY-3 (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
20260423211459	DL3APY-3>APRS,QB9N6,qAO,DB0THA-10:!5103.46N/01114.66E_225/00 g...t045r000p...P...h100b10327 Lux:0 WX-Berlstedt
20260423211608	DL3APY-3>APRS,QB9N7,qAO,DB0THA-10:!5103.46N/01114.66E_270/00 g...t045r000p...P...h100b10327 Lux:0 WX-Berlstedt
20260423211716	DL3APY-3>APRS,QB9N6,qAO,DB0THA-10:!5103.46N/01114.66E_270/00 g...t045r000p...P...h100b10327 Lux:0 WX-Berlstedt
20260423212407	DL3APY-3>APRS,QB8N5,qAO,DB0THA-10:!5103.46N/01114.66E_045/00 g...t045r000p...P...h100b10327 Lux:0 WX-Berlstedt
20260423212950	DL3APY-3>APRS,QB9N6,qAO,DB0THA-10:!5103.46N/01114.66E_180/00 g...t044r000p...P...h100b10328 Lux:0 WX-Berlstedt
20260423213058	DL3APY-3>APRS,QB6N3,qAO,DB0THA-10:!5103.46N/01114.66E_225/00 g...t044r000p...P...h100b10328 Lux:0 WX-Berlstedt
20260423213207	DL3APY-3>APRS,QB8N5,qAO,DB0THA-10:!5103.46N/01114.66E_270/00 g...t044r000p...P...h100b10327 Lux:0 WX-Berlstedt
20260423215023	DL3APY-3>APRS,QB7N5,qAO,DB0THA-10:!5103.46N/01114.66E_225/00 g...t045r000p...P...h100b10326 Lux:0 WX-Berlstedt
20260423215131	DL3APY-3>APRS,QB6N3,qAO,DB0THA-10:!5103.46N/01114.66E_270/00 g...t045r000p...P...h100b10326 Lux:0 WX-Berlstedt