Skip to main content

Route

Jyvaskylan Maalaiskunta → Tampere

JYVJyvaskylan MaalaiskuntaJyväskylä Airport
TMPTampereTampere-Pirkkala Airport
Distance
96 mi
Estimated flight time
~40m

Same local time in Jyvaskylan Maalaiskunta and Tampere.

No nonstop connection observed

Our route data contains no observed nonstop flight from Jyvaskylan Maalaiskunta to Tampere. That does not rule out a one-stop journey; see the direct destinations of Jyvaskylan Maalaiskunta for the options.

About this route

  • Domestic route: both airports are in the same country.
  • Direct destinations observed from Jyvaskylan Maalaiskunta: 1.
  • Direct destinations observed from Tampere: 4.

The airports on this route

Jyväskylä Airport

Jyvaskylan Maalaiskunta, FinlandJYV / EFJY

Regional airport · 1 direct destinations · 1 runway · longest runway 8,533 ft

50 °F · RainSource: METAR observation via the NOAA Aviation Weather Center

Tampere-Pirkkala Airport

Tampere, FinlandTMP / EFTP

Regional airport · 4 direct destinations · 1 runway · longest runway 8,858 ft

52 °F · RainSource: METAR observation via the NOAA Aviation Weather Center

Alternative airports for this journey

Same journey, a different airport nearby - with an observed direct connection.

About the route from Jyvaskylan Maalaiskunta to Tampere

The distance between Jyväskylä Airport (JYV) and Tampere-Pirkkala Airport (TMP) is approximately 96 mi; no direct connection has been observed in our route data.

Frequently asked questions about this route

How far is Jyvaskylan Maalaiskunta from Tampere by air?
The great-circle distance between Jyväskylä Airport and Tampere-Pirkkala Airport is approximately 96 mi.
Is there a direct connection from Jyvaskylan Maalaiskunta to Tampere?
No direct connection between JYV and TMP has been observed in our route data. That does not rule out a one-stop journey.
What is the current time difference between Jyvaskylan Maalaiskunta and Tampere?
Same local time in Jyvaskylan Maalaiskunta and Tampere.

Where this data comes from

The route data comes from the flight archive (ADS-B, adsb.lol): which connections actually flew over the last twelve full months and who flew them, combined with our own airport, runway, and airline datasets. It is reference data about observed routes - not a current timetable and no claim about bookability.

The flight archive of the last twelve months has nothing for this route, so we say nothing about frequency.

Route data updated on October 11, 2026.