The Las Vegas marriage license calendar

The highest pooled weekday average is Friday, at 332.16 licenses issued per covered date. The highest calendar-day average belongs to 02-13, at 450.89. These are historical licensing patterns. Choose a month and day below to see its range, including dates that were quiet as well as dates that attracted a large number of applications.

Every date on this page is a license issue date, not a wedding date. The date picker returns the historical minimum, maximum and mean for that calendar day across the covered files. A withheld endpoint remains withheld in the tool as well as the table. The no-script table contains the same month-day values, so the calendar works as a reference even when JavaScript is unavailable. No information you choose in the picker is sent to a server.

The series runs from 2007 to 2025. The 2022 file stops on 22 December. Its missing final days do not enter the average as zero, and the table lists the years actually contributing to each calendar day in the aggregate download. Leap day also has a different set of contributing years.

Weekday averages pool the covered dates for each named weekday. Zero-license days within a file's covered range are included. This avoids describing only days when a license happened to be issued. The averages are not opening hours, staffing levels or waiting-time measurements. The Clerk's license guide supplies the official office hours and walk-in process, which should be checked before arranging a visit.

Choose a license issue date

The full historical range table is below.

Repeated-number dates

Pattern dates get their own table because a recognizable sequence can be a reason to inspect the historical record. The table includes the requested repeated-number examples, with the exact issue date next to the license count. It does not say why applicants chose that date, how many used it for a ceremony, or whether the result would repeat on a future patterned day. Those interpretations would go beyond the administrative date field.

The yearly pages show the leading daily peaks within each annual file. That view is useful when a large single-date count sits inside a year with a different overall volume. The pooled calendar answers a different question: what has this month and day looked like across the covered period? Reading the two together keeps an exceptional date visible without turning it into a normal expectation for every year.

The minimum and maximum are the endpoints of the observed daily totals. Neither says what an individual couple will experience. A low historical day can still involve a wait at a particular hour, and a large daily total does not reveal when applicants arrived. The files contain no arrival time, appointment duration or live queue. The tool is a historical reference for choosing a date to explore, not a bureau booking system.

The calendar stays countywide. It does not let a visitor combine a chosen date with a home city, exact age or marriage history. Those extra cuts would raise disclosure concerns and are unnecessary for the bureau-wide pattern. The method and downloads explain the publication floor and complementary suppression used elsewhere. Small endpoints are removed from the downloaded calendar data.

For a couple ready to arrange the paperwork, the practical sequence begins with the application and office visit described by the Clerk. The ceremony and the later certified copy are separate steps. Use the marriage certificate guide for the proof you need afterwards. Return to the overview to compare annual totals and origins once you have finished exploring a date.

The repeated-number examples record 975 licenses on 2007-07-07, 784 on 2011-11-11, and 607 on 2022-02-22. The corresponding yearly pages retain the leading issue dates within those years, including any peak that fell on another day. Reading the pattern-date count beside its annual table avoids assuming that a recognizable sequence must itself have been the busiest licensing day.

The date picker reads a local aggregate file containing the same released calendar values as the fallback table. Changing the year in the input does not request a future forecast: the lookup uses the selected month and day. The result lists the years contributing to that calendar day.