Is it possible your API results are simply showing the GMT date?
Pretty sure the API is going to return GMT (Zulu) because all databases require that you render to your locale (whatever that may be).
As far as other mysteries, fields can be set to map a common time for all users in Airtable’s formatting options. I’ll bet that’s why you see the one hour diff on some tests. As such, users in two different time zones could see the same timestamp on a record.

[quote=“Bill.French, post:2, topic:26851”]
Is it possible your API results are simply showing the GMT date?
Pretty sure the API is going to return GMT (Zulu) because all databases require that you render to your locale (whatever that may be).
As far as other mysteries, fields can be set to
I see your point, and I totally agree with the API returning in Zulu.
Ive investigated a bit further to find that
- airtable value “8.10.2019 10:00” is returned as “2019-10-08T08:00:00.000Z” from API, and
- airtable value “10.1.2020 10:00” is returned as “2020-01-10T09:00:00.000Z” from API.
I can slighty see why now, but not really sure. The first is GMT+2, the latter GMT+1.
Switching the GMT flag does the trick though, thats what I needed all along! Thanks!