Enoch Calendar — Reading

The Library

References and arguments behind the calendar

Seven topics maintained alongside the Enoch Calendar — the solar gate table of 1 Enoch 72, Wednesday or Thursday, the Leap Week, biblical chronology, the empires of Daniel, the empires of Revelation, and the 360-day prophetic year. Each topic is available as a quick-reference card and as a longform essay. The references are for looking up; the essays are for the experience of the argument.

How to use this page

Each topic below has two pages. The reference is a structured card stack — every anchor, empire, or vision presented in a consistent format with the relevant scriptures and dates. Use it for looking things up or for an overview at a glance.

The article is a 25–30 minute longform essay that argues the case in prose. Use it when you want the story rather than the data, or when you want to see how the pieces hold together as a single line of thought.

Topic 1

1 Enoch 72 — The Solar Gate Table

The Astronomical Book of Enoch reduces the solar year to a single table: twelve months, six rising portals on the eastern horizon, and the day-by-day count of light and dark. It is the mechanism the rest of this library rests on — the calendar's own account of how the sun keeps time, and where the year's first morning falls.

Topic 2

Wednesday or Thursday?

The Day the Entire Biblical Calendar Hinges On

The foundational calendar question: does the Enoch year begin on Wednesday or Thursday? The Dead Sea Scrolls community placed Day 1 on Wednesday, but seven independent biblical anchors resolve only when Thursday is treated as Day 1 — with Wednesday standing as Wednesday or Thursday, the boundary day that stands outside the count. The argument rebuilds the Enoch calendar's starting point from 1 Enoch 72's own sunrise-counting logic and shows where the original was most plausibly lost.

Topic 3

The Leap Week

The 364-day Enoch Calendar runs 1.24 days short of the solar year. Left uncorrected, the spring equinox would drift out of its season within decades. The solution is a Leap Week — seven days added once every five or six years, keeping the weekly cycle intact while holding the equinox inside a ±3.5-day window centered on noon of the Tekufah Spring day. The calendar computes every Leap Week directly from NASA's JPL DE441 ephemeris — across 7,000 years of that data, the equinox never left the one-week window.

Topic 4

Biblical Chronology

Every date in the Bible can be traced — through bracket arithmetic and external records — to a small number of anchor points that are independently fixed by Assyrian, Babylonian, Persian, Greek, and Egyptian sources. The chain runs from the patriarchs to the Crucifixion, anchored at every joint to documents that survive outside Scripture.

Topic 5

The Empires of Daniel

Daniel saw the future of the world three times — in metals (a great statue), in beasts (lion, bear, leopard, dreadful), and in named animals (a ram and a he-goat). The angel Gabriel identifies two of the empires explicitly in Daniel 8, which locks the entire architecture. Babylon → Medo-Persia → Greece → Rome, then the divided final form, then the kingdom that has no end.

Topic 6

The Empires of Revelation

In Revelation 17, an angel pauses to do the count: seven kings, five fallen, one currently reigning, one yet to come — plus an eighth, of the seven, that goes to perdition. Each is a world empire that ruled the covenant people in turn. John, exiled to Patmos, was alive inside the sixth empire when the count was given to him. The empires he sees overlap exactly at four with the empires Daniel saw.

Topic 7

The 360-Day Prophetic Year

Daniel and Revelation, six centuries apart, both measure prophetic spans on a fixed calendar of 30-day months and 360-day years — never the real moon, never the real sun. Every stated conversion between months, days, and years on that calendar comes out exact, because the unit is never adjusted for the real sky. It needs no leap week, because unlike the Enoch Calendar it is never reused as a lived, ongoing calendar — only as a one-time conversion of a stated span into days.