When receiving GPS signals you have a very accurate universal time reference. Would that not be used to stamp the ADS-B output meaning received order would not be limiting?
Remember that the data stream is from multiple receivers with different (and non-constant) latencies to the server. So occasionally packets may arrive at the server in a different order from when they were originally transmitted.
It follows that if one tries to use those unreliable timestamps to derive second-order parameters, it's asking for trouble, as in that absurd "33,000 ft/min" climb rate that several posters have quoted.
It's trivial to show that the last ~ 16 packets were not affected by reordering and that the max likely timestamp error for any packet would be 0.4 seconds.
Even if we conservatively
double the possible timestamp error, the bounds for vertical rate for the last few data points is still between 17,000 fpm and 30,000 fpm. Not physically realistic.
And even if we ignore the timestamps completely, we also have space constraints. The lat/long and altitude data shows the aircraft climbing at least 500 ft in altitude in about 350 ft horizontal distance (conservatively assuming 50 ft of ADS-B altitude errors due to granularity).
That means the aircraft achieved a 55 degree up vertical flight path in less than twice the aircraft's on length. Again not physically realistic.