Allemannsdata Wiki
Manual search

Granly

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

Programmatic access to stop-place data (JSON)

Source: Entur. Retrieved 2026-09-28T23:46:06Z.

Next departures

3 results

  1. realtime:
    no
    aimedDepartureTime:
    2026-09-29T05:28:00+02:00
    expectedDepartureTime:
    2026-09-29T05:28:00+02:00
    destinationDisplay:
    frontText:
    Tønsberg-Hvasser
    quay:
    id:
    NSR:Quay:30502
    name:
    Granly
    serviceJourney:
    journeyPattern:
    line:
    id:
    VKT:Line:2
    name:
    Tjøme-Tønsberg-Horten-Holmestr
    publicCode:
    2
    transportMode:
    bus
  2. realtime:
    no
    aimedDepartureTime:
    2026-09-29T05:43:00+02:00
    expectedDepartureTime:
    2026-09-29T05:43:00+02:00
    destinationDisplay:
    frontText:
    Tønsberg-Tenvik
    quay:
    id:
    NSR:Quay:30502
    name:
    Granly
    serviceJourney:
    journeyPattern:
    line:
    id:
    VKT:Line:2
    name:
    Tjøme-Tønsberg-Horten-Holmestr
    publicCode:
    2
    transportMode:
    bus
  3. realtime:
    no
    aimedDepartureTime:
    2026-09-29T05:44:00+02:00
    expectedDepartureTime:
    2026-09-29T05:44:00+02:00
    destinationDisplay:
    frontText:
    Skoppum
    quay:
    id:
    NSR:Quay:30502
    name:
    Granly
    serviceJourney:
    journeyPattern:
    line:
    id:
    VKT:Line:40
    name:
    Horten-Holtandalen-Skoppum
    publicCode:
    40
    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.

AI agent? Read the complete navigation and programming guide.