No, there does not appear a way see exactly when a timer when will run next. `systemd` offers `systemctl list-timers` and `systemctl status something.timer`, but those don't show the affect of `AccuracySec=` and possibly other directives that shift the time.

If you set `AccuracySec=1h` on two servers, they will both report that the same timer on both servers will fire at the exact same time, but in fact they could start up to an hour apart!  If you are interested to know if two randomized timers might collide, there appears to be no way to check the final calculated run time to find out.

There is a [systemd issue open](https://github.com/systemd/systemd/issues/12192) to make the output of list-timers more accurate / less confusing.