[Regions](/regions/) › [Hohe Tauern](/regions/hohe-tauern-west/) › Poldis Jausenstation [Open in the HutScanner map](/app?region=hohe-tauern-west&hut=hut_osm_node_837805909)

# Poldis Jausenstation

1489 m · [Hohe Tauern](/regions/hohe-tauern-west/) · AT

We hold no calendar and no booking contact for this hut yet. We do read 42 huts in the Hohe Tauern network daily.

Poldis Jausenstation is an alpine hut at 1489 m in the Hohe Tauern, AT.

## How to book

You book Poldis Jausenstation directly with the hut. HutScanner is a planning tool and does not take bookings or hold beds.

See [the Hohe Tauern region guide](/regions/hohe-tauern-west/) for how huts here take bookings.

[Plan a route from this hut](/app?region=hohe-tauern-west&hut=hut_osm_node_837805909)

[See the whole Hohe Tauern network](/regions/hohe-tauern-west/)

## About Hohe Tauern

323 huts connected by 1283 walking routes in the Hohe Tauern massif.

## Planning a route through Poldis Jausenstation

Booking one hut is the easy half. The work is the chain: every night needs a bed, at a hut you can walk to from the one before, on consecutive dates, and one full night sends you back to the start. Poldis Jausenstation has no onward hut within a day's walk in our Hohe Tauern network, so it is a base or an out-and-back rather than a link in a chain; the other 322 huts in the network are searchable as chains.

Poldis Jausenstation takes bookings by phone or email rather than through a calendar HutScanner can read, so a route through it is planned around the 42 huts in Hohe Tauern that do publish one, and this night is arranged with the hut directly. [Plan a multi-night route from Poldis Jausenstation](/app?region=hohe-tauern-west&hut=hut_osm_node_837805909).

If you plan trips through ChatGPT or Claude, they can run this same search for you without opening the app, over the regions HutScanner has reviewed by hand. How that works is described in [using HutScanner with AI assistants](/guides/ai-assistants-and-hutscanner/), and the endpoint is documented in the [OpenAPI spec](/api/openapi.json).
