Search the Community
Showing results for tags '587 bce'.
-
We know that dates like 1513 BCE, 606 BCE, 587 BCE, 539 BCE, 70 CE (or AD), don't occur in the Bible, nor in the ancient astronomical diaries either. If we can pin a specific astronomical event to a record of any of Nebuchadnezzar's years, it would help. But we don't need those kinds dates yet. We can get them later. The first thing we need to do is to figure out where the variously listed kings fit in our timeline relative to each other. If we knew the order of the kings in succession and knew how long they each ruled for, we could at least create a "relative" timeline. So. To begin. Do ancient records provide an agreed upon list of kings, their order of succession, and the lengths of their rule? Yes. Do all ancient records agree? No. (Most would argue that they agree in all the important areas, and minor disagreements are easily fixed, but we should still admit that not all records are 100% in agreement.) So. Can we find two or three that do agree with each other, or perhaps even the majority of the records, in order to start a tentative timeline, and then deal with the disagreements later? Yes. The most important of the ancient records from Babylon itself and from those who made use of Babylonian records for astronomical purposes all agree anyway (Babylonians, Persians, Greeks). We would expect the most accurate records to relate to works for predicting or understanding eclipses (for example) or various lunar cycles and planetary movements. We know that certain types of astronomical phenomena were predicted in advance, or even known to be occurring even if invisible behind thick clouds, or because it occurred below the horizon, or invisible because some events relative to stars and planets could not be seen in the daytime. So we should expect records accurate enough to be used to actually calculate and predict a future eclipse even if it would be invisible. OK. So we'll put into our chart an example where two of these records agree with each other. For now, we'll pick the Royal King List that must have been available to Ptolemy's Almagest as a kind of "look-up table" and the writings of Berossus a Babylonian historian/priest from the Seleucid Period. They both agree on the following: Nabopolassar 21 years Nebuchadnezzar 43 years Awel-Marduk 2 years Neriglissar 4 years [Labashi-Marduk 9 months]* Nabonidus 17 years So, we have two "witnesses" (so far) to the names, years, and order of succession for these kings, which I will place in the chart below. To save space and give us a fairly legible font size, I only put in the last few years of Nabopolassar's 21 year reign. And we haven't discussed the length of position of Cyrus reign yet, but both Berossus and the Royal King List give him 9 years starting immediately after the 17th year of Nabonidus. So this, so far, becomes an 81-year span (arbitarily) from the 16th year of Nabopolassar up to the 9th year of Cyrus as King of Babylon. It might not be right, but it's a version that we can begin to test against the data to see if it holds up. E-M by the way, is short for Evil-Merodach (Awel-Marduk). 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 Nabopo-lassar N E B U C H A D N E Z Z A R II (reigned for 43 years) E-M Nerig- lissar N A B O N I D U S C Y R U S 16 17 18 19 20 21 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 1 2 1 2 3 4 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 1 2 3 4 5 6 7 8 9 *Labashi-Marduk reigned only a few months, but we would NOT expect his name included in a timeline used for counting the number of years between any points on the timeline. And we definitely would not expect it to be included for any purposes related to astronomy calculations. That's because if a reign was so short that it started in a year already counted as "Neriglissar 4" and it ended before the start of "Nabonidus 1" then it should not be inserted because those full years were already counted. In fact, it would be considered a mistake then to include it in an astronomical reference, because it would have thrown off all calculations. predictions and cycles by a full year, making the entire king list worthless. In this case, Berossus, in the role of historian mentions him, but in the Royal King List used for astronomical purposes as a reference for Ptolemy's Almagest, for example, it should NOT be listed, and it wasn't.
- 680 replies
-
- neo-babylonian
- chronology
- (and 9 more)
-
The October 1, 2011 Watchtower says this date is important for two reasons. *** w11 10/1 p. 26 When Was Ancient Jerusalem Destroyed?—Part One *** But why be interested in the actual date when Babylonian King Nebuchadnezzar II razed the city of Jerusalem? First, because the event marked an important turning point in the history of God’s people. . . . Second, because knowing the actual year when this “ultimate catastrophe” began and understanding how the restoration of true worship in Jerusalem fulfilled a precise Bible prophecy will build your confidence in the reliability of God’s Word. So why do Jehovah’s Witnesses hold to a date that differs from widely accepted chronology by 20 years? [Emphasis added]
- 774 replies
-
- 70 years
- gentile times
- (and 4 more)
-
A recent topic about whether the Watchtower view of 607 BCE is SCRIPTURALLY supported is linked below. This new topic should provide a better place to discuss the SECULAR evidence. I also think it would be useful to discuss the methodology that the Watch Tower Society has historically used to treat this evidence. I would hope that we can do this without so much side discussions of unrelated topics. To avoid another topic that goes on for 30+ pages where only half of them were on-topic, I would suggest that if we get enough off-topic posts, we merely move them to another more appropriate topic. The link to the most recent topic on a similar subject is here: