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
〃

11 rows where contestant = 29

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▲ task contestant PO base ± points rank episode series team location
913 The most embarrassing item 195 Josh Widdicombe 29 2 5   5 1 5 5    
918 Throw an exercise ball into a bath or put the coconuts in a trolley 196 Josh Widdicombe 29 5 1   1 5 6 6    
923 Blow something substantial off a table 197 Josh Widdicombe 29 4= 4   4 2= 10 10    
928 Perform a miracle 198 Josh Widdicombe 29 4 5   5 1= 15 15    
933 The second longest T-word 199 Josh Widdicombe 29 0 4   4 2= 19 19    
937 Sing along to the Taskmaster theme tune 200 Josh Widdicombe 29 1 0   0   0 19    
939 The best thing 201 Josh Widdicombe 29 4 3   3 3= 3 22    
944 Find out what’s in the briefcase 202 Josh Widdicombe 29 3 4   4 2 7 26    
949 Make a delicious mask 203 Josh Widdicombe 29 2 4   4 2 11 30    
954 Make a mess and then clean it up 204 Josh Widdicombe 29 3= 3   3 4 14 33    
959 Record the most steps on your pedometers 205 Josh Widdicombe 29 0 4   4 2 18 37    

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)
);