Raamses II to Thutmosis III: a helpful? Fixed?
Period ---From
the accession of Raamses II to the accession of Thutmosis III earlier, scholars
are working with a 200 year period. Thus Kitchen, Krauss and Hornung. ---Just
when you think it is fixed, it is not. ---Others
are working with a 225 year period. ---Thutmosis
III died exactly in the year biblical chronology recorded it to be. 1450 BC. ---Traditionally,
scholars accepted that Raamses II became king in the 19th year of
the Kassite Kadashman-Enlil of Babylon, namely 1304 or 1290 BC. ---Some
calculated 1304, others 1290 BC. ---From
these alternatives the 200 year period was calculated. ---J.
A. Brinkman of Chicago University, lowered the Babylonian chronology and caused
the date in his system to be 1279 BC. ---A
certain M. Bierbrier supported this view. ---Brinkman
has two dates for the 19th year of Kashman-Enlil namely a higher
date as 1283 BC and a lower date as 1261 BC. ---If
one accepts 1283 BC as the accession year, then 1304 BC is the year of the accession
of Raamses II. ---So
three dates are given for Raamses II: 1304 BC (high) or 1290 (middle) or 1279
BC (low). ---In
the diagram below is given the various calculations regarding these two
Pharaohs by scholars. Three dates listed supra are used. ---One
can see two options for the length of the reigns namely 225 or 200. ---One
can see subtracting 55 years to arrive at the date for the Exodus. ---We
already know that the Bible mentioned 1450 BC as the date of the Exodus. ---Keep
in mind that the scholars who calculated these various options, are not
necessarily Bible readers. They may be agnostic, atheists or secular. ---One
can see that there is one option for 200 years between the Pharaohs ending in
1450 BC for the Exodus. ---There
is also one option for 225 years between the Pharaohs ending also in 1450 BC. ---Whether
you want to follow truth by quantity of supporters or truth because it aligns
perfectly with the Bible…is a case that I cannot force you to accept, but I
will know why you are right or wrong on the issue.