How to Make 2016 Better After a Rough 2015 in Nepal

✈️ The First Morning in Kathmandu, October 2015

I sat on a cracked concrete step outside a shuttered teahouse in Thamel, watching dust rise in slow spirals under weak morning light. My backpack leaned against my thigh like an uncooperative companion. A man swept broken bricks into a pile with a broom made of twigs—no motor, no machine, just rhythm and resignation. That was Nepal in late 2015: not broken, but breathing shallowly. If you’re planning travel to Nepal after a rough year—especially post-2015 earthquake—you need to know this: recovery wasn’t linear, infrastructure wasn’t restored overnight, and the most reliable travel resource wasn’t a guidebook or app—it was patience, local conversation, and knowing where to look for quiet resilience. How to make 2016 better after a rough 2015 in Nepal starts with understanding that ‘better’ doesn’t mean returning to pre-2015 conditions—it means traveling with grounded expectations, adaptive logistics, and respect for what communities were rebuilding—not just roads or temples, but routines, trust, and economic lifelines.

🌍 The Setup: Why I Went in November 2015

I’d booked the trip in March—before the 7.8-magnitude earthquake struck on April 25. My plan was simple: trek the Annapurna Circuit, spend ten days in Kathmandu documenting street-level cultural shifts for a long-form travel journal, then volunteer three weeks with a rural education NGO near Pokhara. By June, everything had changed. Flights were canceled. Hotels suspended bookings. Friends asked if I was still going. I paused—but didn’t cancel. Not because I thought it was ‘safe’ or ‘easy,’ but because I’d spent years reporting on post-disaster travel ethics, and I knew data gaps widened when outsiders stopped showing up. Official reports cited over 8,000 deaths, 22,000 injuries, and damage to more than 600,000 homes 1. But no report captured how a baker in Bhaktapur measured time now—not by sunrise, but by whether his oven had enough firewood to bake 30 loaves instead of 12.

I arrived on November 4, 2015—six months after the quake, two months before monsoon’s final retreat, and one week before Dashain, Nepal’s largest festival. The airport smelled of damp wool and diesel fumes. Customs officers stamped passports without eye contact. A taxi driver named Rajan charged me 800 NPR (≈$7.50) to Thamel—same rate as pre-quake, though his rearview mirror hung by tape and his spare tire was lashed sideways with rope. He didn’t complain. He just said, ‘We fix what breaks. Then we wait for the next thing to break.’

🌄 The Turning Point: When the Map Stopped Working

The first real rupture came on Day 3—not with rubble, but silence. I’d mapped a day walk from Swayambhunath to Kirtipur using a 2013 OpenStreetMap export. GPS worked fine. But the footpath I expected—a narrow stone lane lined with prayer flags and terracotta roof tiles—was gone. In its place: a landslide scar, raw red earth exposed like a wound, bisected by a temporary bamboo bridge strung with fraying nylon cord. No signposts. No detour markers. Just two children sitting cross-legged on a boulder, eating roasted corn, watching me hesitate.

I asked one boy, maybe nine years old, where the path went. He pointed—not forward, but diagonally uphill, behind a leaning brick wall plastered with faded Bollywood posters. I followed. The ‘path’ was less trail and more sequence: duck under rebar, step across stacked sandbags, climb three uneven concrete steps poured by hand, then follow a clothesline strung between two half-collapsed houses. At the top, an old woman offered me turmeric tea in a chipped enamel cup. She didn’t speak English. She held up three fingers, then tapped her temple. I understood: Three ways up. One way down. You chose right.

That moment rewired my approach. My guidebook—the one I’d carried since 2012—hadn’t been wrong. It was obsolete. Not inaccurate, but temporally irrelevant. What I needed wasn’t updated coordinates. It was contextual navigation: learning to read micro-signs (a freshly painted door number, a new blue tarp over a roof, a cluster of empty plastic water bottles outside a shop) as indicators of functional recovery. And it meant accepting that ‘getting there’ wasn’t about speed or efficiency—it was about noticing who was rebuilding, how, and at what cost.

🤝 The Discovery: Who Held the Map

I met Sunita on Day 7, outside the Patan Museum’s eastern gate. She wore a faded green shawl and carried a notebook bound in duct tape. She wasn’t a guide. She was a community mapper—part of a volunteer collective called Samriddhi Maps, training residents in Kathmandu Valley to document damaged infrastructure using low-tech methods: paper grids, color-coded stickers, oral histories recorded on donated smartphones 2. Her map wasn’t digital. It was pinned to a plywood board in her living room in Lalitpur—hand-drawn, laminated with clear packing tape, annotated in Nepali and English.

She showed me how to distinguish between ‘temporary repair’ (a road patched with gravel and tar, often washed away in rain) and ‘reconstruction’ (stone foundations laid, steel reinforcement visible, official signage posted). She taught me to ask not ‘Is this open?’ but ‘Who repaired this last month?’—because the answer told me whether labor was local, paid, and ongoing. She introduced me to Bishnu, a carpenter whose workshop doubled as a shelter for displaced families. His new windows used salvaged glass from collapsed heritage buildings—each pane slightly warped, each frame reinforced with recycled rebar. He didn’t call it ‘upcycling.’ He called it ‘not wasting what still holds air.’

One afternoon, Sunita took me to a school in Kirtipur where students were painting murals over cracked walls. Not slogans or slogans about hope—but diagrams: water filtration systems, earthquake-resistant roof trusses, solar panel wiring. A 14-year-old girl named Anjali explained, ‘We draw what we’ll build. So we remember how.’ Her brush moved with certainty. No hesitation. That mural wasn’t art therapy. It was technical literacy in pigment form.

🚌 The Journey Continues: From Thamel to Upper Mustang

I didn’t trek Annapurna. Not in November. Landslides had blocked the main trail between Ghorepani and Poon Hill for 47 days straight. Instead, I took a bus to Pokhara—three hours instead of the usual two—then hired a local driver named Hari to take me along the ‘back route’ to Jomsom: dirt roads bypassing landslide zones, passing through villages where schools operated in tents and health posts ran on solar-charged batteries. Hari drove slowly, stopping every few kilometers to check bridges built from salvaged timber and wire cable. He kept a logbook—not of mileage, but of which households had received reconstruction grants, which hadn’t, and which were waiting for land-title verification before rebuilding could begin.

In Jomsom, I stayed at a guesthouse run by a woman named Lhamo. Her lodge had no running water—water came in 20-liter jerrycans hauled up by mules twice daily. Electricity lasted four hours each evening, powered by a single solar array shared with three neighboring homes. But her kitchen served dal bhat with lentils cooked in a pressure cooker she’d bartered for with a teacher in Kagbeni: two English lessons for one week of fuel-efficient cooking. She kept receipts taped to her cupboard door—not for accounting, but to show guests exactly where their money went. ‘You pay 350 NPR. 180 goes to rice and lentils. 90 to firewood. 50 to my daughter’s school fee. 30 is for soap. I write it so you know your rupees are not lost.’

From Jomsom, I walked north—not to Lo Manthang, but to a smaller village called Tangbe, where elders had revived a centuries-old irrigation system using stone channels diverted around new landslide scars. They didn’t wait for engineers. They surveyed slopes by walking them at dawn, noting where dew pooled longest—indicating stable ground—and redirected flows accordingly. No GPS. No drone. Just observation, memory, and consensus.

🌅 Reflection: What This Taught Me About Travel—and Myself

I used to think ‘responsible travel’ meant minimizing footprint. In Nepal that fall, I learned it meant maximizing attention—not to monuments or vistas, but to process. To watch how a woman balanced a basket of bricks on her head while reciting multiplication tables with her daughter. To notice how a shopkeeper reset his scale every morning with a stone he’d kept since childhood—not because it was accurate, but because it was consistent. These weren’t anecdotes. They were operating systems: low-tech, high-resilience frameworks for continuity amid disruption.

My own assumptions unraveled gradually. I’d packed emergency rations, satellite messengers, and backup power banks—all useless when the real bottleneck wasn’t gear failure, but information latency. News traveled slower than rumor. Official updates lagged local reality by days—or weeks. What mattered wasn’t having the latest data, but knowing who had the freshest eyes on the ground. I stopped checking weather apps and started asking tea-sellers whether clouds gathered over Phulchowki Mountain at noon—that told me more about afternoon rain than any forecast.

I also misjudged time. I’d planned ‘flexible’ days—buffer hours for delays. But flexibility isn’t passive. It’s active recalibration: adjusting sleep schedules when generators cut power at midnight, rewriting itinerary notes in pencil instead of ink, carrying cash in small denominations because ATMs failed unpredictably. I learned to measure progress not in kilometers covered, but in conversations sustained: the number of times I repeated a Nepali phrase until pronunciation clicked, the number of shared meals where silence felt companionable, not awkward.

💡 Practical Takeaways: Woven, Not Listed

Traveling Nepal in early 2016—still deep in recovery—meant adapting to rhythms that didn’t match pre-2015 templates. Here’s what worked, tested not in theory but in mud, dust, and intermittent Wi-Fi:

• Transport isn’t just about mode—it’s about timing. Buses left when full, not on schedule. But drivers often shared departure estimates verbally: ‘When the third truck passes the blue gate, we go.’ Learning those informal cues saved more time than any app.
• Accommodation required verification on arrival. Listings marked ‘open’ online sometimes referred to structural integrity—not operational status. I started calling ahead using local SIM cards (NTC worked best in valleys; Ncell had stronger signal in hills), but always confirmed again at the door: ‘Do you have water tonight? Do you have light after dark?’
• Food security was localized. In Kathmandu, restaurants reopened fast. In remote areas, kitchens operated only when supply trucks arrived—which varied by road condition, not calendar. I carried dried fruit and roasted soybeans, not as emergency rations, but as trade items: exchanged for boiled potatoes or a seat near the hearth on cold nights.
• Documentation mattered differently. My visa extension paperwork required proof of accommodation—but landlords provided handwritten letters on lined paper, signed with thumbprints. Officials accepted them. What they rejected were glossy PDFs printed abroad. Local context over global format.

⭐ Conclusion: How This Trip Changed My Perspective

I left Nepal in January 2016 with fewer photographs and more annotations—in margins of maps, on napkins, in voice memos dictated while riding buses. I didn’t ‘see’ more. I witnessed differently. The earthquake hadn’t erased Nepal’s texture—it had intensified it. Cracks in walls revealed older brickwork beneath plaster. Abandoned shops became impromptu classrooms. Silence in a marketplace wasn’t emptiness—it was space held for something else to grow.

What made 2016 better wasn’t restoration. It was recalibration: learning to travel not as a consumer of experiences, but as a participant in continuity. I stopped asking ‘What’s open?’ and started asking ‘What’s being remade—and how can I move alongside it?’ That shift didn’t make travel easier. It made it truer. And truth, I found, is the most durable currency in places rebuilding themselves—one repaired roof, one redrawn map, one shared cup of tea at a time.

❓ FAQs: Practical Questions from the Field