Lundby

Stop-place ID NSR:StopPlace:11073 with scheduled and real-time departures.

Programmatic access to stop-place data (JSON)

Source: Entur. Retrieved 2026-09-21T02:28:59Z.

Next departures

3 results

realtime:
no
aimedDepartureTime:
2026-09-21T07:17:00+02:00
expectedDepartureTime:
2026-09-21T07:17:00+02:00
destinationDisplay:
frontText:
Hadeland vgs via Solheimstorget
quay:
id:
NSR:Quay:18689
name:
Lundby
serviceJourney:
journeyPattern:
line:
id:
INN:Line:451
name:
Gran-Lunner-Grindvoll-Jevnaker
publicCode:
451
transportMode:
bus
realtime:
no
aimedDepartureTime:
2026-09-21T07:42:00+02:00
expectedDepartureTime:
2026-09-21T07:42:00+02:00
destinationDisplay:
frontText:
Lunner usk via Solheimstorget
quay:
id:
NSR:Quay:18687
name:
Lundby
serviceJourney:
journeyPattern:
line:
id:
INN:Line:451
name:
Gran-Lunner-Grindvoll-Jevnaker
publicCode:
451
transportMode:
bus
realtime:
no
aimedDepartureTime:
2026-09-21T08:17:00+02:00
expectedDepartureTime:
2026-09-21T08:17:00+02:00
destinationDisplay:
frontText:
Lunner b.sk. via Solheimstorget
quay:
id:
NSR:Quay:18689
name:
Lundby
serviceJourney:
journeyPattern:
line:
id:
INN:Line:451
name:
Gran-Lunner-Grindvoll-Jevnaker
publicCode:
451
transportMode:
bus

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the stop place page

Use the NSR stop place ID as the key. Distinguish scheduled time from expected real time, and state the time/time zone.

Use the departure lookup for the desired time window and number of departures.
Open the stop's coordinate as a place for weather, address, charging and other nearby services.

AI agent? Read the complete navigation and programming guide.