Hah, it's a bit cloudy today, but I'll try it out tomorrow. I'm going to test out all the age() values with and without a fix for the functions inherent to TinyGPS++, and see the changes. Like I said I checked gps.speed.age() and was getting a number like 11 digits wrong, but the webpage says that age() will output the number of milliseconds since it's last gotten new data, but if that works well then I think that may be the way to go.