Jump Scares in Urban Legends: Final Cut (2000)

Urban Legends: Final Cut (2000) screenshot
Urban Legends: Final Cut (2000) screenshot
Urban Legends: Final Cut (2000) screenshot
Urban Legends: Final Cut (2000) screenshot

See below for the exact times and descriptions of the 9 jump scares in Urban Legends: Final Cut, which has a jump scare rating of 2.5.

Jump Scare Rating: While there are a couple jump scares throughout, most aren’t particularly effective. Less jumpy than Urban Legend (1998), its predecessor, overall.

Synopsis: While working on a thesis movie, a group of film students become the targets of a masked serial killer who seems hell bent on eliminating any competition for the best film award.

Contributor: Frogge contributed all the information on this page (Sign up now to become a contributor too! Learn more)

Jump Scares: 9 (2 major, 7 minor)

Reviews: IMDb, Rotten Tomatoes

Rating: R

Director: John Ottman

Runtime: 97 minutes

Netflix (US): No

Tags: Slasher

WARNING: The jump scare descriptions listed below may contain minor spoilers

Jump Scare Times

00:05:15 – A man bangs on the front window of the plane from the outside, after which it’s revealed the plane is actually a set.

00:16:55 – The girl is suddenly grabbed by a plastic bag on the face while going through a rack of clothes.

00:18:58 – A dog jumps at the window behind the girl and starts barking.

00:40:54 – Someone suddenly runs across the room behind the plastic sheets.

00:45:34 – Simon turns out and is struck by the killer.

00:51:19 – A hammer smashes the glass as Amy leans in for a look.

01:16:05 – A mannequin drops onto the table from above.

01:19:02 – While running away from the killer, Amy runs into Trevor.

01:21:45 – Toby is startled while driving, followed by a cut to Amy standing in the middle of the road.

(Major jump scares in bold)

Watch with subtitles that warn you about jump scares! Download the .srt file of the jump scares in Urban Legends: Final Cut. [More info]

Report inaccurate data: Contact us with the URL of this page and a description of what data is inaccurate. We’ll work to get it fixed!