.NET ticks to date
For example, 638712000000000000 is Tue, Dec 31, 2024, 12:00:00 AM UTC, which is 2024-12-31T00:00:00.000Z in ISO 8601 and 1735603200 in Unix seconds.
100-nanosecond intervals since 0001-01-01T00:00:00 (the .NET DateTime epoch), read as UTC.
Detected: .NET DateTime ticks/t/638712000000000000
Your timezone
UTC · GMT+00:00 · UTC
Tue, Dec 31, 2024, 12:00:00 AM
Common formats
UTC
Tue, Dec 31, 2024, 12:00:00 AM
ISO 8601
2024-12-31T00:00:00.000Z
Unix (seconds)
1735603200
Unix (millis)
1735603200000
Relative
…
In .NET, DateTime.Ticks counts 100-nanosecond intervals since midnight on January 1 of year 1. For any modern date that's an 18-digit number. You'll see it in serialized objects and log dumps. Paste a ticks value below to get the date back, along with the Unix timestamp and ISO 8601 form.
Do it with the API
curl https://parsetime.dev/api/t/638712000000000000?format=ticksThe same conversion as JSON: no key, no signup, permissive CORS. Try this call or read the API docs.
Common questions
- How do I convert ticks to a DateTime in C#?
- new DateTime(ticks, DateTimeKind.Utc), or paste the value above if you just need to read one. Note that Ticks alone carries no timezone; .NET's Kind property is separate, so know whether your value was recorded as UTC or local.
- How do ticks relate to a Unix timestamp?
- Unix seconds = (ticks − 621355968000000000) ÷ 10,000,000. That constant is the tick count at the Unix epoch, January 1, 1970.
- Why is my ticks value 18 digits when epoch nanoseconds are 19?
- Ticks count from year 1, not 1970, but in units of 100 ns rather than 1 ns, and the two effects nearly cancel. That's what makes the two formats so easy to confuse. A 2026 date is ~638×10¹⁵ ticks but ~1.7×10¹⁸ epoch nanoseconds.