Track Record · Source doc 04-04 · 301 AD–2022

Qumran Chronometrics Scored Against Verified History

22 hits (13 exact-date matches), 1 unverified, 0 clear misses

Purpose: Same discipline as the Shemitah audit — check every dated claim in the Qumran Chronometrics file against documented history before treating it as content-ready.

Scored Results

Date ClaimedEventVerdictNotes
Nov 20, 301 ADDiocletian price-fixing/hyperinflationHITDiocletian’s Edict on Maximum Prices, 301 AD, is well-documented. Exact day-level precision harder to independently verify than the year/edict itself.
Oct 13, 1307Knights Templar arrestHIT (exact)Confirmed precisely — Philip IV’s arrest order was dated Oct 13, 1307.
May 10, 1345Edward III default / Bardi-Peruzzi collapseHIT1345 confirmed as the crisis year across multiple sources; exact day less independently verifiable, but the year and causal claim (Edward III’s default) are accurate.
Feb 5, 1637Tulip Mania collapseHITConfirmed — market collapse began February 1637.
Sept 20, 1674Dutch West India Company insolvencyUNVERIFIEDCouldn’t independently confirm this specific date/event with confidence. Flagging honestly rather than guessing — this one needs its own dedicated check before being published as fact.
Sept 9, 1720South Sea BubbleHIT, with a caveatThe Bubble’s initial burst is often dated mid-July 1720; the collapse deepened through autumn. September falls within the real collapse window but isn’t the single most-cited date.
Sept 15, 1720Mississippi Company / John Law collapseHIT, same caveatSame nuance as above — real event, correct general window, not the most precise single date available.
June 9, 1772Alexander Fordyce collapseHITFordyce’s flight and the credit crisis he triggered are accurately dated to June 1772.
March 9, 1792William Duer / Panic of 1792HITConfirmed as America’s first Wall Street panic, correctly timed.
May 18, 1796French Assignat collapseHITFalls within the real 1795-96 collapse window of the Assignat currency.
May 10, 1837Panic of 1837HIT (exact)May 10, 1837 is the well-documented date New York banks suspended specie payments.
Aug 24, 1857Ohio Life Insurance & Trust failureHITConfirmed, correctly dated and attributed.
May 10, 1866Overend Gurney collapseHIT (near-exact)The firm suspended payments May 10, 1866; the resulting panic (“Black Friday”) hit the next day. Essentially precise.
Sept 18, 1873Jay Cooke & Co. failureHIT (exact)Confirmed precisely, triggered the Long Depression.
Nov 7, 1890Baring Brothers crisisHITConfirmed, correctly timed to the Bank of England’s rescue intervention.
Oct 29, 1929Black TuesdayHIT (exact)Universally documented.
Oct 6, 1973Yom Kippur War / OPEC crisisHIT (exact)War began precisely Oct 6, 1973.
Oct 19, 1987Black MondayHIT (exact)Universally documented, independently confirmed against the Shemitah cycle too.
Aug 17, 1998Russian default / LTCMHIT (exact)Russia’s default and ruble devaluation announced precisely this date.
Mar 10, 2000Dot-com peakHIT (exact)NASDAQ’s actual peak date.
Sept 11, 20019/11HIT (exact)—
Sept 15, 2008Lehman Brothers collapseHIT (exact)Lehman’s bankruptcy filing date.
Mar 16, 2020COVID crashHITOne of several severe March 2020 days; this one specifically was a ~13% single-day Dow drop.
Feb 24, 2022Russia invades UkraineHIT (exact)—

Scorecard: 22 hits (13 exact-date matches), 1 unverified, 0 clear misses.

The important finding isn’t the score — it’s why the score is so high

This file’s hit rate is dramatically stronger than the Shemitah cycle’s (22/24 vs. 12/18). That’s not because this framework is more predictively powerful — it’s because it’s a structurally different kind of claim, and conflating the two would be dishonest.

The Shemitah cycle makes a genuinely risky claim: a fixed 7-year mathematical interval, calculated forward regardless of what actually happens in a given year. It can and does miss (1907 and 1929 both fell in the gaps).

Qumran Chronometrics does something different: it starts from already-known, real historical crashes and calculates which point in the Enochian solar calendar each one landed on. Every entry was selected because something real happened on that real date — there was never a chance of it “missing,” because the dates weren’t predicted in advance, they were identified after the fact and then mapped onto a calendar system.

Both things can be true at once, and both are worth publishing — but they’re different claims:

  • Shemitah cycle: “This interval predicts crashes” — genuinely tested, genuinely imperfect, genuinely more interesting because it could have failed and mostly didn’t.
  • Qumran Chronometrics: “Major historical crashes cluster around specific points in this calendar system” — a real, checkable pattern, but not a predictive claim in the same sense. It’s closer to “here’s what these events have in common” than “here’s what to expect next.”

Presenting the second as if it has the same predictive force as the first would be exactly the kind of overclaiming this whole project exists to catch. We use this file’s real strength — calendar clustering is a genuinely interesting pattern — without borrowing the Shemitah file’s kind of credibility (successful advance prediction) for it.

One open item

Sept 20, 1674 (Dutch West India Company) needs its own dedicated verification pass before being published as a confirmed fact — flagged honestly rather than asserted.

Frequently Asked Questions

How accurate is Qumran Chronometrics compared to the Shemitah cycle?

It scores much higher — 22 hits (13 exact-date matches), 1 unverified, 0 clear misses — but that's because it's a fundamentally different kind of claim. It maps already-known historical crashes onto a calendar system after the fact, rather than predicting a date in advance the way the Shemitah cycle does. A high score here isn't proof of stronger predictive power.

Is there anything still unverified in this file?

Yes, one entry: the September 20, 1674 Dutch West India Company insolvency couldn't be independently confirmed with confidence and is flagged honestly as unverified rather than asserted as fact.

← All Track Record audits