Suzuran

The Suzuran (すずらん) is a limited express train service operated by Hokkaido Railway Company (JR Hokkaido) between Muroran and Sapporo in Hokkaido, Japan.[1] The current limited express service was introduced in July 1992, but the name was first used from 1956 for an express service operated by JNR between Hakodate and Sapporo.[2] Suzuran is Japanese for Lily of the valley.

Suzuran
785 series EMU on a Suzuran service at Muroran Station, October 2007
Overview
Service typeLimited express
LocaleHokkaido
First service1956 (Express)
July 1992 (Limited express)
Current operator(s)JR Hokkaido
Former operator(s)JNR
Route
StartSapporo
EndMuroran
On-board services
Class(es)Standard class only
Technical
Rolling stock789-1000 series & 785 series EMUs
Track gauge1,067 mm (3 ft 6 in)
Electrification20 kV AC overhead
Operating speed130 km/h (80 mph)

Rolling stock

Services are formed of 5-car 785 series and 789-1000 series EMUs. All seats are non-reserved, except for car 4, which has improved "u-Seat" accommodation, including AC outlets for personal use.[1][3]

Formations

Trains are formed as shown below, with car 1 at the Muroran end.[3][4]

Car No.12345
Accommodation Non-reservedNon-reservedNon-reservedReserved (u-Seat)Non-reserved
Facilities  Toilet Wheelchair space, toiletToilet
781 series EMU on Suzuran service at Sapporo Station, June 2001

From July 1992 until 30 September 2007, Suzuran services were formed of 4-car 781 series EMUs, with one reserved car (car 4), formed as shown below.[5][6]

Car No.1234
Accommodation Non-reservedNon-reservedNon-reservedReserved
Facilities ToiletVending machineTelephone, toilet 
gollark: On Switchcraft I actually have a system which detects people complaining about it and logs it to the incident report system as blasphemy.
gollark: > I mean, I don't think that potatOS was a success<@170530017103577089> HERESY!
gollark: <@!222424031368970240> If you're trying to make a sandbox which can't be broken even if you know it's there and are deliberately trying to remove it here are some things to watch out for- `getfenv`- `os.queueEvent` (if you run code which does basically any IO outside of the sandbox/with access to non-sandbox functions)- `debug`- `load` (it has some weird environment quirks)- `io` (due to, again, environment weirdness, depending on how you load the new FS API it might still use the regular one)- potential meddling with global APIs like `string` and/or metatables, to confuse your sandboxing codeand to hide it you probably also want to worry about- `debug`- `string.dump`- `error` (you can generate stack tracebacks in a really convoluted way using it, which could allow detecting the sandbox)- `error` (in some very convoluted way you can generate stack tracebacks using this and thus realize
gollark: Proper sandboxing is extremely hard. But if you want to protect against people/things not actively attempting to break it you can do quite well.
gollark: What happened to make you want to avoid programming anyway?

See also

References

  • JR Timetable, December 2008
  1. JR新幹線&特急列車ファイル [JR Shinkansen & Limited Express Train File]. Japan: Kōtsū Shimbun. 2008. p. 86. ISBN 978-4-330-00608-6.
  2. 列車名鑑1995 [Train Name Directory 1995]. Japan: Railway Journal. August 1995.
  3. JR Timetable, August 2011 issue, p. 1002
  4. JR電車編成表 2012冬 [JR EMU Formations - Winter 2012]. Japan: JRR. October 2011. pp. 2–3. ISBN 978-4-330-25611-5.
  5. こだわりの新幹線&特急列車ガイド [In-depth Shinkansen & Limited Express Guide]. Japan: Ikaros Publishing. August 2000. p. 53. ISBN 4-87149-284-2.
  6. JR電車編成表 '05冬号 [JR EMU Formations - Winter 2005]. Japan: JRR. January 2005. p. 3. ISBN 4-88283-042-6.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.