Aminadab-Aram/Adam-Admin-Arni in Luke 3, 33 133 it is reasonable to suppose that its author worked with annotations from various sources and, in the specific case of the succession from Perez to David, from the passage cited from I Chron. It would not be improbable to admit that, at first, such notes would have been organized in a very common manner for genealogical lists, that is, vertically with one name under the other, going from father to son, since that is the order found in his sources. This way, from the quoted passage in I Chron, he may have extracted only the information related to the succession of names and organized them as shown in the table 1: Table 2: Genealogical list from Perez to David Ι II φαρεσ φαρεσ εσρων εσρων αραμ αραμ αμιν αμιναδαβ αδαμ ναασσων ναασσων σαλμαν σαλμαν βοοσ βοοσ ωβηδ ωβηδ ιεσσαι ιεσσαι δαυιδ δαυιδ Column I presents a probable form of the list in the hypomnémata prior to the composition of the final text, possibly written in cursives, which would allow for the alternation between β and μ (αμιναδαβ > αμιναδαμ). Aminadab is the longest name in the list (with eight char- acters) which may have caused it to be divided into two parts merely for practical reasons (although Naasson is also long, having seven letters, it appears in the reduced forms Nasson or Naason, and its ending allows for abbreviation). Column II presents what the list may have looked like after the division of the name Aminadab into two lines, the stage after which the reading Adam-Admin would have been created through the following process: a) since the order in Luke’s genealogy is inverse to the one found in I Chron, the list in column II should be read from the bottom up, a process through which the author may have inadvertently produced the following sequence: δαυιδ του ιεσσαι του ωβηδ του βοοσ του σαλμαν του ναασσων του αδαμ του αμιν του αραμ του εσρων του φαρεσ;