A moment is counted in minutes
This generator treats a range as a finite sequence of calendar minutes. The first minute, every minute between it and the final minute, and the final minute itself are eligible. It converts the two local date-and-time entries into timestamps, counts the inclusive minute offsets, chooses one offset, and formats the result back in the browser’s local time. Choosing by minutes matches the precision of the form and avoids pretending that a hand-entered “09:00” specifies milliseconds. It also gives each eligible minute the same chance, unlike separately choosing a random day and a random clock time when the first and last day are partial.
Inclusive range formula
Let A be the starting timestamp and B the ending timestamp, both aligned to minutes. The number of eligible values is M = floor((B − A) / 60,000) + 1. A uniform integer r from 0 through M − 1 produces A + 60,000r. The plus one is essential: from 09:00 through 09:02 there are 09:00, 09:01, and 09:02—three choices, not two. The tool rejects an end earlier than the start and caps the span at ten years, which keeps the integer range and displayed explanation practical. Daylight-saving transitions are interpreted by the browser’s local calendar.
Worked interval
Set the start to 2026-09-01 09:00 and end to 2026-09-30 17:00. September has 30 days, so the elapsed span is 29 days, 8 hours: 29 × 1,440 + 480 = 42,240 minutes. Adding the inclusive endpoint yields 42,241 eligible minutes. If the selected offset is 12,345, the browser adds 12,345 minutes to the start and displays the corresponding local date and time. The chance of any exact listed minute is 1 / 42,241, about 0.00237%. A result on September 1 at 09:00 is possible, as is September 30 at 17:00.
When a random moment is useful
Choose a random test appointment inside an agreed availability window, assign an audit sample time, pick a writing prompt timestamp, or make a fair turn order deadline for a casual game. Before using it with other people, decide the time zone, whether weekends and holidays count, and how to handle unavailable slots. This page does not consult calendars, travel time, business hours, or regional public holidays. A date-time that is mathematically eligible may still be operationally impossible. For meetings, share the selected local time with its zone rather than relying on a bare timestamp copied into another region.
Calendar edge cases
A local clock can move forward or backward at a daylight-saving change. Browsers normalize nonexistent local times, and an hour that occurs twice needs a named time zone to distinguish the two instants. For an auditable cross-border draw, use a UTC-based procedure or record an ISO timestamp with an offset; this simple local-time page is not a time-zone scheduler. Leap days are handled by the browser’s calendar parser, but an invalid entry such as February 30 must be corrected before a meaningful range exists. The tool works at minute precision, so it is unsuitable for lottery draw seconds, laboratory timing, or a security token expiry.
Why date and clock time stay coupled
The existing random date generator selects whole calendar days and can return several distinct dates; it deliberately has no clock component. The random time generator selects times of day between two clock values and does not span dates. This page combines both coordinates into one continuous interval, which is what makes 23:30 on one date through 00:30 on the next unambiguous. It is a local randomizer, not a booking system. Start, end, and the resulting moment remain in the current browser and are never submitted to DiceDecide.
Recording a selected time
Write the resulting date, clock time, and time zone in the same notation when the result will be shared. “2026-09-14 14:27 Europe/Amsterdam” is clearer than “Monday afternoon,” especially for a participant in another country. If the purpose needs an exact audit trail, also record the input endpoints and confirm that neither changed after selection. A list of excluded periods cannot be represented by one continuous interval: selecting a moment from Monday through Friday while excluding nights and weekends requires a list of eligible slots rather than this form. Do not repeatedly rerun merely because the selected time is inconvenient; either accept the rule or define a new eligible interval openly.
Distribution across calendar days
Uniform minutes do not give every date equal chance when the endpoints make days unequal. In the September example, most middle dates contribute 1,440 eligible minutes, while the opening date contributes only the minutes from 09:00 onward and the closing date only those through 17:00. That is correct for a continuous availability window: every minute receives one ticket. A “random day, then random time” procedure would instead overrepresent short endpoint days because it first grants each date equal probability. If the policy truly requires each calendar day to have equal odds, select a day separately and only then select a time from an equally defined daily window. Choose the probability model to match the rule being administered.
Civil time is a moving convention
A local timestamp is not a permanent offset from UTC. Time-zone rules can change, and the IANA time-zone database is updated so software can carry those changes. A shared selection should therefore include a location-based zone such as Europe/Amsterdam or America/Phoenix, not an ambiguous abbreviation like CST. This browser form intentionally chooses a local minute; it does not preserve a named zone beside the result or resolve a repeated wall-clock time at an autumn transition. For a cross-border audit, select from UTC instants with a system that stores the zone rule, then present each participant with a converted local time.