attempts

Table actions
PO (presentation order)
the order in which the contestant's prize, VT, work of art, or live attempt was presented; 0 for simultaneous (most live tasks)
± (adjustment)
any alteration (bonus or deduction) applied to the attempt's base score
episode
the contestant's cumulative episode score after this task
series
〃

10 rows where contestant = 31

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: PO, base, points, rank, episode

id ▲ task contestant PO base ± points rank episode series team location
915 The most embarrassing item 195 Noel Fielding 31 4 1   1 5 1 1    
920 Throw an exercise ball into a bath or put the coconuts in a trolley 196 Noel Fielding 31 4 5   5 1 6 6    
925 Blow something substantial off a table 197 Noel Fielding 31 1= 1   1 5 7 7    
930 Perform a miracle 198 Noel Fielding 31 1 4   4 3= 11 11    
935 The second longest T-word 199 Noel Fielding 31 0 5   5 1 16 16    
941 The best thing 201 Noel Fielding 31 2 4   4 2 4 20    
946 Find out what’s in the briefcase 202 Noel Fielding 31 5 5   5 1 9 25    
951 Make a delicious mask 203 Noel Fielding 31 3= 2   2 4= 11 27    
956 Make a mess and then clean it up 204 Noel Fielding 31 1= 4   4 2= 15 31    
961 Record the most steps on your pedometers 205 Noel Fielding 31 0 1   1 5 16 32    

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE attempts (
   id         INTEGER PRIMARY KEY,
   task       INTEGER REFERENCES tasks(id),
   contestant INTEGER REFERENCES people(id),
   PO         TEXT,
   base       INTEGER,
   adjustment INTEGER,
   points     INTEGER,
   rank       TEXT,
   episode    INTEGER,
   series     INTEGER,
   team       INTEGER REFERENCES teams(id),
   location   INTEGER REFERENCES special_locations(id)
);