Canada Event Spot
Menu

Around the venue

Named places within a few minutes' walk, from OpenStreetMap. We hold a name, an address and a distance for each and nothing more, so opening hours and prices are worth checking with them.

Places to eat and drink

Places to stay

All places to eat in Montréal · where to stay · Montréal events

Places from OpenStreetMap contributors, under the ODbL.

Upcoming events at Chalet du parc du Pélican

Within two kilometres

Places to visit near Chalet du parc du Pélican

Parc du Pélican

Longueuil, QC 1.5 hr 0.1 km away

Park in Montreal (Quebec, Canada)

Parks & Nature 116 events nearby

Place Pierre-Falardeau

Montréal, QC 1.5 hr 0.2 km away

Park in Montreal (Quebec, Canada)

Parks & Nature 120 events nearby

Parc Ludmilla-Chiriaeff

Longueuil, QC 1.5 hr 0.9 km away

Park in Montreal, Quebec, Canada

Parks & Nature 267 events nearby

Parc Jean-Duceppe

Longueuil, QC 1.5 hr 0.9 km away

Park in Montreal, Quebec, Canada

Parks & Nature 234 events nearby

Parc Mia-Riddez-Morisset

Longueuil, QC 1.5 hr 0.9 km away

Park in Montreal, Quebec, Canada

Parks & Nature 234 events nearby

About Chalet du parc du Pélican

What events are on at Chalet du parc du Pélican?

Everything this site holds for Chalet du parc du Pélican is listed on this page, soonest first, collected from official municipal and regional calendars and refreshed daily. Each listing links back to the calendar it came from.

Where is Chalet du parc du Pélican?

Chalet du parc du Pélican is at 2590 Rue Masson, Montréal, QC.

What else is there to do near Chalet du parc du Pélican?

This page lists the museums, parks, galleries and landmarks within two kilometres of Chalet du parc du Pélican, each with its own page. They are the same places that appear on the Montréal places-to-visit listing.

Where this page comes from

  • Events — the official municipal and regional calendars this site crawls. Each listing links back to the calendar it came from; every source is listed here.
  • Corrections — if something here is wrong, tell us and it gets fixed at the source rather than patched on this page.