First Train Last Train Guide for Major Cities

Overview

First and last departure times are among the most searched transit details for a reason. They affect airport arrivals, evening plans, hotel choice, and whether a train-based itinerary is realistic at all. Yet they are also some of the easiest details to misunderstand. A city may have a published first train last train range, but that headline number often hides important differences by line, direction, weekday, weekend, station, and holiday calendar.

That is why a useful subway schedule by city is less about memorizing one figure and more about learning how to verify the details that matter for your trip. In practice, travelers usually need answers to five questions:

• When does the system begin service on the day I am traveling?
• When is the last train from my origin station toward my destination?
• How often do trains run during the specific window I care about?
• What changes on weekends, holidays, or maintenance nights?
• What is my backup if rail service ends earlier than expected?

This guide focuses on major urban rail systems, including metro, subway, underground, rapid transit, and city rail networks. The exact naming differs by city, but the planning logic is similar everywhere. Use this article as an update-friendly process rather than a static timetable page. It will stay useful even as apps, agency websites, and station information tools evolve.

For many trips, urban rail hours are only one part of a wider chain. If you are connecting from a terminal, you may also want to read our Airport to City Center Transport Guide: Train, Bus, Taxi, and Shuttle Options by Airport, which complements this workflow with last-mile transfer planning.

Step-by-step workflow

Use this workflow whenever you need dependable late night train times or early-morning metro access in a large city. It is designed to work whether you are a visitor planning one trip or a frequent traveler keeping your own transport notes.

1. Define the exact journey, not just the city

Start with the specific stations, direction of travel, and date. “What time is the last metro in Paris?” or “When does the subway open in Tokyo?” is usually too broad to be useful. Large systems often have different terminal departures by branch, and some interlined routes split after a certain stop.

Write down:

• Origin station
• Destination station
• Travel date
• Day type: weekday, Friday, Saturday, Sunday, public holiday, or holiday eve
• Your tolerance for risk: exact last possible train, or a safer earlier cutoff

This single step prevents one of the most common planning mistakes: using a citywide operating-hours headline when you really need the last train in one direction from one station.

2. Check the official network map before checking times

Open the current rail map and confirm that your route is actually rail-only. In some cities, a late-night journey shown in a trip planner may involve a rail segment plus a replacement bus, night bus, or short walk between stations with similar names. The map tells you whether your route stays on the urban rail system or quietly changes mode.

At this stage, note any details that could affect first and last service:

• Branching lines with different terminals
• Express and local patterns
• Airport branches with limited hours
• Interchange stations that may close transfers earlier than the whole system closes
• Stations served by only part of the line late at night

This is especially important for travelers who assume all stations on a line keep identical metro operating hours. They often do not.

3. Find the station-level first and last train information

Look for station-specific timetables, first/last train pages, PDF schedules, or a journey planner with departure detail. Your aim is to find the departure from your actual station toward your intended destination or transfer point.

When reviewing schedules, prioritize sources in this order:

1. Official operator website or app
2. Station timetable posted by the operator
3. Official journey planner results for your date and time
4. Well-maintained local transit maps or traveler references

A city may advertise a simple range such as “trains run roughly from early morning to around midnight,” but your real working data should be more specific. If you can, note both:

• The first departure you could realistically board
• The last departure you are willing to rely on

Those are not always the same as the first and absolute final trains published by the system.

4. Build in a safety margin for the last train

The absolute final departure is rarely the best target. If you are attending a concert, arriving from a delayed flight, or navigating a city for the first time, aim for a buffer. A practical rule is to identify a “hard last train” and a “comfort last train.”

Your hard last train is the final workable rail option if everything goes right. Your comfort last train is the one you plan to catch, leaving room for wrong exits, fare gate confusion, queues, or transfer delays.

This matters even more in complex systems where the final train may require:

• A fast cross-platform transfer
• A station change between nearby but separate terminals
• A final branch departure that leaves earlier than the main line
• A short transfer window before gates close or platforms clear

In other words, useful urban rail hours planning is about workable timing, not theoretical timing.

5. Check frequency patterns, not just opening and closing time

Many people search for first train last train information when the real issue is frequency. A line may technically be running, but trains could be sparse early in the morning, late at night, or on weekends. That changes connection risk.

Look for service patterns in these periods:

• Start of service window
• Morning peak
• Midday off-peak
• Evening peak
• Late evening
• Final hour before last train

Frequency affects how aggressively you need to plan. A missed train on a three-minute headway is an inconvenience. A missed train on a twenty-minute headway may break the entire trip.

6. Check late-night caveats by day type

One of the biggest sources of confusion in any transport schedule is the difference between weekday and weekend operations. Some systems extend service later on Friday and Saturday. Others do the opposite by running reduced evening frequency or closing sections for maintenance. Some cities supplement rail with night buses rather than extending trains.

Always verify:

• Weekend transport schedule changes
• Holiday transport changes
• Engineering works or planned closures
• Special event operations
• Seasonal timetable adjustments

Do not assume a Friday-night pattern applies to a public holiday eve, or that a Sunday timetable matches a national holiday. Even experienced commuters get caught by this.

7. Confirm transfer viability on multi-line trips

If your journey requires changing lines, check each transfer separately. The relevant question is not only whether the first line still runs, but whether you can complete the whole chain before the second line stops accepting practical connections.

For a multi-leg route, note:

• Last departure from origin
• Expected arrival at interchange
• Walking time within the station
• Last connecting departure onward
• Last-mile option after arrival

This is where a station-to-station approach becomes essential. A citywide claim about late service can create false confidence if the final branch or feeder connection ends earlier.

8. Decide on a fallback before you need it

Every solid first train last train plan includes an alternative. If your evening depends on rail, identify your backup while you still have signal, battery, and time to think clearly.

Possible fallbacks include:

• Night bus routes
• Licensed taxi or ride-hail pickup points
• Walking to a different station on a line with later service
• A hotel closer to your late-night destination
• Leaving earlier than originally planned

The fallback is part of the workflow, not an afterthought.

9. Save your findings in a reusable personal format

The most practical way to manage subway schedule by city information is to build a small note for each destination. Keep it short enough to skim on your phone. A simple template works well:

• City and system name
• Lines relevant to my stay
• First train from nearest hotel station
• Last comfort train back
• Last hard train back
• Weekend or holiday caveats
• Backup bus or taxi plan
• Date checked

That final line—date checked—is what turns your note into an evergreen planning tool instead of a stale memory.

Tools and handoffs

You do not need a complex setup to track metro hours well, but it helps to know which tool answers which question. The mistake many travelers make is expecting one app to cover everything perfectly. In reality, good trip planning often involves a handoff between tools.

Use the official site or app for system rules

Official channels are usually best for line notices, engineering work, platform changes, and station-level first/last train pages. They are also the best place to verify whether apparent gaps in service are real or simply not displayed well in a third-party map app.

Use a journey planner for trip-specific routing

A journey planner helps answer the practical version of the problem: if you leave at a certain time, can you still make the whole route? This is especially useful for airport runs, event returns, and early departures. If your city trip includes a flight, you may also find schedule coordination easier when paired with a flight time calculator or a broader itinerary note.

Use map tools for station exits and walking time

Even the best rail timetable can fail you if the interchange requires a long walk. Mapping tools are useful for platform-to-platform estimates, station exit choice, and deciding whether transferring at one station is safer than another.

Use your own note as the final handoff

The most reliable travel planning tool is often your own condensed summary. Once you have checked the official information, transfer the useful details into a format you can trust at a glance. That is especially helpful in cities where mobile data is patchy underground.

If you enjoy building city-specific itineraries around rail lines, our MTR Food Crawl: How to Plan a Transit-Friendly Dining Route in Hong Kong shows how timetable-aware planning can shape a full day out, not just a commute.

Quality checks

Before relying on any first and last train reference, run a short quality check. This is what separates a useful transit note from a copied timetable snippet.

Check 1: Is the information station-specific?

If not, it may be too broad to trust. Citywide system hours are only a starting point.

Check 2: Does it reflect the right day type?

Weekday, Friday, Saturday, Sunday, and public holiday patterns can differ substantially.

Check 3: Does it cover your direction of travel?

The last train inbound and outbound may not align. Branch destinations matter.

Check 4: Have you tested the full route?

A valid first leg means little if the transfer or final branch no longer works.

Check 5: Do you have a backup?

If not, your plan is fragile. Add a night-bus, taxi, or earlier-departure option.

Check 6: Did you note when you checked it?

Without a date, you will not know whether your own reference is still reliable.

As a final editorial rule, be cautious with crowd-sourced pages, old blog posts, and forum answers that quote exact times without update context. They may still be useful for understanding how a system works, but they should not be your only source for a time-sensitive journey.

When to revisit

The best first train last train guide is one you revisit at the right moments. Urban rail systems change in small but important ways: maintenance windows shift, late-night service is adjusted, station access patterns change, and apps redesign how timetable information is displayed. You do not need to recheck everything constantly, but you should refresh your notes when one of these triggers appears.

• Before any early airport departure or late-night arrival
• Before weekends and public holidays
• When a city announces line works, closures, or timetable revisions
• When staying in a different neighborhood than usual
• When your route depends on the final branch or a tight transfer
• When the transit app or official website changes its features or layout

A simple practical routine works well:

1. Forty-eight to seventy-two hours before travel, check your route again.
2. On the day of travel, confirm there are no service alerts.
3. Save screenshots or a short note with your comfort last train and backup plan.
4. If conditions look uncertain, leave one train earlier than planned.

That last step is the most useful action in this whole guide. Timetables are precise, but travel is not. A small margin turns a stressful end-of-night dash into a manageable routine.

Use this article as a standing workflow for any city with a metro, subway, or urban rail network. The exact tools may evolve, and the published times certainly will, but the process remains the same: define the trip clearly, verify station-level data, account for frequency and day type, confirm transfers, and keep a backup. That is how you make travel schedules work in the real world.