1 microsoft second = 0.00001157407407

calendar_today Asked Nov 26, 2013
thumb_up 19 upvotes
history Updated April 14, 2026

Direct Answer

In Excel, each day is represented by 1.0, with a value of 1.0 being equal to January 1st, 1900 (ie: it's effectively the days since 12/31/1899, plus one if you're after Feb 1900).…. This is a prose walkthrough, ranked #92nd of 303 by community upvote score, from 2013.


The Problem (Q-score 4, ranked #92nd of 303 in the Excel VBA archive)

The scenario as originally posted in 2013

I was writing a routine to read from an Excel spreadsheet.

I have just discovered thro that MS Excel spreadsheet that

1 microsoft second = 0.00001157407407

1/1/1900 0:00:01.000    1.000011574
1/2/1900 0:00:02.000    2.000023148

Why?

Why not 0.00001, or some rounder number?

What is the significance of 0.00001157407407?

Binary value = 0.00000000000000001100001000101110

Why community consensus is tight on this one

Across 303 Excel VBA entries in the archive, the accepted answer here holds strong answer (top 25 %%) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — strong answer (top 25 %%) (+19)

Verbal answer — walkthrough without a code block

Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Excel VBA entries ranked in the top 10 of the same archive.

In Excel, each day is represented by 1.0, with a value of 1.0 being equal to January 1st, 1900 (ie: it’s effectively the days since 12/31/1899, plus one if you’re after Feb 1900).

This works out to each second being the number you posted, which is effectively 1 day / (24 * 60 * 60) or 1 / 86400 == 0.00001157407407.


When to Use It — classic (2013–2016)

Ranked #92nd in its category — specialized fit

This pattern sits in the 94% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Excel VBA archive for a higher-consensus alternative.

What changed between 2013 and 2026

The answer is 13 years old. The Excel VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

Why does this sit in the top quartile of Excel VBA answers?
expand_more

Answer score +19 vs the Excel VBA archive median ~6; this entry is strong. The score plus 4 supporting upvotes on the question itself (+4) means the asker and 18 subsequent voters all validated the approach.

The answer has no code block — how do I turn it into a snippet?
expand_more

Use the walkthrough above as a checklist, then open a top-10 Excel VBA archive entry for a concrete starting template you can adapt.

Published around 2013 — what’s changed since?
expand_more

Published 2013, which is 13 year(s) before today’s Office 2026 build. The Excel VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Excel VBA pattern ranks just above this one at #91?
expand_more

The pattern one rank above is “How to Call VBA Function from Excel Cells?”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 4, Answer-score 19, original post 2013, ranked #92nd of 303 in the Excel VBA archive. Last regenerated April 14, 2026.

excel