25.03.2016 Views

The Gentile Times Reconsidered Chronology Christ

An historical and biblical refutation of 1914, a favorite year of Jehovah's Witnesses and other Bible Students. By Carl Olof Jonsson.

An historical and biblical refutation of 1914, a favorite year of Jehovah's Witnesses and other Bible Students. By Carl Olof Jonsson.

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix 343<br />

Nebuchadnezzar’s army left Babylon “in the month of Kislev,”<br />

which was the ninth month, and seized Jehoiachin “on the second<br />

day of the month Adar,” that is, the twelfth month. 69 This means<br />

that even if the army left Babylon in the beginning of Kislev (which<br />

this year began on December 18, 598 B.C.E., Julian calendar), the<br />

interval between the day it left Babylon until the city was captured<br />

and its king (Jehoiachin) seized, on the second Adar (which<br />

corresponded to March 16, 597), was three months at the most. 70<br />

As Jehoiachin ruled for “three months and ten days” (2<br />

Chronicles 36:9), he evidently had been ruling for some days already<br />

when Nebuchadnezzar left Babylon in the month of Kislev! If the siege of<br />

Jerusalem described at Daniel 1:1f. referred to this siege during the<br />

reign of Jehoiachin, how could it be said that it took place during the<br />

reign of Jehoiakim (Daniel 1:1), that Nebuchadnezzar came up<br />

“against him” (2 Chronicles 36:6), and that “Jehovah gave into his<br />

hand Jehoiakim” (Daniel 1:2), when Jehoiakim was already dead<br />

when Nebuchadnezzar left Babylon?<br />

Equating the siege described at Daniel 1:1f. with the one that<br />

took place during the reign of Jehoiachin (2 Kings 24:10–12; 2<br />

Chronicles 36:10) is clearly impossible. Daniel and the Chronicler<br />

at 2 Chronicles 36:6 both obviously describe an earlier siege and an<br />

earlier deportation, during the reign of Jehoiakim. <strong>The</strong>re is no reason<br />

to believe that the “third year” of Daniel 1:1 means anything else<br />

but his third year of reign. <strong>The</strong>re is no evidence at all, either in the<br />

book of Daniel, in the other books in the Bible or in the<br />

contemporary Neo-Babylonian historical texts, that regnal years<br />

were reckoned from a king’s vassalage, or from Nebuchadnezzar’s<br />

rise to world dominion. Such theories are nothing more than<br />

unfounded guesses, adopted only in an attempt to defend an<br />

erroneous application of the seventy years of servitude predicted by<br />

Jeremiah.<br />

69 <strong>The</strong> Babylonians had a second Ululu (an intercalary month) in the seventh year of<br />

Nebuchadnezzar, thus making Kislev and Adar the tenth and thirteenth months<br />

respectively that year, although they were normally the ninth and twelfth calendar<br />

months . This fact does not affect the discussion above.<br />

70 If the Babylonian army left Babylon some time after Jehoiachin had ascended the<br />

throne, the siege was of very short duration, two months at most and probably<br />

less, as the time the army needed to march from Babylon to Jerusalem has to be<br />

subtracted from the three months from Kislev to Adar. Such a march took at least<br />

one month. It is possible, however, that a part of the army had left Babylon earlier,<br />

as 2 Kings 24:10–11 indicates that Nebuchadnezzar arrived at Jerusalem some<br />

time after the siege had begun. <strong>The</strong> reason for the short duration of the siege was<br />

Jehoiachin’s surrender to Nebuchadnezzar on Adar 2 or March 16, 597 B.C.E.,<br />

Julian calendar. (2 Kings 24:12) For an excellent discussion of this siege, see<br />

William H. Shea, “Nebuchadnezzar’s Chronicle and the Date of the Destruction of<br />

Lachish III,” in Palestine Exploration Quarterly, No. 111 (1979), pp. 113f.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!