Denise (Hawise) de Redvers, Countess of Devon

‹ Back to de Redvers surname

Is your surname de Redvers?

Research the de Redvers family
Start your family tree now

Denise (Hawise) de Redvers, Countess of Devon's Geni Profile

Share your family tree and photos with the people you know and love

  • Build your family tree online
  • Share photos and videos
  • Smart Matching™ technology
  • Free!
Get Started

Denise (Hawise) de Redvers (de Dunstanville), Countess of Devon

Also Known As: "Hawise"
Birthdate:
Birthplace: Cornwall, England
Death: April 21, 1162 (16-25)
Place of Burial: Twynham, England
Immediate Family:

Daughter of Réginald de Dunstanville, 1st Earl of Cornwall and Beatrice (Mabilia) fitzWilliam
Wife of Richard de Reviers, 2nd Earl of Devon, Lord of The Isle of Wight
Mother of Baldwin de Reviers, 3rd Earl of Devon and Richard de Reviers, 4th Earl of Devon
Sister of Sarah de Cornouailles, of Cornwall; Joan FitzRoy de Valletort; William FitzCount; Maude de Dunstanville, of Cornwall; John de Dinstanville and 3 others
Half sister of Henry FitzCount, Co

Managed by: Private User
Last Updated:
View Complete Profile
view all 23

Immediate Family

view all 15

Denise (Hawise) de Redvers, Countess of Devon's Timeline

1141
1141
Birth of Denise (Hawise) de Redvers, Countess of Devon
Cornwall, England
1162
April 21, 1162
Age 21
Death of Denise (Hawise) de Redvers, Countess of Devon
1939
August 28, 1939
Age 21
baptised (LDS) on 8/28/1939
August 28, 1939
Age 21
baptised (LDS) on 8/28/1939
August 28, 1939
Age 21
baptised (LDS) on 8/28/1939
October 26, 1939
Age 21
endowed (LDS) on 10/26/1939
October 26, 1939
Age 21
endowed (LDS) on 10/26/1939
MANTI
October 26, 1939
Age 21
endowed (LDS) on 10/26/1939
1955
March 2, 1955
Age 21
child sealed (LDS) on 3/2/1955
Salt Lake City Utah Temple, Salt Lake City, Salt Lake, Utah, USA
Follow UsLike Us
English (US)   eesti   Svenska   Español (España)   Français   עברית   Norsk (bokmål)   dansk   Nederlands   Deutsch   »
close
settings
By using Geni you agree to our use of cookies as identifiers and for other features of the site as described on our Privacy page.