60fps can be ok at night (with some work on the firmware) but all things being equal I think 30fps is still going to have an advantage
30fps can only give an advantage if you take advantage of the extra time available which allows a longer exposure. However longer exposure = more motion blur, and on a dashcam motion blur is normally a negative.
If I'm making a movie to be played at 30fps then having some motion blur is good, it smooths the movement between frames so that you don't notice the 30fps frame updates, so a movie camera should use low shutter speeds, but for a dashcam you want fast shutter speeds to remove the motion blur from plates.
So it is a bit odd that my dashcams use 30fps and have a lot of motion blur in the dark while my movie (action) cam uses 60fps with low motion blur, and has much more readable plates!
Filmed this on the A129 Pro prototype at 9:05 PM on a cloudy night, movement between frames is nicely blurred, ideal for movies, and much better than the Gitup Git2 action camera that I used for the sound and which had almost no motion blur at 60fps and had numbers that were clearly readable, while they are totally unreadable on the A129 video. But the A129 is a dashcam, it should capture those numbers, while the Gitup Git2 is my movie camera which i want some nice blur from, they are the wrong way around!
On a positive, the A129 Pro did manage to make things look almost like a cloudy midday rather than a cloudy 9:05 PM, would be hard to tell it wasn't midday if it wasn't for the blinding LED headlights and the cab full of flames - driver must have been a bit hot! The Gitup Git2 video on the other hand is dark and blurry, quite poor quality, but I can read the engine number from it!
So, it is a compromise, quality v readability, but I'm still not convince my dashcam and action camera are the right way around!
(No, it wasn't mounted on a drone, I was just playing with the zoom control!)