Høgda

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

Programmatic access to stop-place data (JSON)

Source: Entur. Retrieved 2026-09-30T20:44:11Z.

Next departures

4 results

realtime:
yes
aimedDepartureTime:
2026-09-30T22:59:00+02:00
expectedDepartureTime:
2026-09-30T23:00:10+02:00
destinationDisplay:
frontText:
Enebakk kirke
quay:
id:
NSR:Quay:8683
name:
Høgda
serviceJourney:
journeyPattern:
line:
id:
RUT:Line:550
name:
Enebakk - Oslo
publicCode:
550
transportMode:
bus
realtime:
yes
aimedDepartureTime:
2026-09-30T23:23:00+02:00
expectedDepartureTime:
2026-09-30T23:23:00+02:00
destinationDisplay:
frontText:
Oslo bussterminal
quay:
id:
NSR:Quay:8684
name:
Høgda
serviceJourney:
journeyPattern:
line:
id:
RUT:Line:550
name:
Enebakk - Oslo
publicCode:
550
transportMode:
bus
realtime:
no
aimedDepartureTime:
2026-09-30T23:59:00+02:00
expectedDepartureTime:
2026-09-30T23:59:00+02:00
destinationDisplay:
frontText:
Enebakk kirke
quay:
id:
NSR:Quay:8683
name:
Høgda
serviceJourney:
journeyPattern:
line:
id:
RUT:Line:550
name:
Enebakk - Oslo
publicCode:
550
transportMode:
bus
realtime:
no
aimedDepartureTime:
2026-10-01T00:59:00+02:00
expectedDepartureTime:
2026-10-01T00:59:00+02:00
destinationDisplay:
frontText:
Enebakk kirke
quay:
id:
NSR:Quay:8683
name:
Høgda
serviceJourney:
journeyPattern:
line:
id:
RUT:Line:550
name:
Enebakk - Oslo
publicCode:
550
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.