Clock Angle Calculator
Calculate the angle between clock hands at any time with a visual clock face and step-by-step math.
Last reviewed: April 2026New to this tool? Click here for instructions
Step-by-step:
How to use the Clock Angle Calculator
To use the Clock Angle Calculator, enter a time in the format of hours (1-12) and minutes (0-59). Click 'Now' to use the current time or 'Calculate' to find the clock hand angle. The visual clock and both angles (acute and reflex) will update instantly with step-by-step math.
When to use the Clock Angle Calculator in real workflows
The Clock Angle Calculator is useful for math problems and coding interviews, where you need to calculate the angle between clock hands. It's also a great tool for practicing mental calculation skills and competing with others to get the closest answer.
How the Clock Angle Calculator works
The calculator uses the angular velocities of both hands to calculate the angle between them. The minute hand moves at 6 degrees per minute, while the hour hand moves at 0.5 degrees per minute.
Tips, edge cases, and limitations
The hour hand is never stationary and continuously advances as minutes pass. The clock angle problem requires the ability to translate a real-world problem into a mathematical model and handle edge cases.
Frequently Asked Questions
Find the precise angle between the hour and minute hands at any time — to the nearest tenth of a degree. Whether you're checking your work for LeetCode 1344, preparing for a technical interview, or just curious what angle your wall clock shows right now, this calculator accepts hours, minutes, and optional seconds and returns both the primary angle and its reflex counterpart.
What This Tool Does
Enter any time in H:MM:SS format (seconds are optional) and the calculator returns two values: the smaller angle between the hands — acute, right, or obtuse — and the reflex angle, which is 360° minus the primary. Results are decimal degrees, making them directly usable in code or further calculations. The tool normalizes 24-hour input automatically (15:00 resolves to the same face position as 3:00) and handles the classic edge cases that trip up interview candidates, including midnight, noon, and the continuously moving hour hand. If you've encountered LeetCode 1344 "Angle Between Hands of a Clock", this tool is the interactive reference for it.
How to Use It
Step-by-step input instructions
- Enter the hour in the first field (0–23 accepted; values above 12 are reduced automatically).
- Enter minutes in the second field (0–59).
- Enter seconds in the third field if you need sub-minute precision (0–59); leave it at 0 otherwise.
- Click Calculate or press Enter. The clock face updates and the angle boxes below populate immediately.
- Read the primary angle (the smaller arc between the hands) and the reflex angle (the larger arc).
- Use the Copy button to grab the result as plain text for pasting into a document or code comment.
Try Example button walkthrough
Clicking Try Example pre-fills the inputs with 3:15:30 — a deliberately tricky time because the hands look almost coincident yet differ by 4.75°. The step-by-step breakdown shown below the result walks through exactly how that number is reached, which is useful for verifying your own hand-calculation before a coding round.
Step-by-Step Formula Breakdown
Hour hand position
The hour hand completes one full revolution in 12 hours, which equals 720 minutes. Dividing 360° by 720 minutes gives 0.5° per minute. It moves 30° per hour mark and an additional 0.5° for each elapsed minute within that hour. Including seconds, it advances another 1/120° per second (since 60 seconds make one minute, and one minute contributes 0.5°).
hour_angle = (H % 12) * 30 + M * 0.5 + S * (1/120)Minute hand position
The minute hand completes one revolution every 60 minutes, so it moves 6° per minute. At the sub-minute level it covers 0.1° per second (6° ÷ 60 seconds).
minute_angle = M * 6 + S * 0.1Combining for the final angle
Take the absolute difference of the two positions, then clamp to the smaller of the two possible arcs:
diff = |hour_angle − minute_angle|
angle = min(diff, 360 − diff)Accounting for seconds
Without the seconds term, the result for 3:15:30 would be 7.5° — the classic 3:15 answer. Adding 30 seconds modifies both hands: the hour hand shifts by +0.25° and the minute hand by +3.0°, closing the gap to 4.75°. Interview problems typically omit seconds, but this tool includes them for real-world accuracy.
Working through 3:15:30 in full:
- Normalize: 3 % 12 = 3
- Hour hand: 3 × 30 + 15 × 0.5 + 30 × (1/120) = 90 + 7.5 + 0.25 = 97.75°
- Minute hand: 15 × 6 + 30 × 0.1 = 90 + 3.0 = 93.00°
- Difference: |97.75 − 93.00| = 4.75°
- Final: min(4.75, 355.25) = 4.75°
Worked Example — 3:15:30
- Input
- Time: 3 hours, 15 minutes, 30 seconds
- Normalize hours: 3 % 12 = 3
- Hour hand angle: 3 × 30 + 15 × 0.5 + 30 × (1/120) = 90 + 7.5 + 0.25 = 97.75°
- Minute hand angle: 15 × 6 + 30 × 0.1 = 90 + 3.0 = 93.00°
- Raw difference: |97.75 − 93.00| = 4.75°
- Apply min(): min(4.75, 360 − 4.75) = min(4.75, 355.25) = 4.75°
- Report both angles: primary = 4.75° (acute), reflex = 355.25°
Expected output: Hour hand: 97.75° | Minute hand: 93.00° | Angle between hands: 4.75° | Reflex angle: 355.25°
Edge Cases and Gotchas
Hour hand is not stationary
The single most common mistake — in interviews and in code — is treating the hour hand as frozen at the hour mark. At 3:59:00, the hour hand sits at 3 × 30 + 59 × 0.5 = 119.5°, nearly halfway between 3 and 4. Forgetting the 0.5°/min term produces an answer off by up to 29.5°, which is a failing response in any technical screen.
Midnight and noon both map to 0°
Both 12:00:00 and 0:00:00 produce hour_angle = 0° and minute_angle = 0°, so the result is 0°. The H % 12 normalization handles this: 12 % 12 = 0 and 0 % 12 = 0. Use 12:00:00 and 6:00:00 as your two quick sanity checks — they should always yield exactly 0° and 180° respectively.
Reflex vs. acute angle choice
Two arcs always exist between any two clock-hand positions. Their measures sum to 360°. The primary angle reported by this tool is always the smaller one (≤ 180°); the reflex angle is 360° minus that value. Some problems specifically ask for the reflex angle, so both are displayed. Converting either to radians is straightforward with the Degree ↔ Radian Converter.
Inputs after 12:00 (13:xx, 24:xx)
Apply H % 12 before any other arithmetic. 15:30 reduces to 3:30; 23:00 reduces to 11:00. The clock face is cyclic with a 12-hour period, so any 24-hour input maps cleanly onto the equivalent 12-hour position — no special-casing required.
The Math Behind Clock Angles
Angular velocity analogy
Think of the two hands as runners on a circular track. The minute hand runs at 6°/min; the hour hand runs at 0.5°/min. The relative angular velocity — how fast the minute hand pulls away from the hour hand — is 6 − 0.5 = 5.5°/min. Every problem about clock angles reduces to one-dimensional relative motion once you accept this framing.
Why 11 overlaps, not 12, occur in 12 hours
Starting at 12:00:00 when both hands coincide, the minute hand must gain exactly 360° on the hour hand to overlap again. At 5.5°/min, that takes 360 ÷ 5.5 ≈ 65.4545… minutes, or roughly 1:05:27. Over a full 12-hour period of 720 minutes, the minute hand accumulates 720 × 5.5 = 3960° of relative gain — exactly 11 × 360°. Eleven complete relative laps means 11 overlaps. A 12th overlap would land precisely at 12:00:00, which is overlap #1 of the next 12-hour cycle, not an additional event in the current one.
Deriving overlap times algebraically
The general formula for the nth overlap (n = 0, 1, 2, … 10) is:
t_n = n × (720 / 11) minutes after 12:00:00720/11 ≈ 65.4545 minutes, confirming the roughly 65-minute spacing. The 90° events follow the same structure: hands reach 90° separation at t = 90/5.5 ≈ 16.36 min and 270/5.5 ≈ 49.09 min after each overlap, producing 22 right-angle events per 12 hours. For any target angle θ, the hands reach that separation at t = θ/5.5 and t = (360 − θ)/5.5 minutes after each overlap. For angles between arbitrary lines in 2D space rather than on a clock face, the Angle Between Lines Calculator covers that case.
| Time | Hour Hand (°) | Minute Hand (°) | Angle Between Hands (°) | Angle Type |
|---|---|---|---|---|
| 12:00:00 | 0.0 | 0.0 | 0.0 | Coincident |
| 3:00:00 | 90.0 | 0.0 | 90.0 | Right |
| 3:15:30 | 97.75 | 93.0 | 4.75 | Acute |
| 6:00:00 | 180.0 | 0.0 | 180.0 | Straight |
| 6:30:00 | 195.0 | 180.0 | 15.0 | Acute |
| 9:00:00 | 270.0 | 0.0 | 90.0 | Right |
| 9:47:00 | 293.5 | 282.0 | 11.5 | Acute |
| 12:20:00 | 10.0 | 120.0 | 110.0 | Obtuse |
| 1:05:27 | 32.73 | 32.7 | 0.0 | Coincident |
| 4:21:49 | 130.9 | 130.9 | 0.0 | Coincident |
| Overlap # | Time (H:MM:SS) | Minutes Since 12:00 | Verification (angle ≈ 0°) |
|---|---|---|---|
| 1 | 12:00:00 | 0.00 | 0° |
| 2 | 1:05:27 | 65.45 | 0° |
| 3 | 2:10:54 | 130.91 | 0° |
| 4 | 3:16:21 | 196.36 | 0° |
| 5 | 4:21:49 | 261.82 | 0° |
| 6 | 5:27:16 | 327.27 | 0° |
| 7 | 6:32:43 | 392.73 | 0° |
| 8 | 7:38:10 | 458.18 | 0° |
| 9 | 8:43:38 | 523.64 | 0° |
| 10 | 9:49:05 | 589.09 | 0° |
| 11 | 10:54:32 | 654.55 | 0° |
| Overlap | Time | Minutes Since 12:00 |
|---|---|---|
| 1 | 12:00:00 | 0.00 |
| 2 | 1:05:27 | 65.45 |
| 3 | 2:10:54 | 130.91 |
| 4 | 3:16:21 | 196.36 |
| 5 | 4:21:49 | 261.82 |
| 6 | 5:27:16 | 327.27 |
| 7 | 6:32:43 | 392.73 |
| 8 | 7:38:10 | 458.18 |
| 9 | 8:43:38 | 523.64 |
| 10 | 9:49:05 | 589.09 |
| 11 | 10:54:32 | 654.55 |
Worked Examples
Example 1 — 3:15:30
As derived above: hour hand = 3 × 30 + 15 × 0.5 + 30/120 = 97.75°; minute hand = 15 × 6 + 30 × 0.1 = 93.00°; difference = 4.75°. This one is worth memorizing because interviewers frequently use 3:15 expecting you to say "the hands are nearly on top of each other," then probe whether you account for the moving hour hand.
Example 2 — 9:47:00
Hour hand: 9 × 30 + 47 × 0.5 + 0 = 270 + 23.5 = 293.5°. Minute hand: 47 × 6 + 0 = 282.0°. Raw difference: |293.5 − 282.0| = 11.5°. Since 11.5° < 180°, no clamping needed — the angle is 11.5° and the reflex angle is 348.5°. Both hands are crowded near the 47-minute mark at 9:47, which is why the angle is small despite looking different on a clock face.
Example 3 — 6:00:00 (sanity check)
Hour hand: 6 × 30 + 0 × 0.5 = 180.0°. Minute hand: 0 × 6 = 0.0°. Difference: 180°. min(180, 180) = 180° — a straight line, as expected. If your implementation ever returns anything other than 180° for exactly 6:00:00, there is a bug in the normalization or the absolute-value step.
Real Interview Question Context
LeetCode 1344 equivalent framing
LeetCode 1344 "Angle Between Hands of a Clock" gives you integer hours (1–12) and integer minutes (0–59) with no seconds, and asks for the minimum angle as a float. The problem is rated Easy, but candidates who forget H % 12 or who use integer division on the minutes term get Wrong Answer on the hour=12 test case.
Python one-function solution pattern
def angleClock(hour: int, minutes: int) -> float:
hour_angle = (hour % 12) * 30 + minutes * 0.5
minute_angle = minutes * 6
diff = abs(hour_angle - minute_angle)
return min(diff, 360 - diff)To extend this to second-level precision, add seconds * (1/120) to hour_angle and seconds * 0.1 to minute_angle before computing the difference.
Common follow-up questions
Interviewers routinely follow up with: "Find all times in a 12-hour period when the angle equals a given target θ." The answer uses the relative-velocity relation: the hands reach separation θ at t = θ/5.5 minutes and t = (360 − θ)/5.5 minutes after each of the 11 overlap events, for up to 22 solutions. Another common follow-up: "How many times per day are the hands at exactly 180°?" — the answer is 22 per 12-hour period (and 44 per 24-hour day). Two interviewer red flags to avoid in your own solution: forgetting H % 12 (breaks input 12) and using // integer floor-division instead of floating-point arithmetic (loses all sub-degree precision).