LDAP timestamp to date (Active Directory)
Active Directory shows logon, password change and account expiry times as long numbers. Paste one to see the date in UTC and your zone.
Loading the tool…
Processing and privacy: The result is calculated inside your browser and your data is not sent to any server.
How to use it
- Enter ldap timestamp and time zone (optional).
- The result appears straight away and updates as you edit.
- Copy the result, or copy a link that keeps the same values to share it.
How it is calculated
The value counts 100-nanosecond intervals since 1601-01-01 00:00:00 UTC. Unix seconds = (value / 10000000) - 11644473600.
Example
Inputs: LDAP timestamp = 134352864000000000, Time zone (optional) = Riyadh (Saudi Arabia). Result: Date and time (UTC): 2026-10-01 00:00:00; Weekday: Thursday.
134352864000000000
2026-10-01 00:00:00
Limits and caveats
- lastLogonTimestamp replicates between domain controllers only every 9 to 14 days or so, so it can lag the real last logon.
- An accountExpires value points to the start of the day after the last valid day.
Questions about this tool
How do I read lastLogonTimestamp in PowerShell?
Use [DateTime]::FromFileTimeUtc(value) to get the UTC date.
What does 9223372036854775807 mean?
It is the largest possible value, and Active Directory puts it in accountExpires for accounts that never expire.
How is lastLogon different from lastLogonTimestamp?
lastLogon is exact but kept on each domain controller separately; lastLogonTimestamp is replicated but can lag by days.