That is definitely a display bug on our side - nice catch! Please log a support case for that. In the meantime, you can find the real value e.g. here:
↧