Reference

Sources and methodology

How information is collected, matched to routes and turned into warning labels.

01

How labels are derived

Every item passes through the same four stages. Source class and distance explain the record; they do not independently determine the final label.

1

Who published it?

Source class

  • Official government
  • Verified or scientific organisation
  • Weather model
  • News media (not an official notice)

The class identifies the publisher. It does not raise or lower the route label.

Source details
2

Why is it attached?

Route match

Published-area records match when a waypoint falls inside the area. Media reports match by a named trek or place.

Distance is context. A BIPAD record may match within 20 km, but only a verified severe incident within 3 km crosses its Warning threshold.
Matching details
3

How urgent is the record?

Record severity

InfoAdvisoryWarningCritical

Severity is publisher-provided or assigned from a documented live-feed threshold.

See thresholds
4

Which label appears?

TrekStatus label

  1. Closure reportedActive trail closure or permit suspension
  2. Significant warningOtherwise, an active Warning or Critical record
  3. AdvisoryOtherwise, any active record
  4. Nothing retrievedOtherwise, no active record retrieved
Label details

Live-feed reference

Current thresholds

DHM mountain wind
25–39 kt Advisory · 40–59 kt Warning · 60+ kt Critical
DHM river station
Official warning level → Warning · danger level → Critical
BIPAD incident
Advisory by default · verified severe incident within 3 km → Warning
USGS earthquake
Magnitude 4.5–5.9 → Advisory · magnitude 6+ → Warning
News media
Disruption wording → Advisory · specified strong wording → Warning

Coloured 7-day weather-outlook highlights are separate forecast aids. They never change a trek label. Media records remain marked as media and low confidence.

Only active, non-demo records are considered, and the highest applicable rule wins. Labels are automatic scanning aids, not safety judgements or advice.

02

Where the information comes from

We collect published measurements, forecasts, notices, incident records and reports on the schedule shown below. Every item remains linked to its original source.

DHM mountaineering forecast

Twice daily

Visit source

Department of Hydrology and Meteorology wind, direction and temperature forecast for 3000 m, 5500 m, 7000 m and 9000 m in each province. Raises a wind alert on the band nearest each trek's high point.

DHM river watch (flood early warning)

Hourly

Visit source

Official gauging stations with live water level and the department's own warning and danger thresholds. Publishes a flood alert for any station at or above warning level within 60 km of a route.

DHM forecast bulletins and press releases

Every 3 hours

Visit source

National three-day forecast bulletins and press releases with their official issue time. Queued for moderator review rather than published automatically, because they are national and in Nepali.

Nepal Tourism Board travel updates

Every 6 hours

Visit source

Watches the board's latest travel updates page and captures the official wording whenever it changes, for a moderator to turn into a trek notice.

Department of Immigration permit rules

Daily

Visit source

Watches the restricted-area trekking route fee table and the trekking permit rules page, so permit changes affecting Manaslu and other controlled regions are caught.

National parks and conservation authorities

Every 6 hours

Visit source

Watches the national parks department news and press release pages and the Annapurna conservation project news page for closures, checkpoint changes and route diversions.

Open-Meteo waypoint forecasts

Hourly

Visit source

Coordinate-based weather and snowfall for every major waypoint, stored with the exact API URL it came from.

BIPAD national disaster portal (NDRRMA)

Hourly

Visit source

Nepal's official incident register. Every geocoded landslide, flood, avalanche, storm and cold-wave record within 20 km of a route is published with the authority's own verified flag, as an Advisory with its distance shown. Only a verified severe incident within 3 km of a stop escalates to a Significant warning. This is the feed that carries district-level events the weather and river networks never see.

Nepali newspaper coverage

Every 2 hours

Visit source

Reads the published feeds of The Kathmandu Post, Onlinekhabar English, Nepal News and The Rising Nepal. Keeps only articles naming both a trekking place and a disruption, and publishes them as clearly-labelled media reports that never outrank an official notice.

OpenStreetMap trail geometry

Monthly

Visit source

The mapped walking path for each trek that has one in OpenStreetMap, drawn on the trek map so the route shown is the real trail rather than a straight line between listed stops. Refreshed monthly.

USGS earthquake feed (Nepal)

Every 3 hours

Visit source

Magnitude 4.5 and above inside the Nepal box over the last 14 days, published when the epicentre is within 120 km of a route, because shaking of that size loosens slopes above trails.

03

How TrekStatus handles information

1

A source publishes something

A government notice, measurement, scientific feed or news report.

2

TrekStatus attaches it to a route

By a named place or the source's published geographic area.

3

A warning label is calculated

The highest applicable rule becomes the route label.

4

You check the original

The publisher, publication date and source link remain attached.

Warning labels are automatic scanning aids based on retrieved records. They do not decide whether a route is safe, open or dangerous.

04

How warning labels are calculated

TrekStatus checks these rules from top to bottom. The first rule that applies becomes the route label. The calculation uses active, non-demo records only.

1

Closure reported

Active trail closure or permit suspension

2

Significant warning

Otherwise, an active Warning or Critical record

3

Advisory

Otherwise, any active record

4

Nothing retrieved

Otherwise, no active record retrieved

A record's severity may be stated by its publisher or assigned from a documented live-feed threshold, such as a published river level or wind band. Source type and geographic matching are shown separately and do not change the label rule.

Critical weather, river, earthquake and media records can produce a Significant warning, but never Closure reported. Only an actual trail closure or permit suspension notice can do that.

05

Source hierarchy

Official government

DHM weather and hydrology, Nepal Tourism Board, Department of Immigration, national park and conservation authorities

Provides official notices, published measurements and forecasts. An official closure label appears only when the source publishes a closure or permit suspension.

National disaster register (BIPAD)

Every geocoded landslide, flood, avalanche and storm recorded by the disaster authority

Matched by published location. The record's stored severity may affect the automatic warning label, but it does not establish the condition of the trail.

Scientific and verified organisations

TAAN, Himalayan Rescue Association, USGS earthquake feed, registered operators

Kept visibly separate from government notices. Its stored severity may affect the automatic warning label.

Weather models

Open-Meteo coordinate forecasts for each waypoint

Shown as model output, never as an observation from the trail.

News media

The Kathmandu Post, Onlinekhabar English, Nepal News, The Rising Nepal

Shown only as a media report matched by a named place. It may affect the automatic warning label, but it is never presented as an official notice or used to claim a route is open or closed.

06

Geographic matching

Each geographically published record stores its affected area: a centre point, a radius and an optional elevation band. When a record is retrieved, every trek waypoint is tested against that area. A trek is attached to the record when at least one of its waypoints falls inside it, and the matched waypoint and its distance are stored so the match can be audited.

07

Use of AI

Automated summarisation may shorten retrieved text. It may never introduce a condition, a severity or a location that is not in the retrieved record, and every summary stays attached to the source URL, publication time and retrieval time it came from.

08

Limitations and liability

  • Information may be outdated, miscategorised, or missing entirely.
  • Automated geographic matching is approximate; a nearby incident may be in another valley and not affect the trail.
  • Weather models are forecast output for a coordinate, not observations from the trail.
  • We do not verify permits, bridge conditions, track openings or local rules in person.
  • This site is provided as-is for trip planning only. You are solely responsible for verifying conditions and deciding whether to trek.