This article is about the cooked version. For the raw version, see Spider on stick (raw).
Spider on stick
File:Spider on stick.png
Release date 9 August 2005 (Update unknown) edit
Members Yes
Quest item No
Tradeable Yes
Equipable No
Edible Yes}}{{#vardefine:heal1|}}Yes
Stackable No
High alch 30 coins
Low alch 20 coins
Destroy Drop
Store price 50 coins
Exchange price 64 coins (info)
Buy limit 1,000
Examine A nicely roasted spider threaded onto a skewer stick.
Weight 0.6 kg
[view] [talk]

A Spider on stick can be made on Karamja during the Tai Bwo Wannai Cleanup minigame. Kill a Jungle Spider to get spider carcass, then use a machete to cut a thatching spar from the undergrowth around Tai Bwo Wannai to skewer stick and use stick with the spider carcass. During the Tai Bwo Wannai Cleanup minigame this can be very useful against the white and blue masked broodoo victims since this food is obtained during the course of the minigame thereby reducing need for inventory food.

When spider is on a stick, it can be cooked. Cooking level 16 is needed. When eaten, the skewer stick returns to inventory, occasionally the spider will heal 100 life points instead, saying "You eat the spider. The meat has a silky texture with a delicate web of flavours". Alternatively an arrow shaft can be used to make spider on shaft however the arrow shaft is not returned to inventory. A spider on stick is needed to be cooked during a medium Karamja Task.

Tools/Utensils None
Ingredients Spider carcass, Thatching spar made into Skewer stick
Cooking-icon Level 16
Level at which it stops burning Unknown edit
Cooking-icon Experience 80
Range Only? No.
Instructions See above.


  • The raw and cooked versions of this item have the exact same name, unlike most other foods in RuneScape - only they are a different colour and have different examine information.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.