Passes Last checked April 3, 2026 Best when Your hotel area and Tokyo days already look...

Edited by First Days Japan editorial desk How the editorial method works Request a correction

Passes decision guide

Tokyo Subway Ticket

Broad Tokyo Subway Ticket guide for visitors: when the 24-, 48-, or 72-hour pass is real value, when hotel and airport logic break it, and when Welcome Suica is the safer default.

This transport guide still fits if

Your hotel area and Tokyo days already look compact, central, and subway-heavy.

Another guide fits better if

Your hotel area or airport day is still moving enough that route coverage...

What this page settles now

Whether coverage discipline is now strong enough for a timed subway pass.

Checked before publish

Current Tokyo Subway Ticket prices, first-use validity, sales rules, and coverage limits.

Wrong question to stop asking

Do not ask which duration is cheapest before checking hotel area, airport day, and operator mix.

Edited as a decision guide, then checked against official sources. See the editorial method and jump to the official checks below .

Pass verdict

Best starting default

Tokyo Subway Ticket is worth buying only after your hotel area and core routes are fixed enough that most useful rides stay on Tokyo Metro and Toei Subway lines inside the validity window.

Do not force it if: Avoid buying it too early if your hotel, airport route, or neighborhood list still points you toward JR or non-subway travel.

Lowest cost only if

It can be the cheapest option for a compact subway-heavy plan, but not for flexible days...

Lowest stress when

It is easiest only when the trip is already planned. Otherwise it adds one more coverage...

Transport reasoning next

1 Transport fit first
2 Purchase session next
3 Transport-fit patterns

Official product and eligibility checks come after the main comparison.

This transport guide still fits if

Your hotel area and Tokyo days already look compact, central, and subway-heavy.
You are testing whether route coverage can now beat flexibility.

Another guide fits better if

Your hotel area or airport day is still moving enough that route coverage is guesswork.
You still need the broad flexible transport default before forcing a route-limited pass.

Purchase best practice

Pick the product move that matches the hotel lane and airport day

Use the timing and scenario cards below to decide what to buy now, what to delay, and which product still fits once the airport day and first useful station pair are real.

Treat Tokyo Subway Ticket as a reward for route discipline, not as a shortcut to discipline. The best practice is to buy it only after the hotel, airport days, and dense ride block already look real.

Purchase decision order

1

Before comparing 24, 48, and 72 hours

Separate airport and JR-heavy days from the pass logic

Do not let arrival, departure, or one major JR segment distort a city-pass decision.
2

When the hotel and neighborhoods are mostly fixed

Check whether the useful station pair stays on Tokyo Metro and Toei lines

If the route keeps leaning on JR, the pass still has not earned the purchase.
3

Only after the dense block is visible

Choose the shortest duration that matches the real high-usage days

A longer pass is better only when the covered rides are already there.

Best-fit transport pattern

Dense central sightseeing block

The hotel and useful rides already stay compact, central, and subway-heavy.

Next move: Choose Tokyo Subway Ticket and match the duration to the real high-usage days.

Tradeoff: Best value only when repeated coverage checks already feel predictable.
What it protects: You turn a compact route pattern into real pass value instead of buying on hope.

Hotel or airport still leaks into JR

The route still depends on JR, airport rail, or a station pair that is not clearly subway-friendly.

Next move: Do not buy the pass yet. Step back to Welcome Suica or fix the hotel base first.

Tradeoff: Less immediate optimization, much lower chance of defending the wrong pass.
What it protects: You avoid paying for coverage discipline that the trip does not actually have.

Three calendar days look tempting

The main reason you want the 72-hour ticket is simply that the trip lasts three days on paper.

Next move: Recalculate around dense ride blocks, not calendar length.

Tradeoff: More honest planning, less screenshot-friendly neatness.
What it protects: You stop buying the longest pass just because the calendar makes it look tidy.

Purchase action pack

Pass-buying session

Prove the dense coverage block before you choose 24, 48, or 72 hours

This session should end with one defendable pass window or with a decision to step back to Welcome Suica. It should not end with a prettier screenshot than the real trip.

Settle now

1

Mark airport and JR days outside the pass

Separate arrival, departure, and obvious JR-heavy movement before you let any duration math speak.
2

Check the hotel station pair is subway-side

Make sure the base really finishes on the useful Tokyo Metro or Toei side rather than quietly leaning back toward JR.
3

Choose the shortest real dense block

Pick 24, 48, or 72 hours only after the covered rides already cluster into a believable window.

Ignore for now

72 hours because the stay spans three calendar days

Calendar length is not the same as three dense covered days.
A subway pass if Shinjuku or Shinagawa still leans on JR

A JR-leaning base can make the pass look neat while the real route keeps leaking value.
A dual setup if you still need a map to defend it

If the pass fit still needs explanation ride by ride, the trip is not ready for complexity.

Pass fit

Pick the transport-product pattern that fits the trip shape first

Match your hotel, route coverage, and airport-day logic first. Fare math can wait.

Start with the broad answer

Tokyo Subway Ticket is worth buying only after your hotel area and core routes are fixed enough that most useful rides stay on Tokyo...

Then review transport tradeoffs

You already have a compact 24-, 48-, or 72-hour subway-heavy plan

The ticket can be strong value. This pass works best when the useful rides are already visible before you buy, not when you hope the plan will somehow become subway-only later.

Your hotel area or airport route still leans on JR

Do not force the ticket. One hotel, airport, or intercity segment outside the covered network can undo the clean savings story very quickly.

Your first Tokyo days are still flexible

Start with Welcome Suica instead. A flexible IC card is usually the calmer first answer when the route pattern is not stable enough to defend a pass.

Product comparison

Fit before savings

Each card shows when the product holds, where coverage leaks, and who it fits best.

Quick fit scan

Open only the option that still looks alive after one quick scan.

1 Product 1 Coverage Best when most rides stay inside the subway network. Best for Compact subway-only plans

When it wins: Most rides stay on Tokyo Metro and Toei Subway lines
Where it breaks: The useful route keeps leaving the subway network
Best for: Compact subway-only plans

2 Product 2 Value Best when the ride count is real, not hopeful. Best for Trips with real ride-count savings

When it wins: You expect enough rides inside 24, 48, or 72 hours
Where it breaks: You buy it on hope and then underuse it
Best for: Trips with real ride-count savings

3 Product 3 Stress Best when you already know which rides are covered. Best for Travelers trading flexibility for savings

When it wins: You already understand which lines are covered
Where it breaks: You keep second-guessing whether each ride is included
Best for: Travelers trading flexibility for savings

Quick fit scan

Start here, then open only the detailed card that still looks right.

Product 1

Coverage

Best when most rides stay inside the subway network.

Best for

Compact subway-only plans

Where it breaks

The useful route keeps leaving the subway network

Product 2

Value

Best when the ride count is real, not hopeful.

Best for

Trips with real ride-count savings

Where it breaks

You buy it on hope and then underuse it

Product 3

Stress

Best when you already know which rides are covered.

Best for

Travelers trading flexibility for savings

Where it breaks

You keep second-guessing whether each ride is included

Product 1

Coverage

Best when most rides stay inside the subway network.

When it wins

Most rides stay on Tokyo Metro and Toei Subway lines

Where it breaks: The useful route keeps leaving the subway network
Best for: Compact subway-only plans

Product 2

Value

Best when the ride count is real, not hopeful.

When it wins

You expect enough rides inside 24, 48, or 72 hours

Where it breaks: You buy it on hope and then underuse it
Best for: Trips with real ride-count savings

Product 3

Stress

Best when you already know which rides are covered.

When it wins

You already understand which lines are covered

Where it breaks: You keep second-guessing whether each ride is included
Best for: Travelers trading flexibility for savings

Live product note: Tokyo Metro's official English page lists the current ticket types, eligibility, and coverage. Recheck the official page because prices and conditions can change.

Common mistake

Coverage is the whole decision

The ticket only works well when the subway network already matches the shape of your trip. Savings disappear quickly when the useful route leaves the covered lines.

Common mistake

Airport and hotel choices can break the pass logic

If your arrival route or hotel area depends on JR or another operator, do not assume the subway ticket stays elegant.

When Tokyo Subway Ticket is actually worth buying

Product truth: Tokyo Subway Ticket is a time-based pass for Tokyo Metro and Toei Subway rides. It works well only when your real movement already stays inside that network often enough.

Coverage: Tokyo Metro and Toei Subway lines only
Main promise: Time-based value for compact, subway-heavy Tokyo days
Main risk: Hotel, airport, or JR-heavy movement can break the clean savings story

For many first-time visitors, the broad answer is not which duration to buy. It is whether the pass has earned the trip at all. If your hotel lane and core days already stay compact and subway-heavy, the ticket can work well. If airport days, JR links, or a loose neighborhood plan still dominate, it is too early.

Official facts that make the pass answer more concrete

Current official prices are JPY 1,000 / 1,500 / 2,000 for 24 / 48 / 72 hours: Tokyo Metro’s current English page still lists the adult price ladder clearly, which is useful only after coverage fit is already strong enough to make duration math real.
You can buy it in advance from outside Japan or at listed airport and city sales points in Tokyo: Tokyo Metro’s current English site says the ticket can be purchased through travel agencies in certain countries or at airports and subway stations in Japan. That matters because the pass is easier to use when the purchase path is already clear before a tired arrival day.
The validity window starts from first use, not from purchase: Tokyo Metro’s current English page says the ticket is valid for 24, 48, or 72 hours from first use at an automatic ticket gate, and the valid period is shown on the back of the ticket. That matters because a neat three-day calendar does not automatically mean the 72-hour window is the right one.
Buying in Japan still requires an actual passport showing short-term stay status: Tokyo Metro’s current English FAQ says a passport copy is not enough when purchasing in Japan. The actual passport must show that you entered Japan with short-term stay residence status, and the purchase page says you will not be eligible if the short-term stay stamp or sticker is missing.
If the valid period ends while you are still riding, you can still exit if you boarded in time: Tokyo Metro’s current English FAQ says the ticket remains usable to exit as long as you got on the train within the valid period. That keeps one late connection from breaking the pass logic by itself.
The ticket is still subway-only, and airport access is not included: Tokyo Metro’s current English page says fares on other railway companies must be settled separately and its FAQ says you cannot travel to Narita or Haneda using only the standard Tokyo Subway Ticket. That is why airport days should stay outside the pass logic.

These are official product facts, not automatic purchase instructions. They matter because they can break the purchase before fare math even begins. If the ticket clock would start too early, if you need airport access inside the same window, or if buying in Japan would be awkward without the actual passport, the pass fit is weaker before you even compare routes.

What to verify on the official page before you buy the ticket

Confirm whether you are buying in advance from outside Japan or in Tokyo. If you plan to buy in Japan, make sure the actual passport and short-term stay proof are ready.
Confirm that the rides you want to save on really stay on Tokyo Metro and Toei Subway, not on JR, Keisei, Tokyo Monorail, or airport access products.
Confirm which day should start the clock, because the pass begins from first use rather than from purchase or from the start of your trip on paper.
If one ride may stretch close to the end of the validity window, keep Tokyo Metro’s expiry rule in mind: boarding within the valid period still lets you exit even if the clock passes before arrival.

After those rules are satisfied, the decision returns to the editorial fit question this page is for: has the trip really become compact and subway-heavy enough to reward a timed pass, or is Welcome Suica still solving the bigger problem?

Before you compare 24-, 48-, or 72-hour options, settle these three filters first

Make sure the hotel area is already fixed enough that the useful station pair is not still drifting toward JR or another operator.
Separate the airport day, JR-heavy day, or intercity segment from the pass logic before you let duration math do the talking.
Decide whether the trip is already disciplined enough to reward coverage planning, or whether flexibility is still the calmer default.

Those three filters usually answer the pass question faster than duration math does. They also stop the 72-hour version from looking smarter simply because it covers more clock time while the real route pattern is still leaking outside the network.

Three trip shapes where the answer becomes obvious

Good pass fit: Your hotel is already near useful subway stations, the main neighborhoods cluster in central Tokyo, and the airport leg is not being asked to prove the pass value.
Bad pass fit: The hotel still leans on JR, the arrival or departure day is heavy, or one anchor district keeps pulling you outside Tokyo Metro and Toei coverage.
Still too early: You are hoping the pass will create an organized itinerary for you instead of confirming one that is already visible.

Three concrete Tokyo-base examples

Example 1: buy the 24-hour ticket for one dense central day: You are staying around Asakusa or Ueno, the airport day is already handled separately, and one full sightseeing day will stay dense across Tokyo Metro and Toei-friendly neighborhoods. In that pattern, the 24-hour ticket can be the cleanest use of the pass.
Example 2: buy the 48-hour ticket only after two dense days are already visible: Your hotel base is fixed, the next two city days are clearly central and subway-heavy, and JR is no longer doing important work. In that pattern, 48 hours can be stronger than 72 because it fits the real dense block instead of stretching over weak airport or recovery time.
Example 3: step back to Welcome Suica instead: You are staying around Shinagawa or Shinjuku, the airport leg still matters, or Google Maps keeps giving you useful JR options. In that pattern, a flexible IC default is usually better than buying a subway pass that asks you to defend coverage on every ride.

These examples are not official Tokyo Metro recommendations. They are editorial shortcuts built from official pass conditions and from the way short Tokyo trips become either clearly subway-heavy or still too mixed for the ticket to stay calm.

Hotel lanes where the pass can still win, and where it usually breaks

Strongest fit: Asakusa with a real A18-side handoff: If the hotel really keeps Asakusa Station A18 practical and the dense city days stay on Tokyo Metro and Toei lines, the pass can remain elegant because the station-side finish is already aligned with subway coverage.
Possible fit: Ueno only when the subway side really wins: Ueno can work, but only if the useful hotel handoff stays close to the subway side and the real sightseeing days are central and subway-heavy. If the property keeps pulling you back toward JR Ueno or Keisei Ueno logic, the pass starts losing its clean shape.
Usually weaker: Shinjuku by default: Shinjuku can still be a good base, but the useful finish often leans on JR, New South Gate, or an airport-bus answer. That makes Tokyo Subway Ticket much easier to overestimate there.
Usually weaker: Shinagawa as an airport-practical base: Shinagawa is one of the cleanest Haneda-first hotel lanes, but that same airport practicality is a clue that the route logic still leans on non-subway segments. In that pattern, Welcome Suica often stays the calmer first answer.

These are not official Tokyo Metro recommendations. They are editorial inferences built from official ticket rules, airport benchmarks, and station-side clues so the hotel choice does not stay abstract while you compare pass durations.

When Tokyo Subway Ticket is worth it

Tokyo Subway Ticket wins when coverage and itinerary line up cleanly. Tokyo Metro’s official page makes the product clear: it is a time-based ticket for Tokyo Metro and Toei Subway rides, not a catch-all Tokyo transport pass.

Worth it when the hotel base is already fixed near stations that keep you on Tokyo Metro or Toei Subway most of the day.
Worth it when the useful neighborhoods cluster into a compact central plan instead of bouncing between JR-heavy anchors.
Worth it when the airport leg is already separate from the pass decision instead of being asked to prove the pass value on day one.
Not worth forcing when you are still hoping the trip will somehow become subway-only later.

That means the ticket can be excellent value, but only when the fit is already obvious before you buy it.

Why the 72-hour ticket is not automatically the best deal

Many travelers see the longest validity and assume it is the smartest buy. In practice, the 72-hour version only wins when those three days are still dense with covered subway rides. Three days in Tokyo often include an arrival leg, a wider JR-heavy day, or a hotel-and-neighborhood plan that keeps drifting. A longer validity window does not rescue a route pattern that keeps leaking outside the covered network.

The screenshot itinerary that makes the pass look better than it is

The failure pattern is usually simple:

You picture three dense Tokyo days and assume the longest pass should naturally be the best value.
You undercount the half-day lost to arrival, the JR segment that keeps appearing, or the hotel base that drifts the useful route away from subway-only logic.
The pass is not completely wrong, but it asks for more coverage discipline than the trip ever really had.

That is why this page keeps separating screenshot logic from actual route logic. A pass should reward a compact itinerary that already exists, not one you are still hoping will happen.

Why first-time visitors misread the 72-hour option

They count calendar days, not dense ride blocks. A three-day stay can still contain one weak airport half-day and one JR-heavy day.
They assume central sightseeing always means subway-only movement. In practice, one hotel choice or one useful JR segment can change the math fast.
They buy the longest duration first and only then ask whether the covered rides are actually there.

What breaks the pass logic fastest

The common mistake is buying the ticket before the hotel area, sightseeing zones, and airport logic are clear. Once the useful route starts leaning on JR or another operator, the ticket often stops feeling elegant.

Typical failure patterns look like this:

The hotel wins on price, but the cleanest station access keeps pointing to JR.
The arrival or departure day is doing too much work inside the pass window.
One anchor district or day trip keeps pulling the plan away from Tokyo Metro and Toei Subway.

The decision chunk that settles Tokyo Subway Ticket faster

Choose Tokyo Subway Ticket when

The dense subway block is already visible before you pay for it

Use the pass only after you know which days are genuinely dense city-movement days, the hotel station pair stays subway-friendly, and repeated coverage checks will feel predictable rather than exhausting.

Lock first: the hotel area, the airport or JR-heavy days that sit outside the pass, and the shortest real 24-, 48-, or 72-hour block that already exists in the trip.

Step back to Welcome Suica when

Flexibility is still more valuable than optimization

Welcome Suica is usually safer when the hotel is not booked yet, the first day still includes luggage and airport recovery, or you want Google Maps to show the fastest ride without filtering every option through subway-only coverage.

Useful rule: if the route still changes or the hotel lane still leaks toward JR, the pass is asking the trip for more discipline than it really has.

Regret signal

The pass is technically possible, but it keeps asking for one more explanation every time you move

That is the common regret pattern: the ticket was not totally wrong, but it was bought before the hotel area, airport day, and real route pattern were stable enough to support it calmly.

Do not buy yet if: the pass still looks elegant only in a neat screenshot version of the trip instead of in the real movement pattern.

If the hotel is still undecided, choose that first in Best area to stay in Tokyo for first-time visitors because station choice often decides whether the subway network still fits.

If the pass logic is clear and the next weak point is arrival-day data

Move to live data next if the pass logic already feels stable and the remaining friction is wayfinding or hotel contact on the actual day.
Keep the phone question separate so the provider page does not reopen the pass decision you just finished.
Use the live page as a final fit check, not as proof that the transport choice was correct.

Arrival-day data check

If subway coverage already won, solve phone data as the next separate task

Open the partner section below only after the pass logic feels defensible and the next remaining risk is live route checking on the day itself.

Check device support and unlock status before comparing any live data plan.
Check plan size and activation timing against the days when the pass will actually be used heavily.
Do not let the data page blur the pass-versus-flexibility decision you already settled.

Jump to arrival-day data checkIf transport still feels open, step back to the pass comparison first.

Next high-intent step after subway-pass fit is mostly clear

Open Best area to stay in Tokyo next if the hotel base or station pair is still doing more work than subway-pass duration math.
Open Best eSIM for Japan next if the pass mostly fits and the next weak point is live exits, hotel contact, or route recovery on the actual day.
Open Welcome Suica vs Tokyo Subway Ticket for 3 days only if the stay is already short, compact, and close to one final pass decision.

Official product checks

Use operator pages to confirm live coverage, validity, device support, and purchase rules after the broad transport answer is already clear.

Last checked April 3, 2026

Check live product rules before you pay: Eligibility, duration, supported networks, and pass validity can change.

Checked here first

Current Tokyo Subway Ticket prices, first-use validity, sales rules, and coverage limits.
Current official purchase conditions, including advance purchase routes, actual passport checks in Japan, and airport exclusion.
The route-limited assumptions and hotel-lane clues most likely to break the pass value.
Which live checks still matter before paying for a timed ticket, including expiry handling during a ride.

Official pages kept nearby

If the product answer mostly holds

Keep one guide open before provider or booking tabs spread

Use one more guide only if transport fit, hotel lane, or the first airport route still changes what you should buy. Then use the live provider or booking page to confirm the last weak point instead of reopening the whole transport search.

Where to stay in Tokyo next

Hotel base first: Best area to stay in Tokyo

Choose the hotel base next because station access often decides whether the pass still works elegantly.

Best when

Your hotel base is still open. Settle that first because it decides whether later transport and booking choices stay calm.

Open where-to-stay guide

Keep only the one remaining transport or route question open

Best eSIM next

Arrival-day data next: Best eSIM for Japan

Open the data guide next if subway-pass fit is mostly clear but live exits, hotel contact, or route recovery still feel weak.

Short-trip comparison next

Short trip check: Welcome Suica vs Tokyo Subway Ticket for 3 days

Open the direct comparison only if your Tokyo stay is short, compact, and already close to one pass decision.

Reader-supported, not sales-first

Partner links appear only after the comparison, cautions, and official-source check are already in place.

If subway coverage already won

Open only the live page that confirms the pass package or the final recovery check

Use the ticket page only after the subway-pass decision already makes sense. Keep the data page as a separate last-mile check for maps, hotel contact, or arrival-day recovery, not as proof that the pass fits.

Partner option

Disclosure

Klook

Most useful once the guide already confirms that the pass fits the actual Tokyo route pattern and the next job is choosing the right duration or redemption path.

Useful when: Travelers whose hotel area and ride pattern already make Tokyo Subway Ticket defensible and who now need one live ticket page

Shown only after the article already narrows the pass fit, so the live page is used to confirm 24-, 48-, or 72-hour packaging instead of reopening the subway-versus-flexibility decision.

Check before booking

Match 24, 48, or 72 hours to the real dense subway block instead of buying the longest option by default.
Recheck that JR is still outside the key ride pattern before you pay.
Use bundled add-ons only if they fit the route you already proved, not because the package looks tidier.

Check Tokyo Subway Ticket options

Final package details, redemption instructions, add-ons, and booking terms are shown on the partner page.

Partner option

Disclosure

Airalo

Useful once the guide already confirms that a compact subway-heavy plan fits and you want to solve connectivity as a separate trip task, not as proof that the pass fits.

Useful when: Travelers whose subway-pass decision is mostly clear and who still need mobile data for the last arrival or station-side checks

Shown after the pass logic is narrowed enough that the provider page becomes a live data check for hotel contact, maps, or station recovery, not a distraction from the transport decision.

Check before booking

Confirm validity period, supported network, and whether hotspot sharing matters for your trip.
Compare the plan size against your arrival day and intercity travel days, not just the first evening.
Use the official operator page if you still need device compatibility confirmation.

Compare data plans next

Final pricing, supported network, and activation steps are shown on the partner page.

Pass questions

Last pass questions

Use these only if the product fit is already mostly clear.

If I am in Tokyo for three days, should I just buy the 72-hour ticket?

Not automatically. The 72-hour option only wins when those three days are dense with covered subway rides and are not being diluted by JR-heavy movement or airport logic.

When does Tokyo Subway Ticket start counting time?

Tokyo Metro's official English page says the 24-, 48-, or 72-hour validity begins from first use at an automatic ticket gate, not from the moment you buy it.

If the ticket expires while I am still on the train, do I have to pay extra just to exit?

Usually no. Tokyo Metro's current English FAQ says that if you boarded within the valid period, you can still get off the train even after the valid period has expired.

Can I buy it in Japan with a passport copy or photo?

No. Tokyo Metro's current English FAQ says you must show an actual passport proving you entered Japan with short-term stay status when buying it in Japan.

What if I entered Japan through an automated gate and do not have the short-term stay stamp in my passport?

Tokyo Metro's current purchase page says you will not be eligible to buy in Japan unless your passport shows the short-term stay stamp or sticker. The same page says you should use a staffed automated gate or ask an attendant if you need that mark.

Can I use Tokyo Subway Ticket to get to Narita or Haneda?

No. Tokyo Metro's official English FAQ says airport access is not covered by the standard Tokyo Subway Ticket, so airport transport should be treated as a separate decision.

Why can Tokyo Subway Ticket feel harder than Welcome Suica even if it looks cheaper?

Because the value depends on coverage discipline. If you keep checking whether each useful route is still covered, the mental overhead can cancel out the neat savings story.

If Google Maps keeps showing JR, is the pass already a weak fit?

Usually yes. If the most useful routes keep leaning on JR or another operator, the subway-only logic is probably not strong enough yet.

When should I stop reading this guide and step back to the Tokyo base guide?

Step back when the hotel lane is still moving or the useful station pair still leaks toward JR. If the broad Tokyo base is not stable yet, the stay guide will settle more of the trip than another round of subway-pass duration math.