FANDOM


Ulfric
Ulfric Longbeard
Release date 10 April 2007 (Update)
Members? Yes
Combat level 100
Always drops Bones
Examine
What could be worse than an angry, undead Fremennik?
Combat info
Hitpoints 60
Aggressive Yes
Poisonous No
Max hit 11
Weakness None
Attack Styles
Melee (slash)
Slayer-icon Slayer info
Not assigned
Combat-icon Combat stats
Attack-icon Strength-icon Defence-icon Ranged-icon Magic-icon
100 82 100 1 1
Attack-icon Aggressive stats
White dagger White scimitar White warhammer Magic-icon Ranged-icon
+0 +0 +0 +0 +0
Defence-icon Defensive stats
White dagger White scimitar White warhammer Magic-icon Ranged-icon
+0 +0 +0 +0 +0
Other bonuses Immunities
Strength-icon RangedStrength-icon Attack-icon Poison hitsplat Venom hitsplat
+0 +0 +0 Not immune Not immune
Attack speed
Monster attack speed 4

Ulfric Longbeard is a skeletal boss monster who appears during Olaf's Quest. There is a ranging safespot at his grave. It is a good idea for players to turn on Protect from Melee to avoid the use of food. His max hit is rather low compared to monsters of a similar level, with the fact that Ulfric is inaccurate, makes him a very easy boss for players about his level.

HistoryEdit

Ulfric Longbeard was once a Fremennik sailor who collected treasure. However, some treasures were cursed. A few years ago, several ships, including Ulfric's, were destroyed along the shores of the Fremennik Province. The survivors found a cave on a cliff far east of Rellekka where they decided to stash the remaining treasure from their ships. Ulfric and his men died soon afterwards.

Later, Sven the Helmsman created a treasure map to the entrance of the cave. This map eventually came to be in the hands of Olaf Hradson and comes into players' hands during Olaf's Quest.

DropsEdit

100%Edit

Item Quantity Rarity GE market price
Bones Bones 1 Always 67

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.