Turkse veldslag nabij Barkan aan de Donau, 1683

Caspar Luyken (mentioned on object), 1689

Prent rechtsboven gemerkt: fol. 256.

  • Artwork typeprint, boekillustratie
  • Object numberRP-P-1896-A-19368-750
  • Dimensionsheight 115 mm x width 137 mm
  • Physical characteristicsets

Discover more

more by Caspar Luyken

Heelal met aarde, zon, maan en sterren

Caspar Luyken, 1712

Heelal met aarde, zon, maan en sterren

Title Page and Eight Prints with Flowers

Caspar Luyken, 1698

Title Page and Eight Prints with Flowers

Title Page and Eight Prints with Flowers

Caspar Luyken, 1698

Title Page and Eight Prints with Flowers

Title Page and Eight Prints with Flowers

Caspar Luyken, 1698

Title Page and Eight Prints with Flowers

Title Page and Eight Prints with Flowers

Caspar Luyken, 1698

Title Page and Eight Prints with Flowers

Title Page and Eight Prints with Flowers

Caspar Luyken, 1698

Title Page and Eight Prints with Flowers

Identification

  • Title(s)

    • Turkse veldslag nabij Barkan aan de Donau, 1683
    • Batalje van de Keisersche tegen de Turken bij Barkan, in 't Jaar 1683 (title on object)

  • Object type

  • Object number

    RP-P-1896-A-19368-750

  • Description

    Prent rechtsboven gemerkt: fol. 256.

  • Inscriptions / marks

    collector's mark: Lugt 2228

  • Catalogue reference

    Van Eeghen 1031

Creation

  • Creation

    • printmaker: Caspar Luyken (mentioned on object), Amsterdam
    • printmaker: Jan Luyken (mentioned on object), Amsterdam
    • printer (person): Jurriaen van Poolsum, Utrecht

  • Dating

    1689

  • Search further with

Material and technique

  • Physical description

    ets

  • Dimensions

    height 115 mm x width 137 mm

Explanatory note

  • Illustratie uit: Pers, Dirck Pietersz. Romeynschen adelaer, waer in de loffelijcke en lasterlijcke daden der Romeynsche koningen, en keyseren, verhandelt werden, 3 delen. Utrecht: Jurriaen van Poolsum, 1689, fol. 256.

This work is about

  • Subject

  • Period

    1683

Acquisition and rights

Documentation

Persistent URL

Questions?

Do you spot a mistake? Or do you have information about the object? Let us know!