My starting point was the .log CSV text file that the dash board saves in the folder specified under the Dashboard Settings | Files Tab.
Mine (on Windows XP) is C:\Documents and Settings\MY_USER_NAME\Local Settings\Application Data\FUNcube-1\
[That "Local Settings" folder is hidden by default, but so many programs store stuff there that I unhid it many years ago ].
In there, you will find a file for each time Dashboard was started and stopped. Anything that is 1k is likely to be the headers only and can probably be ignored. Each successfully decoded frame is listed in the log file, The overall file format is not ideal but the info is there.
Using the UTC of a decoded frame, I used Orbitron, in simulation mode for that UTC, to work out the parameters of the whole pass, and the duration above the horizon in seconds and hence the absolute max number of frames available . I then looked at the time of the first and last successful decodes and used Orbitron to work out the Az and El at those frames. I subtracted the time of those frames to give a duration, in seconds, between first and last decode, divided by 5, and rounded up to get the total frames I should / could definitely have decoded (if elevation was the only issue and there was no fading, which there is of course).
So in detail
Date Time 04/12/2013 10:31 - Approximate start of pass from log file and Orbitron
Duration 720 Secs - Pass Duration - 0deg to 0deg from Orbitron
Avail Frames 145 - Duration / 5 rounded up
First to Last Decode Time 274 Secs - From Log File Times of decoded frames on this pass
High Elevation Frames 55 - First to last decode seconds divided by 5 and rounded up - "High Elevation" is not the best term, but it applies my case!
Actual Decodes 34 - Simple manual count of decodes in log file
PerCent Decode Total / High Angle 23/63 - Percent of (Actual Decodes / Avail) and (Actual Decodes / High Elevation)
Elv/Az of First Decode 32.7/70.9 - From Orbitron using time of first decode
Elv/Az of Last Decode 10.7/163.4 - From Orbitron using time of last decode
Hope that helps, Paul. It was largely a manual process with a little spreadsheet help. I feel a programming project coming on. (So many possibilities, so little time).