Introduction

If you need the hour and minute from an NSDate, the modern answer is to convert it through Calendar and read the relevant date components. In Swift, you will usually work with Date rather than NSDate, but the idea is the same because the two bridge directly.

Use Calendar and DateComponents

The core API is Calendar.dateComponents.

1import Foundation
2
3let date = Date()
4let calendar = Calendar.current
5let components = calendar.dateComponents([.hour, .minute], from: date)
6
7print(components.hour ?? 0)
8print(components.minute ?? 0)

If you already have an NSDate, bridge it:

let nsDate = NSDate()
let date = nsDate as Date
let components = Calendar.current.dateComponents([.hour, .minute], from: date)

That is the standard way to extract time components numerically.

Why Calendar Matters

A Date or NSDate represents an absolute point in time, not a human calendar interpretation. The hour and minute depend on calendar, timezone, and locale choices.

That is why the API requires a Calendar. Without one, there is no meaningful answer to “what hour is this” for a user-facing context.

If you need a specific timezone, set it explicitly:

1var calendar = Calendar.current
2calendar.timeZone = TimeZone(identifier: "America/Toronto")!
3
4let components = calendar.dateComponents([.hour, .minute], from: date)
5print(components.hour ?? 0)
6print(components.minute ?? 0)

Extracting Numbers vs Formatting Text

If the goal is to show 08:30 to the user, DateFormatter may be more appropriate than manual component extraction. This is an important distinction because business logic often needs numbers, while UI usually needs localized text that respects the user's 12-hour or 24-hour preference.

1let formatter = DateFormatter()
2formatter.dateFormat = "HH:mm"
3
4print(formatter.string(from: date))

Use Calendar when you need numeric values for logic. Use DateFormatter when you need a display string.

There is also a shorter API when you only need one component at a time:

let hour = Calendar.current.component(.hour, from: date)
let minute = Calendar.current.component(.minute, from: date)

That is convenient for quick extraction, while dateComponents is nicer when you need several fields at once. It also keeps related values consistent because they are computed from the same calendar context in one step.

Legacy Objective-C Style

Older codebases may still use NSCalendar and NSDateComponents directly. The logic is the same.

let calendar = NSCalendar.current
let components = calendar.dateComponents([.hour, .minute], from: date)

In modern Swift, Calendar and DateComponents are the preferred style, but they bridge cleanly with older Foundation types. If you are repeatedly extracting many components, reuse the same calendar rather than recreating it in tight loops. That keeps the intent clearer and avoids small but unnecessary setup overhead. It also makes it easier to ensure every extraction in the same code path uses the same timezone rules.

Common Pitfalls

The biggest mistake is forgetting about timezone. The same absolute date can produce different hours depending on which timezone the calendar uses.

Another mistake is using numeric components when the real need is formatted display text. A formatter is usually better for UI.

A third mistake is force-unwrapping hour or minute unnecessarily. Use safe unwrapping or defaults unless you are certain about the component set.

Summary

• Use Calendar.dateComponents([.hour, .minute], from: date) to extract hour and minute.
• Bridge NSDate to Date in Swift when needed.
• Set the calendar timezone explicitly if the result must match a specific region.
• Use DateFormatter instead when the goal is display text such as HH:mm.
• Remember that a date is an absolute instant, while hour and minute are calendar interpretations.