This article is about the consumable item. For the Fishing outfit from Treasure Hunter, see Fury shark outfit.
Fury shark
Fury shark
Release date 21 February 2011 (Update unknown) edit
Members Yes
Quest item No
Tradeable No
Equipable No
Edible Yes}}{{#vardefine:heal1|}}Yes
Stackable No
Value 500 coins
High alch 300 coins
Low alch 200 coins
Destroy Drop
Store price Not sold
Examine Best before end: Bennath, 169. It's only a suggestion anyway...
Weight 0.6 kg
[view] [talk]

Fury sharks are a type of shark obtainable as a drop from lava strykewyrms and WildyWyrms. They are the second highest healing food found outside of Daemonheim behind the great gunkan; consuming one while in combat heals 2475 life points, and eating one outside of combat heals 2800 life points. Fury sharks additionally have the ability to protect one worn item or an item in a player's inventory for up to one minute after being consumed; the effects of this are identical to that of the Protect Item prayer, and the two effects stack, increasing the maximum kept items in the wilderness to 5. Consuming a fury shark has no effect on a High Risk Wilderness World as players may not keep any items they possess at the time of their death per the nature of these worlds.

When it appears to other players on the ground, they will see it as a normal shark.

Dropping monstersEdit

Monster Combat level Quantity Rarity
WildyWyrm13375 (noted)Always
Lava strykewyrm1151Uncommon


  • Originally, fury sharks were removed on 28 March 2011 along with the WildyWyrm. With the reintroduction of the WildyWyrm on 16 February 2015, the fury sharks returned as part of their drops. Its examine info refers to its old removal date, although saying it is only a suggestion as the date is already past.
  • Despite being a buff, the item protection does not give a status icon.
nl:Fury shark

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.