person

Nebushazban

נְבוּשַׁזְבָּן

Nebushazban, a Babylonian official, was among those who took charge of Jeremiah after the fall of Jerusalem.

verses
1
first named
Jeremiah 39:13
period
Divided Monarchy
role
Man

Description

Who was Nebushazban?

In the words of STEPBible TIPNR:

Nebushazban, also known as Nebushazban the Rabsaris, was a Babylonian official mentioned in Jer.39.13. He was one of the high-ranking officers in the army of King Nebuchadnezzar II during the siege and conquest of Jerusalem in 586 BC.

After the Babylonian army had breached the walls of Jerusalem and captured the city, Nebushazban was among the officials who entered the city. Along with Nebuzaradan, the captain of the guard, and other Babylonian officers, Nebushazban was involved in the decision-making process regarding the fate of the city and its inhabitants.

According to Jer.39.13, Nebushazban, along with the other officials, sent for the prophet Jeremiah and had him released from the court of the guard where he had been confined. This action was in accordance with the instructions given by King Nebuchadnezzar, who had ordered that Jeremiah be protected and treated well (Jer.39.11-12).

Apart from this brief mention, no further information is provided about Nebushazban's background, specific role, or personal characteristics. His presence in the biblical narrative serves to highlight the involvement of high-ranking Babylonian officials in the events surrounding the fall of Jerusalem and the treatment of Jeremiah during this turbulent time.

Relations

Direct connections

The kinship import reads the registry's own columns — parent, child, sibling, spouse — for every entity in it, and records none here. An extracted relation would be listed beside them, and none names this person either.

Not stated

No family is recorded for this person.

Places

Where this happens

A person is placed by the events they take part in, and an event has to clear three things to place them: it must say where it happened, that place must be one the gazetteer can put a coordinate on, and the verse must report it rather than foretell, command or ask it. Nothing anchored here clears all three. Where the text names a setting no gazetteer surveys — a vineyard, a palace, a plot of ground — it is left off rather than guessed at; where a place is named only in a prophecy, the map does not draw what was said to be coming as though it had happened; and a place reached only through a relation is not inherited, because standing beside somebody is not being somewhere.

No verse Atlas has read as a report puts this person anywhere.

Not read yet

The pattern

Where Nebushazban 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. 1 verse across 1 of 66 books; 65 write the name nowhere. OLD TESTAMENT · 39 BOOKSNEW TESTAMENT · 27 BOOKSJEREMIAH1 VERSE23 books and 745 chapters with no mentionBOOK WIDTH = CHAPTER COUNT Where the name is written across the corpus. 1 verse across 1 of 66 books; 65 write the name nowhere. OT · 39 BOOKSNT · 27 BOOKSJEREMIAH1 VERSE23 books with no mentionBOOK WIDTH = CHAPTER COUNT

1 verse across 1 of 66 books; 65 write the name nowhere. Named in Jeremiah (1).

Nebushazban is named in 1 verse — 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. 65 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 — one, across 1 book.

  1. Jeremiah1 verse

    39:13

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