Converting Bikram Sambat (BS) to AD for IP Deadlines

Two calendars, one deadline

Bikram Sambat is Nepal's official calendar — used in statutes, official notices, the Industrial Property Bulletin and Departmental correspondence. It is a solar calendar like the Gregorian, with a new year in mid-April (Baisakh 1), twelve months of unequal, year-varying lengths, and a year number roughly 56 years 8 months ahead of AD (2083 BS spans 2026/27 AD).

The unequal months are the practical trap: BS month lengths change from year to year, so there is no fixed formula — 'add 56 years, 8 months' is an approximation, not a conversion. Real conversion is a calendar lookup, which is why converters (and the good habit of double-checking them) matter.

• BS ≈ AD + 56y 8m — an approximation, never a calculation
• Month lengths vary by year: conversion is lookup, not arithmetic
• Every date that enters your docket should exist in both forms

Where conversion actually goes wrong

The failures cluster in four places, all seen in practice:

• The publication date misread — an opposition window counted from a Bulletin date converted carelessly loses days at the month boundary; ninety days shrinks to eighty-eight and nobody notices until it matters
• The anniversary slip — a registration date in BS transcribed as AD wholesale (2083/05/12 read as 2083, or month/day transposed) puts the whole renewal calendar months off
• The holiday collision — a deadline landing on a BS-calendar public holiday (which AD calendars don't show) extends to the next working day; deadline systems that don't know the Nepalese holiday calendar miscalculate the true final day
• The double conversion — a date converted twice or recorded in both systems without labels, leaving the file with two 'deadlines' that are the same day six weeks apart

The habits that keep deadlines safe

The professional practice is unglamorous and effective: convert on receipt — every BS date in a Departmental document is converted to AD the day the document arrives; record both — dockets store the BS original and the AD working date, labelled; use a tool — conversion is a lookup, so let a converter do it, and verify critical dates with a second source; diarise early — internal deadlines sit a week before the legal deadline, absorbing conversion uncertainty and holiday surprises; know the holidays — Nepalese public holidays (a long Dashain–Tihar season among them) are part of the true deadline map.

And one habit above all: treat any date you did not convert yourself as unverified. Deadline disasters in Nepalese IP are almost never arithmetic errors — they are transcription habits.

The tools that do it for you

IP Watch Nepal's deadline tools work in both calendars natively: the BS ↔ AD converter for one-off dates, the Opposition Countdown for publication windows, and the Renewal Deadline Calculator for term anniversaries and grace periods — all producing AD dates your commercial calendar can trust, with the BS original retained. The tools encode the holiday-adjusted working-day logic so the deadline you diarise is the one the Department will apply.