Djupedal

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

Programmatic access to stop-place data (JSON)

Source: Entur. Retrieved 2026-09-29T11:54:51Z.

Next departures

9 results

  1. realtime:
    yes
    aimedDepartureTime:
    2026-09-29T13:56:00+02:00
    expectedDepartureTime:
    2026-09-29T13:58:38+02:00
    destinationDisplay:
    frontText:
    Øystre Slidre ungdomsskule
    quay:
    id:
    NSR:Quay:20478
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    INN:Line:312
    name:
    Lidar - Øystre Slidre
    publicCode:
    312
    transportMode:
    bus
  2. realtime:
    no
    aimedDepartureTime:
    2026-09-29T14:09:00+02:00
    expectedDepartureTime:
    2026-09-29T14:09:00+02:00
    destinationDisplay:
    frontText:
    Beitostølen
    quay:
    id:
    NSR:Quay:20479
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    VYX:Line:31
    name:
    VY450 Bergen-Fagernes-Oslo
    publicCode:
    VY450
    transportMode:
    coach
  3. realtime:
    no
    aimedDepartureTime:
    2026-09-29T14:14:00+02:00
    expectedDepartureTime:
    2026-09-29T14:14:00+02:00
    destinationDisplay:
    frontText:
    Beitostølen
    quay:
    id:
    NSR:Quay:20479
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    NWY:Line:19efbc56-0bb2-5915-9e4e-48af32a0ed7a
    name:
    Beitostølen - Oslo
    publicCode:
    NW150
    transportMode:
    coach
  4. realtime:
    no
    aimedDepartureTime:
    2026-09-29T14:34:00+02:00
    expectedDepartureTime:
    2026-09-29T14:34:00+02:00
    destinationDisplay:
    frontText:
    Beitostølen-Morke
    quay:
    id:
    NSR:Quay:20479
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    INN:Line:302
    name:
    Fagernes - Beitostølen
    publicCode:
    302
    transportMode:
    bus
  5. realtime:
    no
    aimedDepartureTime:
    2026-09-29T14:58:00+02:00
    expectedDepartureTime:
    2026-09-29T14:58:00+02:00
    destinationDisplay:
    frontText:
    Oslo
    quay:
    id:
    NSR:Quay:20478
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    VYX:Line:31
    name:
    VY450 Bergen-Fagernes-Oslo
    publicCode:
    VY450
    transportMode:
    coach
  6. realtime:
    no
    aimedDepartureTime:
    2026-09-29T16:13:00+02:00
    expectedDepartureTime:
    2026-09-29T16:13:00+02:00
    destinationDisplay:
    frontText:
    Beitostølen
    quay:
    id:
    NSR:Quay:20479
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    INN:Line:302
    name:
    Fagernes - Beitostølen
    publicCode:
    302
    transportMode:
    bus
  7. realtime:
    no
    aimedDepartureTime:
    2026-09-29T16:27:00+02:00
    expectedDepartureTime:
    2026-09-29T16:27:00+02:00
    destinationDisplay:
    frontText:
    Oslo
    quay:
    id:
    NSR:Quay:20478
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    NWY:Line:19efbc56-0bb2-5915-9e4e-48af32a0ed7a
    name:
    Beitostølen - Oslo
    publicCode:
    NW150
    transportMode:
    coach
  8. realtime:
    no
    aimedDepartureTime:
    2026-09-29T16:55:00+02:00
    expectedDepartureTime:
    2026-09-29T16:55:00+02:00
    destinationDisplay:
    frontText:
    Beitostølen
    quay:
    id:
    NSR:Quay:20479
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    VYX:Line:31
    name:
    VY450 Bergen-Fagernes-Oslo
    publicCode:
    VY450
    transportMode:
    coach
  9. realtime:
    no
    aimedDepartureTime:
    2026-09-29T16:59:00+02:00
    expectedDepartureTime:
    2026-09-29T16:59:00+02:00
    destinationDisplay:
    frontText:
    Beitostølen
    quay:
    id:
    NSR:Quay:20479
    name:
    Djupedal
    serviceJourney:
    journeyPattern:
    line:
    id:
    NWY:Line:19efbc56-0bb2-5915-9e4e-48af32a0ed7a
    name:
    Beitostølen - Oslo
    publicCode:
    NW150
    transportMode:
    coach

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.