Labskaus

Labskaus (listen ) (also spelled Lapskaus) is a culinary speciality from northern Germany and in particular from the cities of Bremen, Hamburg, and Lübeck. The main ingredients are salted meat or corned beef, potatoes, and onion. Some recipes put beetroot, pickled gherkin, or even herring into it, while others have these ingredients as side orders.[1]

Hamburg-style Labskaus with fried egg, gherkin, and rollmops

Etymology

The origin of this word is uncertain. One possible source for the name could be Latvian Labs kauss, meaning 'good bowl' or hotpot, or Lithuanian labas káušas, meaning the same.[1] The dish became common amongst sailors and seamen during the time of the great ships. Potatoes and salted meats were a standard fare and Labskaus would make a less than fresh cut of meat more palatable and stretch the meat supply. Labskaus is now commonly served in restaurants only on Germany's Northern coast, as well as in traditional Danish restaurants. Compare with (lob)scouse.

Preparation

Labskaus with fried egg

The meal is traditionally prepared by boiling the beef in broth and then mincing it with the beetroot, onions, boiled potatoes and herring (some recipes use ham). Finally the base is fried in lard, condiments as nutmeg, pepper, coriander, or allspice are added.[2]

The dish is similar to the British hash.

Countless variations of the dish exist. For example, in Bremen, 95 km away from Hamburg, Labskaus usually is a preparation of fried corned beef, onions and mashed potatoes with the beetroot and a Rollmops being served as a side dish.

Variations of the dish are also to be found in Scandinavia, generally without the use of herring. In Denmark the dish is similar to the Bremen version, but without the herring and some times with added gravy. In Sweden, Lapskojs is a stew made with beef and mashed potatoes. In Norway, the word lapskaus more often refers to a variation of beef stew often made with gravy, or in some cases other types of stew, more or less identical to the Liverpudlian scouse.

gollark: In case of the failure of Discord, I will have to manually process the reminder database and track down those who set reminders.
gollark: Anyway, to ensure reminder delivery, I should make it try:- original reminder channel- other channels on server if the original is unavailable/deleted- DMing user- DMing a random person who also set a reminder
gollark: Columns are declared in order *too*, but that really shouldn't be relied in like the python API does.
gollark: In SQLite they do actually, there's an INTEGER PRIMARY KEY rowid column unless you disable that explicitly.
gollark: Which is still HIGHLY dodecahedral and dependent on columns' order.

See also

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.