See the railroad as it moves.
RailGlance brings passenger trains, stations, routes, service alerts, and recent movement together on one map. Every position is labeled according to what the source actually provides.
Last updated September 2, 2026
One clear view across a growing passenger-rail region
RailGlance is an independent North American Amtrak and regional passenger rail service for riders, railfans, photographers, families, and anyone curious about the trains around them. It combines compatible public and authorized sources while preserving the limits of each feed.
RailGlance is not an official trip planner, dispatching system, emergency service, or government website. Confirm fares, schedules, platforms, accessibility information, and travel decisions with the operator.
What the markers mean
Not every operator publishes the same kind of location. RailGlance does not turn an estimate into a GPS claim.
Icons may be aligned to nearby rail geometry and speed may be calculated from consecutive plausible fixes. Smooth motion only replays the completed interval between received positions; it never advances beyond the newest update.
Where the map comes from
Routes, stations, positions, trip updates, and service alerts can come from different systems. A listed provider may offer complete GPS positions, estimates only, or static route and station information.
Valley Metro route and arrival data is used with permission from Valley Metro. Seattle Streetcar scheduling, geographic, and realtime data is used with permission from King County.
TransLink route and arrival data is used with permission from TransLink. TransLink is not responsible for the accuracy or currency of information displayed by RailGlance.
Service names, agency names, logos, and trademarks belong to their respective owners. Their appearance identifies a service or source and does not imply sponsorship, endorsement, operation, or verification of RailGlance.
Marked places
RailGlance keeps two optional, independently controlled national place catalogs grouped by state. The motorsports catalog uses permanent U.S. venues from NASCAR’s current national series and NHRA’s current national-event schedule, plus a small, clearly identified set of community-interest independents such as Freedom Factory, Bradenton Motorsports Park, and Brown County Dragway. Temporary street layouts do not receive misleading permanent pins.
The separate Rail history & museums catalog covers public railroad museums, heritage and excursion railways, preserved depots, restoration collections, and major documented historic rail sites. It is a curated national discovery catalog—not a claim to contain every surviving depot, private collection, historical marker, or abandoned rail segment. Each organization retains control of its hours, access, tickets, exhibits, and operating status.
Both place catalogs are display-only. Museum and heritage-railway markers never become live trains, active stations, providers, GPS fixes, alerts, search results, or history records.
Every state stays hidden until a visitor enables it or chooses that state’s focus action. State controls keep the national catalog from cluttering the passenger-rail map.
Each detail card links to NASCAR, NHRA, the museum, railway, park, preservation group, or another identified authoritative source so its name, location, and inclusion can be checked.
A marker is not an advertisement, recommendation, affiliation, sponsorship, endorsement, or statement that the public may enter the property.
RailWatch
RailWatch adds selected third-party rail cameras and links to public railroad-radio coverage. Nearby trains are shown only when RailGlance has a confirmed GPS position within 25 miles. Near does not mean visible, audible, or on the same track.
A camera connects to YouTube only after you press “Load live camera.” Closing the card removes the player.
Radio opens on the public provider page. RailGlance does not proxy, record, transcribe, archive, or rebroadcast the audio.
Each camera identifies the feed network or channel, links to its source page, identifies the physical location host when known, and shows a support link when one is available.
Stream owners control availability, content, advertising, cookies, retention, and access terms. RailGlance promptly reviews correction, relabeling, limitation, and removal requests.
RailWatch is not a security, dispatching, enforcement, or emergency tool and does not identify people, crews, cargo, or private activity.
Embedding an official player does not grant permission to capture or repost its frames. Third-party Discord sightings remain link-only until RailGlance receives written permission for credited still images.
RailGlance may offer clearly labeled sponsorships, approved referral links, managed hosting, or camera and sensor services. Paid relationships will be disclosed and will not change train-position fidelity, erase ownership credit, or buy misleading placement.
Owner-operated detectors and cameras will be labeled separately from third-party streams and from GPS. Site permission, privacy controls, detection limits, retention, and media rights must be documented before activation.
Holiday trains
During limited Halloween and Christmas windows, RailGlance may place clearly fictional named trains on selected published route shapes. These are playful public displays, not transit services or observations.
Holiday trains use the dedicated railglance-event source. They never enter the live train API, provider totals, GPS counts, service alerts, search results, or position history.
The markers follow selected Metrolink GTFS shapes on a deterministic loop. Their position, direction, name, story, origin, and destination are fictional.
Holiday markers use special artwork and their detail cards state that they are fictional seasonal displays—not GPS, operator reports, schedules, or service alerts.
Opening a holiday train remembers its discovery only in that browser. The collectible count is not connected to Discord and is not sent to RailGlance.
Accounts and RailGlance Labs
The live map, trains, stations, search, service alerts, and core details remain available without an account. Discord sign-in is used only for community features and early access in RailGlance Labs; RailGlance does not create a separate password.
Sign-in requests identify and guilds.members.read to confirm basic identity, RailGlance Discord membership, and eligible roles.
RailGlance stores the Discord user ID, username, display name, eligible role IDs, encrypted OAuth credentials, and session timing needed to keep the connection working.
RailGlance does not request a Discord email, password, direct messages, friends list, payment information, or permission to post as you.
When an authorized Developer changes the public site through Control Center, RailGlance records the Discord account ID and display name, action, target, summary, and time in a private audit history limited to the latest 500 entries.
Signing out deletes the current RailGlance session and its OAuth credentials. You may also revoke access from Discord’s Authorized Apps settings.
Early-access features may change or become unavailable and should not be relied upon for travel or safety decisions.
Open account settings →Simple measurement, no advertising profile
RailGlance does not sell personal information or share it for cross-site targeted advertising. There are no public user profiles, ticket sales, or advertising trackers.
A random identifier is saved in this browser so RailGlance can count daily and returning visitors. The server stores only a one-way salted hash, aggregate feature counts, and visit dates for up to 90 days. The analytics database does not store IP addresses, exact map locations, or search words.
Map position, filters, layer choices, display settings, and update preferences are saved locally. Application files may be cached for performance and installable-app behavior.
Discord connection uses short-lived sign-in state and a secure session cookie. These are functional security cookies, not advertising cookies.
Hosting, CDN, reverse-proxy, and security systems may process an IP address, browser details, requested path, response status, timestamp, and error information to deliver and protect the service.
Map tiles and any camera or radio service you choose receive ordinary browser requests and apply their own privacy terms.
RailGlance does not request browser geolocation, camera, microphone, payment, or USB access.
Disabling anonymous measurement removes this browser’s identifier and asks RailGlance to delete its associated visitor record. Existing totals cannot identify or be separated back into individual activity.
Your privacy choices
You may clear local preferences through your browser’s site-data controls, delete the current Discord session from the account page, or revoke future access through Discord Authorized Apps. You may also request access, correction, or deletion of account information through the contact below.
Discord separately processes information under its own Privacy Policy and Terms of Service.
Use RailGlance responsibly
By using RailGlance, you agree to these terms. If you do not agree, do not use the service or connect an account.
Informational use
Positions, arrivals, alerts, vehicle identities, and routes can be late, incomplete, duplicated, wrong, or unavailable. Verify time-sensitive information with the operator.
Rail safety
Do not use RailGlance for dispatching, train separation, emergency response, locating personnel, law enforcement, or any safety-critical task. Never enter railroad property to investigate a marker or obtain a better view.
Acceptable use
Do not overload, disrupt, scrape restricted endpoints, bypass rate limits, evade access controls, probe private systems, introduce malicious code, or interfere with RailGlance or its providers.
Accounts
Do not share session cookies, impersonate another person, or use access granted to someone else. Access may be limited or revoked to protect the service and its users.
Third-party services
Maps, data feeds, Discord, cameras, radio services, and marked venues remain subject to their owners’ terms and access rules. Do not record, redistribute, automate, trespass, or remove attribution unless the owner permits it.
Paid relationships
Sponsorship, referral, hosting, installation, maintenance, or monitoring relationships do not transfer ownership of third-party content and do not guarantee coverage, ranking, continued service, or tracking accuracy.
Intellectual property
RailGlance does not grant rights to third-party feeds, maps, names, logos, or trademarks. Do not present RailGlance as an official operator service or resell data without the necessary rights.
Feedback
RailGlance may use voluntarily submitted bug reports, corrections, and suggestions to improve the service. Do not submit secrets, confidential information, or unlawfully obtained material.
Availability
RailGlance and its data are provided “as is” and “as available,” without guarantees of accuracy, fitness, uninterrupted operation, or continued access to any feature.
Limitation of liability
To the fullest extent allowed by law, RailGlance’s owner and contributors are not liable for indirect, incidental, special, consequential, or reliance-based losses arising from the service, its data, outages, accounts, or third-party providers.
Coverage, sources, features, and these terms may change. Material policy changes will be dated on this page. Valid licensing, attribution, privacy, security, and removal concerns will be reviewed, and affected material may be limited while a concern is resolved. If one part of these terms cannot be enforced, the remaining parts continue to apply.
Help riders see your service clearly
RailGlance welcomes documented passenger-rail data and correction requests. The most useful package is static GTFS plus GTFS-Realtime VehiclePositions, Trip Updates, and Service Alerts with stable identifiers, source timestamps, update cadence, rate limits, licensing, attribution requirements, and a technical contact.
RailGlance does not need dispatch controls, employee accounts, passenger records, manifests, cargo information, or security-sensitive operational data. When a location is not GPS, documentation describing what it represents allows RailGlance to label it accurately.
Contact RailGlance about operator data →Questions, corrections, and partnerships
Contact RailGlance about privacy, data corrections, licensing, attribution, security, operator data, partnerships, or these terms. Never send passwords, API keys, tokens, private railroad information, or other secrets.