Managing authority
Trail association / local authoritiesLW completion certificate
Lycian Way Completion Certificate
Record a completion of Lycian Way in Turkey with private evidence review and a premium QR-verifiable certificate.
LWRegistry route
Image source and licence
Lycian Way 1 by Maurice07, CC BY-SA 3.0; cropped and colour-treated. Derived visual assets are licensed CC BY-SA 3.0.
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.
The Lycian Way combines Mediterranean coast, limestone slopes, pine forest, villages, historic sites, and many optional lines rather than one rigid modern route. Evidence should make the walked sections and timing understandable without treating every published variant as mandatory. GPS activities, dated photographs at landscape or settlement landmarks, accommodation records, and a concise explanation of transfers can support a continuous or section-based claim. Note road links, seasonal access changes, and any skipped portion plainly. The certificate draws on turquoise coast and rugged limestone terrain so it recalls the trail's distinctive setting without reproducing protected marks or archaeological branding. Exact tracks, accommodation details, original photographs, and private travel information remain accessible only to authorised reviewers and are excluded from the certificate's public verification payload.
Completed Lycian Way? 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
Officially promoted cultural route
Cultural trailNormal endpoints
Fethiye to Geyikbayırı / Antalya
Catalogue references: 36.621, 29.116 to 36.877, 30.464Elevation range
0 m to 1,811 m
Rounded catalogue elevationsRecommended months
March-May · September-November
Summer heat and wildfire restrictions possibleAccess requirements
Some archaeological sites charge entry; water planning required
Seasonal constraintsCollection and characteristics
Cultural trail
MediterraneanRuinsVillagesCoastal Mountains
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
approximately 760 km for the current route edition
Approx. 18,000 m
25-35 walking days
StartFethiyeFinishGeyikbayırı / Antalya
- 1Fethiye
- 2Faralya
- 3Kalkan
- 4Kas
- 5Olympos
- 6Geyikbayiri
Planning summary only. Check current closures, permits, weather and official navigation sources before travel.
Why get this certificate?
Record a completion of Lycian Way in Turkey 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
- GPS tracks for each walked coastal or inland section
- Dated photographs at recognisable landscape, village, or historic-site approaches
- Accommodation or transport records that clarify stage order
- A route narrative identifying alternatives, road links, and skipped sections
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
The current authority edition is approximately 760 km; older editions were materially shorter. The certificate must identify the completed edition and any transport links.
Name the sections and coastal or inland options used. Explain road transfers, seasonal diversions, and discontinuities; request a section record when the evidence covers only part of the route.
Prepare proof for Lycian WayVerification 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