Why does my Apple Wallet boarding pass show the wrong time?

The pass issuer (airline or ticket provider) likely encoded the time in UTC without a proper timezone offset. Apple Wallet converts this to your device's local time zone, causing the displayed time to differ from your actual departure time.

Is the time wrong inside the pass or just on the lock screen?

Usually only the lock screen notification shows the wrong time. The time printed on the pass itself (when you open it in Wallet) is typically correct because it is stored as static text, not computed from the timestamp.

Will changing my iPhone time zone fix the Wallet time?

Not usually. The root cause is incorrect timezone encoding in the pass file itself, not your device settings. However, keeping Set Automatically enabled in Date & Time settings ensures your device does not add an extra offset.

Can I edit the time on an existing Apple Wallet pass?

Apple Wallet does not allow editing pass metadata directly. You would need to recreate the pass with correct timezone data using a pass creation app like NeatPass.

Apple Wallet Pass Shows Wrong Time Zone? Here's the Fix

Q: How does NeatPass avoid timezone problems?

NeatPass encodes the correct timezone offset in the relevantDate field when creating passes. If your boarding pass departs at 3pm Eastern Time, NeatPass writes the timestamp as the equivalent UTC time with the proper offset, so the lock screen shows the right time regardless of where you are.

Your boarding pass says the flight leaves at 3pm, but the lock screen notification says 10am. Or your concert ticket shows the wrong start time after you traveled to a different time zone. This is one of the longest-running issues in Apple Wallet, dating back to the original Passbook app in 2012.

The problem is not your iPhone. It is how pass creators encode time data inside the pass file. Most airlines, event platforms, and ticket providers get timezone handling wrong, and Apple Wallet has no built-in way to correct it.

What the Timezone Bug Looks Like

The symptoms depend on the type of pass and how far you are from the original timezone. Here are the most common scenarios.

Boarding pass off by hours

Lock screen shows departure time 3, 5, or even 8 hours earlier or later than the actual flight

Event ticket after traveling

Concert or game time shifts when your iPhone adjusts to a new timezone at your destination

Train pass with wrong boarding time

Notification suggests boarding 1 hour before or after the correct departure

Movie or show ticket confusion

Screening time on the lock screen differs from the time printed on the ticket itself

This has caused real missed flights

Users have reported missing trains and nearly missing flights because they trusted the lock screen time instead of checking the actual pass. Always verify your departure time inside the pass itself or with the airline directly.

Why Apple Wallet Shows the Wrong Time

Every Apple Wallet pass is a .pkpass file. Inside that file, a field called relevantDate tells Wallet when to surface the pass on your lock screen. This field uses the W3C timestamp format, which supports timezone offsets.

The correct format looks like this: 2026-06-15T09:30:00-04:00 (9:30am in US Eastern Daylight Time). But many pass creators write it as 2026-06-15T09:30:00Z, where the Z means UTC (Coordinated Universal Time). Wallet then converts that UTC time to your local timezone.

If the pass creator meant 9:30am Eastern but wrote it as 9:30am UTC, someone in New York sees a lock screen notification for 5:30am. Someone in Mumbai sees 3:00pm. The actual pass content (the printed boarding time) stays correct because it is stored as plain text, not computed from the timestamp.

This issue has been reported with Amtrak, IndiGo Airlines, Porter Airlines, National Express, Cineplex, and many other providers. Apple Community threads about it go back to 2012, the year Passbook launched.

A technical detail for the curious

Apple Wallet supports different pass types (boarding passes, event tickets, generic passes), and each type uses relevantDate differently. Learn more about pass types and how Wallet handles them.

Lock Screen Time vs. Pass Time

There is an important distinction. The lock screen notification time and the time printed on the pass come from different places. The notification time is calculated from the relevantDate timestamp. The printed time is static text set by the pass creator.

This is why you often see the correct time when you open the pass in Wallet, but the wrong time on your lock screen. The pass itself is fine. The notification is the problem.

If your pass is not showing on the lock screen at all, that is a separate issue. Check the guide on lock screen widgets and pass notifications for troubleshooting.

Fix timezone issues by creating passes with correct time data

NeatPass makes it easy to convert any ticket, pass, or loyalty card to Apple Wallet.

Try NeatPass Free

How to Fix or Work Around It

Since the root cause is in the pass file itself, there is no iPhone setting that fully fixes this. But these steps can help.

Verify your time settings

Go to Settings, then General, then Date & Time. Make sure Set Automatically is turned on. This will not fix a badly encoded pass, but it prevents your device from adding an extra offset.

Delete and re-add the pass

Open the pass in Wallet, tap the three-dot menu, and choose Remove Pass. Then re-add it from the original email or app. Some providers update the timezone encoding when you re-download.

Contact the pass issuer

Airlines and ticket providers can fix the timezone encoding on their end. This is the only permanent fix for passes issued through their system. Mention that the relevantDate field uses UTC instead of the local timezone.

Recreate the pass with correct timezone data

If the issuer will not fix it, you can extract the barcode and create a new pass with the correct timezone offset. NeatPass handles this automatically when you scan a boarding pass or ticket barcode.

Recreated passes work offline just like the originals. Learn more about offline mode and how passes work without internet.

Timezone Tips for Travelers

If you travel frequently across time zones, the timezone issue can affect you more than most. Here is what to keep in mind.

Crossing time zones mid-trip

Your iPhone updates its timezone automatically when you land. If a boarding pass for your connecting flight was encoded in UTC, the lock screen time will shift by the timezone difference. Always open the actual pass to verify the real departure time before heading to your gate.

International flight boarding passes

If your airline only gives you a PDF boarding pass, you can convert it to a Wallet pass with the correct timezone. See the guide on converting PDF boarding passes to Apple Wallet.

Event tickets in another city

For tips on managing event passes, see adding concert tickets to Apple Wallet.

Add a note to your pass

When creating passes with NeatPass, you can add the correct local time in the pass description or title as a reminder. Learn how to customize your pass design and fields.

How NeatPass Handles Timezones Correctly

NeatPass encodes the correct timezone offset when creating passes. If your boarding pass departs at 3pm Eastern Time, NeatPass writes the timestamp with the proper UTC offset so the lock screen notification displays the right time, no matter where you are.

Correct timezone encoding

Every pass includes the proper timezone offset in the relevantDate field, not just raw UTC

Editable pass dates

If a time is wrong, you can update the relevant date and timezone directly on the pass

On-device processing

Your boarding pass and ticket data never leaves your phone during conversion

Works offline after creation

Created passes are stored in Apple Wallet and work without internet, even across timezones

Getting started is simple. See the guide on adding your first pass to Apple Wallet.

Common Questions

Create passes with correct timezone data

Download

The Right Time on Your Lock Screen

The Apple Wallet timezone issue is frustrating because it looks like a bug in your iPhone, but it is actually a problem with how pass creators encode their data. The good news is that the barcode and ticket always work correctly. The bad news is that Apple cannot fix what pass issuers get wrong.

NeatPass solves this by encoding the correct timezone offset every time you create a pass. Your lock screen shows the right time, your pass works offline, and your data stays on your device. Learn more about how NeatPass handles your data.