place

Daberath

דָּֽבְרַת

Daberath was a Levitical city located in the territory of Issachar, later given to the Levites of the Gershonite clan.

Where the story of Daberath happens Daberath, and 1 place the claims reach, framed to them: Daberath, Bashan. Each dot is a coordinate from the gazetteer. The coastline is a modern one, simplified; no border, road or settlement of any period is drawn, and no line joins two points, because the rows state where and not in what order.DaberathBashan
Daberath, and 1 place the claims reach
verses
3
first named
Joshua 19:12
last named
Joshua 21:28
feature
settlement
coordinates
32.70°N · 35.38°E
settlement32.70°N · 35.38°E

Horvat Devora (OpenBible)

The gazetteer records one identification, and no competing one.

Description

Daberath in the text

In the words of STEPBible TIPNR:

Daberath was a city located in the territory allocated to the tribe of Issachar (Joshua 19:12) during the division of the Promised Land. It is mentioned as one of the border cities of Issachar, along with Chisloth-tabor and Japhia.

In Joshua 21:28 and 1Ch.6.72, Daberath is listed as one of the cities given to the Levites of the Gershonite clan from the tribe of Issachar, along with its pasturelands. This indicates that Daberath, or a portion of it, was set apart for the Levites, who were responsible for assisting the priests in the tabernacle service and teaching the law to the people.

The exact location of Daberath is not specified in the Bible, but it is generally identified with the modern village of Daburiyya, located at the base of Mount Tabor in Lower Galilee. This identification is supported by the similarity in name and the geographical context provided by the biblical references.

Apart from its designation as a Levitical city and its location on the border of Issachar's territory, no other details are provided about Daberath in the Bible. Its inclusion in the lists of cities and boundaries suggests that it was a recognized settlement during the time of Joshua and the early Israelite period, but its specific history and significance remain unknown.

Relations

Direct connections

Every entity the graph places in a stated relation with this one, grouped by the kind of link. Each relation is authored once and its inverse derived, so both ends always agree. Rows marked “registry” come from the identity spine rather than from a verse, and a row marked “which bearer is the source’s decision” is one where the name could have meant more than one person. The last group is not a relation at all — it counts the events two entities stand in together.

Stands in the same events as

and 13 more, ordered by how many events they share.

The pattern

Where Daberath is named

Every book of the corpus in the order it is read, each as wide as the chapters it holds. A bar is the verses of that book which write the name, and the flat stretches are as much of the answer as the bars.

Where the name is written across the corpus. 3 verses across 2 of 66 books; 64 write the name nowhere. OLD TESTAMENT · 39 BOOKSNEW TESTAMENT · 27 BOOKSJOSHUA2 VERSES53 books and 822 chapters with no mentionBOOK WIDTH = CHAPTER COUNT Where the name is written across the corpus. 3 verses across 2 of 66 books; 64 write the name nowhere. OT · 39 BOOKSNT · 27 BOOKSJOSHUA2 VERSES53 books with no mentionBOOK WIDTH = CHAPTER COUNT

3 verses across 2 of 66 books; 64 write the name nowhere. Named in Joshua (2) and 1 Chronicles (1).

Daberath is named in 3 verses — occurrences of the name in the Hebrew or Greek, counted in the versification of the Berean Standard Bible (v5.7). Every book of the corpus is drawn, its width its share of the 1,189 chapters. 64 of the 66 books never write it. A verse that tells of this subject without writing the name is not counted here.

Read it

Where to read it

Every verse of the text carried here that names this entity — 3, across 2 books.

  1. Joshua2 verses

    19:1221:28

  2. 1 Chronicles1 verse

    6:72

Onward

Where this page goes

Nothing in the graph stands one hop from this entity yet. These are the best-connected entities of the same type, so the page still ends somewhere. Descriptions by STEPBible TIPNR.

Sources

What this rests on