Measure approach delay
Compare traffic-aware travel time on a fixed approach segment with its normal travel time.
Mount Rainier National Park
Know the line before you reach the gate.
Experimental entrance-delay estimates, planning patterns, and community-submitted wait timers for two major approaches.
Public beta: estimates may be inaccurate or unavailable. Always verify closures, road status, and operating hours with the National Park Service.
Checking for recent observations…Checking data availability
Right now
Recent entrance estimates
High confidence
Medium
Limited data
Approach overview
Entrance conditions map
Illustrative schematic—not a measured queue map
Preliminary planning pattern
Experimental typical wait pattern
Choose an entrance and day type to view a preliminary seasonal template. It is not based on current traffic.
Recommended arrival window
Before 8:00 a.m.
Expected peak
11:00 a.m.–2:00 p.m.
Loading planning ranges…
Improve the estimate
Report your gate wait
Start the timer when you reach the back of the entrance line. Stop it after completing the gate transaction. Reports are anonymous community submissions and are not yet location-verified.
Privacy-first default
The beta stores the entrance, timestamps, duration, and an anonymous abuse-prevention identifier—not a visitor’s route. Read the privacy notice.
00:00:00
Timer has not started.
Transparent by design
How the estimate is built
Every estimate should show its age, contributing signals, and confidence—not just a single number.
Review the complete methodologySupplement with community timers
Use recent completed waits as a limited supplement to the traffic signal. Community reports never create an estimate by themselves.
Account for disruptions
Flag roadwork, crashes, closures, weather, and gate-hour changes that can mimic or alter a normal entrance queue.
Build a validated history
Collect field observations before replacing the preliminary seasonal templates with a calibrated historical model.
Questions or concerns about the calculation?
Review the full methodology and submit comments specifically about its assumptions, weights, or limitations.
Current and planned inputs
- Traffic-routing API
- Visitor wait timers
- Manual entrance-status updates
- WSDOT incidents and closures
- Weather observations