Managing authority
Government tourism / national park authorityEBC completion certificate
Everest Base Camp Trek Completion Certificate
Record a completion of Everest Base Camp Trek in Nepal with private evidence review and a premium QR-verifiable certificate.
EBCRegistry route
Image source and licence
Dole, Khumbu, Kangtega and Thamserku by Vyacheslav Argenberg, CC BY 4.0; cropped and colour-treated.
Verification application
Sign in before you start
Authentication protects your application, payment status, and private evidence. You will return to this trail after signing in or creating an account.
Trail context
A certificate grounded in the journey.
An Everest Base Camp journey is usually recorded across many walking days in the Khumbu, with acclimatisation stops, device charging gaps, changing weather, and a return itinerary that may differ from the outward trek. Evidence does not need to form one perfect uninterrupted line. Daily activity files, dated photographs at settlements and high-valley landmarks, permit or booking context, and guide confirmation can work together to show a coherent completion. State whether the record covers the route to base camp, the return, or a defined variant, and explain any helicopter or road transfer plainly. The certificate uses a Khumbu mountain landscape to recall the terrain without implying endorsement by Nepalese authorities. Raw GPS coordinates, permits, photographs, and guide correspondence remain private throughout review.
Completed Everest Base Camp Trek? Submit route-appropriate GPS tracks, activity links, dated photos, stamps, permits, guide confirmation, club confirmation, or a clear completion narrative. Route variants are assessed from the evidence provided.
Structured trail record
Authority, season and access
Official route status
Official established trekking route
Himalayan trekNormal endpoints
Lukla to Everest Base Camp
Catalogue references: 27.687, 86.731 to 28.004, 86.858Elevation range
2,610 m to 5,364 m
Rounded catalogue elevationsRecommended months
March-May · October-November
Flights, snow and monsoon weather cause disruptionsAccess requirements
National park permit and local municipality fee required
Permit/booking · Seasonal constraintsCollection and characteristics
Himalayan trek
High AltitudeTeahousesNational ParkEverest
Coordinates and elevations are rounded catalogue references for discovery only. They are not navigation-grade or emergency waypoints. Always use current official route information and an appropriate map.
Reviewed route data
Route, stages and elevation
Interactive map of Everest Base Camp Trek
120-140 km, depending on itinerary
53.67 km
4,617 m on mapped route
2,590–5,315 m
12-16 walking days
StartLuklaFinishEverest Base Camp
- 1Lukla
- 2Namche Bazaar
- 3Tengboche
- 4Dingboche
- 5Everest Base Camp
Planning summary only. Check current closures, permits, weather and official navigation sources before travel.
Why get this certificate?
Record a completion of Everest Base Camp Trek in Nepal with private evidence review and a premium QR-verifiable certificate.
Your certificate includes a premium PDF, a permanent QR verification page, registry-signed metadata, and privacy-aware public display settings.
Accepted evidence
Route-matched proof examples
- Separate daily GPS activities in walking order
- Dated photographs at settlements, bridges, high-valley landmarks, or base camp
- Permit, lodge, or itinerary records supporting dates
- Guide or expedition confirmation from a credible source
Before payment
Prepare proof that tells the whole route story.
Best evidence: GPX, FIT, or TCX files, trusted activity links, dated trail photos, stamps, permits, or guide confirmation. Photos alone may need supporting context.
Expected review level: Evidence Reviewed. Most reviews target 2–3 working days after payment and private proof upload.
Trail proof checklist
- GPS track file or activity link where available
- Photos at recognisable route landmarks
- Date range and completion narrative
- Permit, stamp, guide, club, or organiser confirmation where relevant
Distance and route variants are reviewed conservatively. Public pages never publish raw GPS points or private proof files.
Private review layer
Your proof is not your public profile.
Reviewers may see
GPS and activity files, uploaded photos, permits, stamps, guide confirmations, completion narrative, and clarification replies.
The public may see
Certificate status, trail, privacy-controlled display name, dates, verification level, issue date, fingerprint, and registry signature state.
Supported route variants
Accepted itineraries range from approximately 120 km to 140 km. The certificate must identify the completed variant or section and any transport links.
Describe acclimatisation days, side trips, return arrangements, and any helicopter or vehicle transfer. Gokyo, passes, and other materially different itineraries should be identified rather than presented as one standard route.
Prepare proof for Everest Base Camp TrekVerification levels
Evidence ReviewedPrivate completion evidence was assessed by a Verified Hikes reviewer.
GPS Evidence ReviewedA GPS file or trusted activity record formed part of the evidence review.
Photo + GPS ReviewedPhotographic context and GPS or activity evidence both supported the review.
Partner ConfirmedAn approved partner confirmed completion through a defined workflow.
Authority ConfirmedA trail authority explicitly confirmed the record through an approved workflow.
How the process works
Start verification
Create a paid application for this trail.
Upload proof
Add GPS, activity links, photos, stamps, permits, or confirmation documents privately.
Registry review
A reviewer checks evidence, dates, privacy, and verification level.
Certificate issued
Receive your premium PDF and QR-verifiable public record.
FAQ
What does the QR code prove?
It opens a safe registry page showing certificate metadata, signature status, evidence summary, and PDF fingerprint.
Request correction
See outdated trail facts? Send a correction request so the registry team can review the route record before publication changes.
Request correction/update