Audited Date Reports

At this point we've built up a calendar system forward from the past. That calendar has a known 30 day per month structure with Jubilee structure that drives a 50 year cycle.

We assumed that prophetic history was still running on that system. The Jewish Return to the modern Nation of Israel being the big, obvious, headline, landing in a series of years driven from histories given in Jeremiah.

We have also shown that there is a day-for-a-year replay of that same historical time line at the Passover just after the millennium break, at the start of 13001 AA.

That day-for-a-year nature meant that the 365 years of the life of Enoch were also 365 modern days, aligning with the Julian calendar for the year 1985. This in part because the Julian calendar has been in operation since the events in Passion Week.

With all of those details established, we now have enough information to link any date given in the Bible to a modern date. This is done with day-accurate precision provided the date is given day-accurately in scripture. (Not all dates are so given, but many are, including some of the earliest dealing with Noah's flood.)

Notice that these day-accurate linkages are dependent on the English Translation of the Bible, and a very simple level of modern headline knowledge, like that traditionally printed in an Almanac.

There is no secret processing, no reliance on off-Bible sources in history, no reliance on any modern academic work, which is often fraudulent. This linkage can be verified by anyone using only a Bible and a source like a printed Almanac. This is powerfully simple, and will be characterist of much future work.

Modern Calendar Problems

What we quickly slam into is a modern problem. The modern calendar is not very day-accurate itself. It is possible to claim, with some support, that the Bible is more accurate than most modern history recording systems.

The biggest problem is the use of the Gregorian Calendar and the transition to that calendar from the Julian. When that transition happened in the English speaking world, even the calendar date for New Years Day was changed, from March 25 to January 1, so even the year number changed for historically recorded dates in January, February and most of March.

In order to provide tooling to cope with these modern issues of calendar variation, I developed a software system that measures all days by a single integer number. That system counts year 1, month 1, day 1 of Adam, as simply day number 1.

It generates reports, called Audited Date Reports(ADRs) that are easily inserted into the HTML of website articles, articles like this one, that you are reading now.

Each row in an ADR represents 1 day somewhere between the first day of the first year of Adam and our own distant future. For a sence of scale, ADR rows for current dates are over 4.7 million days since Adam.

For each of those days the software supplies a total of 9 pieces of information, and that information is provided in a standard report.

The following report is an example. This particular report gives the date of the first Passover inside our new millennium that had started 14 days before.

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

Technical precision like this often forces discussion that might not have happened otherwise. This Passover is measured on the same system used to write the whole Bible itself. It is not a Jewish Passover, something that happens on a different calendar system. The Jewish Calendar used today by Jews uses a formula system that was not stablized until after 900 AD on the Gregrian Calendar.

The New Testament writers knew the difference, and were clear to point out that the Passover when Jesus was crucified was a Jewish Passover, not a passover of Moses. We'll see that in more detail when we study Passion Week.

So when we look at dates on this calendar we are looking through a clear prism to a date system that is totally foreign to modern people. It is lost to all who use the Gregorian, and Julian, calendars to set holidays. It is also lost to all who use the Jewish Calendar to set holidays.

This same calendar has an online version, available in a stand alone tool, cal.paleo.in. You can use that to find current holidays, should you so desire.

Notice how the report has a heading, typically in red, that describes the whole table, its purpose within the article in which it falls.

In this case it is explaining this is the first Passover of Moses inside our new modern milliennia, a prophetic, end-times, millennia long day-break.

Multiple Rows

In some queries, depending on the use, there may be additional dates, this example shows only one date. This particular report shows the day in question in nine different ways.

This is not because the Bible Calendar needs this. The problem springs from modern, real world calendars. This is how they operate. Each day is known by the different labels assigned to that day by various calendars. By having all the various labels provided for each date cross calendar correlation is possible.

Because most browsers are on smaller screens, the 9 pieces of data provided for each date are spread across only 5 columns. The rest of this article explains the various fields in detail.

Field #1: Day of Week

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

The day of week for the individual day is provided in the left most column. Highlighted here with a double arrow (). If you don’t see the arrow your browser is not displaying Unicode and should be upgraded. In this case the day in question is Sunday. This system only knows days by day name, so the day name occupies the space of two rows in the other columns.

The day name cycle has no known changes and has operated on the standard 7 day cycle used today for all known time. This is thus the same 7 day cycle used today. There are differences of opinion about which day of this 7 day cycle should be considered the "first day" Europeans typically draw calendars with Monday as the first day. Americans and Jews typically place Sunday as the first day.

To avoid confusion these date reports do not indicate day of the week but rather use the day name.

Field #2: Bible Date, Adam’s Epoch

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

One of the principles of the Bible Time system is that time in the Bible is both 1) day-accurate and 2) given to the reader on a special calendar used to record the Bible. That period is drawn in green (see colors below) when dates are within the Bible’s historical period.

They are drawn in blue (also see below) when the date in question is passed the Biblical era. Dates are known to continue and are day-accurately alignable between the two date counting systems. The day in question is known on that Bible calendar as given in this field.

The abbreviation AA indicates this is a date from Adam.

Field #3: Bible Date, Exodus Epoch

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

The Exodus Epoch for the Bible Calendar began at the Exodus from Egypt sometimes measuring time from Egypt is more useful than measureing time from Adam so that time is given on each date report.

This epoch is measured "From the Exodus" it is abrieviated "FE" This has the same month and year structure as the calendar from Adam and is offset by a 9500 year difference, the difference in years between the start of Adam’s life and the Exodus from Egypt.

As the day for a year story points at an historical culmination at 3501-01-15 FE, this particular date provides an easy aproximation of the time through this interval.

Curiously, 70 Jubilee Cycles are 3500 years long, so this particular Passover of Moses is timed relative to various "70 times" prophecies. This point is most easily seen on the FE calendar.

Field #4: Modern Date, Gregorian Calendar

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

This is the date as viewed by the modern Gregorian calendar, the most common calendar used in the world today.

As the Gregorian calendar was adopted around the world various countries dealt with the problem of dates given on both calendars. An example is this: a legal contract might be written that said a building was to be leased for 1 year ending on a certain date. The contract was written before the date conversion.

The meaning of the contract was implictly the "Old Calendar" while everyone switched to a "New Calendar." To cope the NS was added to Gregorian dates to indicate a "New Style" date. NS was eventually dropped from dates that were unquestionably new, as the Gregorian calendar is today.

Since these reports generate dates on both calendars the world wide standard NS abbreviation is used here.

The NS calendar is the most accurately aligned with seasonal cycles on the earth and is the best calendar for validating the time of year when different events happened. (Being aware of pole shifts, of course.)

The NS calendar is the one usually used by astronomers, but dates can be converted to historical dates by a well meaning but ultimately harmful astronomers. The NS calender was unknown in New Testament times, for example.

Field #5: Modern Date, Julian Calendar

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

This provides the date as the day was known on the Julian Calendar. As this calendar is the most common calendar supplanted by the modern calendar it is abrievated "OS" for "Old Style." A convention used almost universally at the time of conversion.

There are many quirks in the use of this calendar. The biggest area of confusion is the use of March 25 as New Years day. This was the Christian tradition back to the time of Jesus. Memory of Resurrection Sunday was carried forward in the New Year’s day tradition. It makes many date calculations error prone as the Christian year did not end until its last day on March 24.

Some contries, notably Russia, converted New Years day from March 25 to January 1, while otherwise maintaining the Julian Calendar. These reports use the English speaking world convention where New Years was changed at the same time as the change from Julian to Gregorian calendars.

All dates presented in this field on date reports use the Christian New Years date of March 25.

For completeness, the Pagan year definitions, where January 1 is New Years day, is captured in the Roman calendar explained below.

Field #6: Roman Calendar, City of Rome Epoch

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

The Roman Calendar system began counting years at the founding of the City of Rome, and year counted this way are abrevitated with "AUC" as their ending. Most almanacs containe perpetual calendars and provide the modern correlation to the AUC year counting system.

Most civil documents in Roman times were given on this calendar, though the year of the reign of the emporer was the common notation, as it was in the English speaking world into modern times.

The dates in this column attempt to reflect the dates as actually lived, and so an attempt is made to track the known date changes. No roman date anywhere is trustworthy before the start of the year 46 "BC" as it was at this point that control of the calendar was switched from the political arena to the "scientific" arena and the calendar became regular.

Before 46 BC leap months required a political action of the Roman Senate. (or of the Roman priests, according to some sources) The superstitious Romans would not vote for a leap month if the Roman Empire was at war, something that happened often. This makes all dates given in the Roman world before 46 BC subject to significant errors. No dates given from any source for a BC date before 46 BC should be trusted at all.

There are also quite a few other date details known and implimented in this family of calendars. 46 BC was known in the Roman world as the "year of confusion", the leap year pattern was every 3rd year for a time, then suspended before stablizing in 8 AD. All such known quirks are coded and implemented here.

Field #7: Roman Date, Jesus’ Epoch

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

When Christianity took over and renumbered the Roman AUC years, the "AD" and "BC" notations were adopted to indicate a different form of year counting as being in effect. 753 AUC became 1 AD , 752 AUC became 1 BC and so on out from this transition year.

Christians also firmly in control at Rome abandoned the pagan new years day of January 1 and moved it to March 25. Because the Christian year numbers are sometimes the only implied difference between AUC and AD years, this box uses the odd case of leaving new years at January 1.

Depending on your calendar use this may be the right choice.

This is the calendar that should be used when a known historical date from an authentic source is to be viewed on the system. Note that there was substantial differences in the structure of this calendar before the year 46 BC.

Field #8: Days by number, Numbered from Adam

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

These day numbers are prefixed by with "AA:" indicates the day number "After Adam" as counted on the Biblcal calendar used in the Bible Date column. This system of day numbers provides positive day numbers, defined along the lines of Biblical days, from the beginning at Adam. All day numbers likely to be encountered on all biblical studies are positive using this day numbering scheme.

This system is artificial in the sense that no historical use of this number system was ever used. (It takes a computer before practical use of day numbering systems are possible.)

This number provides provides two sources of possible audits. Because the months on the Bible calendar are always 30 days, the last two digits of the AA Number always agrees with the last two digits of the day of the AA and FE dates. This is also an important audit tool when large day counts, such as the 12,000 days indicated in Revelation 7, are charted using the online tools. In all cases of days being seperated by even multiples of 1000 days, the last three digits of the AANumber for each date are the same.

Field #9: Days by number, Julian Days.

First New Millennium Passover of Moses
Mon13001-01-14 AA1 Mar 2010 NS16 Feb 2763 AUC4742414 AAN
3501-01-14 FE16 Feb 2009 OS16 Feb 2010 AD2455257 JDN

These day numbers are prefixed with "JD:" this day counting system is known as the Julian Day counting System, after the man who invented it. JD Day numbers are a world wide standard for counting of individual days. JD day numbers are commonly used by astronomers.

This day counting system defines its days differently than the rest of the calendar, so take care. Julian days actually start at Noon, GMT, on the day otherwise in question, so up until Noon, GMT, in any given day, the day is still on the previous Julian Day. Since the calendar tools behind these date reports do not care about hours, this odd day-start time is ignored. The JD number provides another source of cross-check to the online calendar system. It can also be used for audit purposes. It is not as useful as the After Adam day numbers as some day numbers are negative, leading to confusion on the part of human readers.

Color Key

All reports generated on this system use color to warn of mis-applied dates. The issues with choosing the right calendar for various uses are complex.

The problem is that calendars are mathematical instruments which are defined well beyond the times when they are typically used. Often, we see various sources re-dating events across different calendars. This is a huge problem since it causes severe problems of error just from the lack of understanding the current calendar.

To help with these problems the Bible Time tools use a coloring scheme to help prevent gross errors of interpretation. The following is an example report showing the way the reports can be colored.

The following shows Sunday, March 25, 31 AD. This is the New Years day that was selected because it was Resurrection Sunday.

Note the calendar coloring is quite different than used on a modern date.

Resurrection Sunday, March 25, 31 AD
Sun11019-10-11 AA23 Mar 31 NS25 Mar 784 AUC4019621 AAN
1519-10-11 FE25 Mar 31 OS25 Mar 31 AD1732464 JDN

The following explains what each color means on these sorts of reports.

  • Green is used to indicate widespread use. Green dates are generally trustworthy.

  • Blue is used to indicate that this is past the point of widespread use on the calendar in question. This is true of the Biblical Calendar after the fall of Jerusalem, the Roman calendars after the adoption of the Gregorian calendar.

  • Red is used to indicated that the calendar in question was unknown to anyone on the date in question. This means that the calendar in question is simply being run backwards from when it was used to an earlier date.

    Knowing back-dates like this is useful as it can be used as a system verification. The Gregorian Calendar, abbreviated NS, for example, is in very close agreement with the seasons of the earth, so it should be the one consulted if you are interested in the season for an event otherwise dated on a different calendar.

  • Black is used to indicate a date not widely used or for which there are issues of accuracy. Black is used in some important ways:

    • On the Exodus Epoch of the Biblical calendar to indicate caution before the Exodus.
    • On the Roman calendar before 46 BC to indicate uncertainty over unknown intercalenary months.
    • On the Gregorian calendar to indicate its lack of full scale adoption. (The English speaking world’s adoption in 1752 marks widespread adoption for our purposes here, though take care, other countries would adopt much later than this.)

Phil Stone, Updated 2016-11-06