I noticed strance behaviour under WolframCloud when using DateString with DateObject having TimeZone set.

I run same DateString operation for three different DateObject instances where first two of them produces expected result i.e. current date and time in Finnish. However the third one where I have explicitly set TimeZone to correct one, I am getting totally wrong result for the time:

DateString[#, <|"Elements"->"LocaleDateTimeShort", "Language"->"Finnish"|>]& /@
{
  DateObject[],
  DateObject[TimeZone->None],
  DateObject[TimeZone->"Europe/Helsinki"]
}

Output:

{16.8.2025 klo 13.29.48,16.8.2025 klo 13.29.48,16.8.2025 klo 21.29.48}

As seen in the output the last member have time totally incorrect 21.29.48 when correct time would be 13.29.48 so that would be several hour off. But this happens only in WolframCloud and not in the desktop version.

I am not sure if this is a bug or if I am just not understand the meaning of TimeZone correctly in this context.