Formerly Sovereign House

Landgraviate of Hesse-Homburg – House of Lorraine-Brabant

Landgraviate of Hesse-Homburg – House of Lorraine-Brabant

Jurisdiction
Hesse-Homburg
Dynasty
House of Lorraine-Brabant
Entry type
House
Editorial status
Reviewed - Verified
hesse-homburg.jpg

Landgrafschaft Hesse-Homburg

Hesse-Homburg was formed into a separate landgraviate in 1622 by the landgrave of Hesse-Darmstadt to be ruled by his son, although it did not become independent of Hesse-Darmstadt until 1668. It was briefly divided into Hesse-Homburg and Hesse-Homburg-Bingenheim; but these parts were again united in 1681. In 1806, Hesse-Homburg was incorporated with Hesse-Darmstadt; but in 1815 by the Congress of Vienna the latter state was compelled to recognize the independence of Hesse-Homburg, which was increased by the addition of Meisenhelm. The landgraviate of Hesse-Homburg consisted of two parts, the district of Homburg on the right side of the Rhine, and the district of Meisenheim, added in 1815, on the left side of the same river.

In 1866, Hesse-Homburg was inherited by the grand-duke of Hesse-Darmstadt, while Meisenheim fell to Prussia. Later that same year these territories were taken from Hesse-Darmstadt again, and the former landgraviate was combined with electorate of Hesse-Kassel, duchy of Nassau, and the free city of Frankfurt to form the Prussian province of Hesse-Nassau. Today it forms a part of the German state of Hesse.

History of the House of Hesse

The House of Hesse is a European royal dynasty from the region of Hesse, originally and still formally the House of Brabant, The origins of the House of Hesse begin with the marriage of Sophie of Thuringia, daughter of Louis IV, Landgrave of Thuringia and Elizabeth of Hungary with Henry II, Duke of Brabant from the House of Reginar. Sophie was the heiress of Hesse which she passed on to her son, Henry upon her retention of the territory following her partial victory in the War of the Thuringian Succession in which she was one of the belligerents.

Originally the western part of the Landgraviate of Thuringia, in the mid 13th century it was inherited by the younger son of Henry II, Duke of Brabant, and became a distinct political entity. From the late 16th century it was generally divided into several branches, the most important of which were those of Hesse-Kassel (or Hesse-Cassel) and Hesse-Darmstadt. In the early 19th century the Landgrave of Hesse-Kassel was elevated to Elector of Hesse (1803), while the Landgrave of Hesse-Darmstadt became the Grand Duke of Hesse (1806), later Grand Duke of Hesse and by Rhine. Electoral Hesse (Hesse-Kassel) was annexed by Prussia in 1866, while Grand Ducal Hesse (Hesse-Darmstadt) as lasted until the end of the German monarchies in 1918. Moritz, Landgrave of Hesse is the current (2012) head of the house.

The Branches of the House of Hesse

Philip I, Landgrave of Hesse, died in 1567. Hesse was divided between his four sons, four new lines which arose: Hesse-Darmstadt, Hesse-Kassel, Hesse-Marburg and Hesse-Rheinfels. The line of Hesse-Darmstadt was also part of the morganatic line of the Battenberg family when Prince Alexander of Hesse and by Rhine married to Countess Julia Hauke. The Battenbergs who later settled in England changed that name to Mountbatten after World War I.

  • House of Brabant
    • Hesse (1264-1567)
      • Hesse-Darmstadt (1567-1918), became Grand Duchy of Hesse in 1806
        • Hesse-Butzbach (1609-1642)
        • Hesse-Braubach (1609-1651)
        • Hesse-Homburg (1622-1866)
        • Hesse-Itter (1661-1676)
        • Battenberg (1858, morganatic line. Mountbatten since 1917)
      • Hesse-Kassel (1567-1866), became Electorate of Hesse in 1803
        • Hesse-Rotenburg (1627-1834)
        • Hesse-Wanfried (1627-1755)
        • Hesse-Rheinfels (1627-1754)
        • Hesse-Philippsthal (1685-1866)
          • Hesse-Philippsthal-Barchfeld (1721-1866)
      • Hesse-Marburg (1567, divided in 1604 between Hesse-Darmstadt and Hesse-Kassel)
      • Hesse-Rheinfels (1567, divided in 1583 between Hesse-Darmstadt, Hesse-Kassel and Hesse-Marburg)

Hesse-Kassel and its junior lines were annexed by Prussia in 1866; Hesse-Darmstadt became the People’s State of Hesse when the monarchy was abolished in 1918. Hesse-Philippsthal died out in the male line in 1925; Hesse-Darmstadt in 1968. Descendants of Hesse-Kassel and Hesse-Philippsthal-Barchfeld are alive to this day.

Princes of Hesse-Homburg – 1622-1866

  • Frederick I, third son of George I of Hesse-Darmstadt, 1622-1638
  • William Christoph, 1638-1681, sold Homburg to his brother George Christian in 1669, but retained Bingenheim (Landgrave of Hesse-Homburg-Bingenheim)
    • Margareta Elisabetha of Leiningen-Westerburg-Schaumburg, Regent 1638-1648
  • George Christian, 1669-1671 Landgrave of Hesse-Homburg
Under mortgage to two merchants (1671-1673) and the Landgraves of Hesse-Darmstadt (1673-1679)
  • Frederick II, son of Fredrick I, 1679-1708, Commander general of the army of Brandenburg (The Prince of Homburg), redeemed Homburg in 1679, regained Bingenheim in 1681
  • Frederick III Jacob, 1708-1746, Cavalry general in the Netherlands
  • Frederick IV, 1746-1751
  • Frederick V, Landgrave of Hesse-Homburg, 1751-1806
    • Ulrike Louise of Solms-Braunfels, Regent 1751-1766
1806 Annexed by Hesse-Darmstadt, 1815 restored by the Congress of Vienna
  • Frederick V, 1815-1820 (restored)
  • Frederick VI, 1820-1829, Cavalry general in Austria
  • Louis William, 1829-1839, Infantry general in Prussia
  • Philip, 1839-1846, Field marshal in Austria
  • Gustav, 1846-1848, Cavalry general in Austria
  • Ferdinand, 1848-1866, Cavalry general in Austria
1866 annexed by Prussia

The Family Titles and Styles

The present members of this family bear the title Prince or Princess and Landgrave or Landgravine of Hesse, together with the formal appellation of His or Her Highness.

The Genealogy of the Princely House

Kasimir Wilhelm, Prince of Hesse-Homburg (Weferlingen 23 Mar 1690-Hötensleben 9 Oct 1726); m. Braunfels 3 Oct 1722 Christine Charlotte Gfn von Solms-Braunfels (Greifenstein 10 Nov 1690-Homburg 16 Oct 1751)

  • 1a) FRIEDRICH IV, Landgrave of Hesse-Homburg (Braunfels 15 Apr 1724-Homburg 7 Feb 1751); m. Hungen 10 Oct 1746 Ulrike Luise Gfn zu Solms-Braunfels (Hungen 30 Apr 1731-Homburg 12 Sep 1792)
  • 1b) FRIEDRICH V, Landgrave of Hesse-Homburg 7 Feb 1751 (Homburg 30 Jan 1748-Homburg 20 Jan 1820); m. Darmstadt 27 Sep 1868 Karoline Landgravine of Hesse-Darmstadt (Buchsweiler 2 Mar 1746-Homburg 18 Sep 1821)

    • 1c) FRIEDRICH VI Joseph, Landgrave of Hesse-Homburg (Homburg 30 Jul 1769-Homburg 2 Apr 1829); m. Buckingham House 7 Apr 1818 Elizabeth Pss of Great Britain, Ireland and Hannover, etc (Buckingham House 22 May 1770-Frankfurt 10 Jan 1840)

  • 2c) LUDWIG Wilhelm, Landgrave of Hesse-Homburg (Homburg 29 Aug 1770-Luxemburg 19 Jan 1839); m. Biebrich 2 Aug 1804 (div 1805) Auguste Pss von Nassau-Usingen (Usingen 30 Dec 1778-Wildbad 16 Jul 1846)
  • 3c) Karoline Ulrike Luise (Homburg 26 Aug 1771-Rudolstadt 20 Jun 1854); m. Homburg 21 Jul 1791 Ludwig Friedrich II Fst von Schwarzburg-Rudolstadt (Rudolstadt 9 Aug 1767-Rudolstadt 28 Apr 1807)
  • 4c) Luise Ulrike (Homburg 26 Oct 1772-Rudolstadt 18 Sep 1854); m. Homburg 19 Jun 1793 Karl Pr von Schwarzburg-Rudolstadt (Rudolstadt 23 Aug 1771-Rudolstadt 4 Feb 1825)
  • 5c) Christiane Amalie (Homburg 29 Jun 1774-Dessau 3 Feb 1846); m. Homburg 12 Jun 1792 Friedrich Erbpr von Anhalt-Dessau (Dessau 27 Dec 1769-Dessau 27 May 1814)
  • 6c) Paul Emil (Frankfurt 27 Sep 1775-Homburg 16 May 1776)
  • 7c) Auguste Friederike (Homburg 28 Nov 1776-Ludwigslust 1 Apr 1871); m. Homburg 3 Apr 1818 Friedrich Ludwig, Hereditary Grand Duke of Mecklenburg-Schwerin (Ludwigslust 13 Jun 1778-Ludwigslust 29 Nov 1819)
  • 8c) Viktor (Homburg 24 Jan 1778-Homburg 14 Sep 1780)
  • 9c) PHILIPP August Friedrich, Landgrave of Hesse-Homburg (Homburg 11 Mar 1779-Homburg 15 Dec 1846); m.(morganatically) Graz 26 Jun 1838 Antonie Potoschnigg, cr Gfn von Naumburg 31 May 1838 (Fürstenfeld 26 Nov 1806-Homburg 21 Feb 1845)
  • 10c) GUSTAV Adolf Friedrich, Landgrave of Hesse-Homburg (Homburg 17 Feb 1781-Homburg 8 Sep 1848); m. Dessau 12 Feb 1818 Luise Pss of Anhalt-Dessau (Dessau 1 Mar 1798-Homburg 11 Jun 1858)
  • 1d) Karoline Amalie Elisabeth (Homburg 19 Mar 1819-Greiz 18 Jan 1872); m. Homburg 1 Oct 1839 Heinrich XX Fst Reuss zu Greiz (Offenbach 29 Jun 1794-Greiz 8 Nov 1859)
  • 2d) Elisabeth (Homburg 30 Sep 1823-Homburg 28 Jan 1864)
  • 3d) Friedrich Ludwig Heinrich Gustav (Homburg 6 Apr 1830-Bonn 4 Jan 1848)
  • 11c) FERDINAND Heinrich Friedrich, Landgrave of Hesse-Homburg (Homburg 26 Apr 1783-Homburg 24 Mar 1866)
  • 12c) Marie Anne Amalie (Homburg 13 Oct 1785-Berlin 14 Apr 1846); m. Berlin 12 Jan 1804 Wilhelm Pr of Prussia (Potsdam 3 Jul 1783-Berlin 28 Sep 1851)
  • 13c) Leopold Viktor Friedrich (Homburg 10 Feb 1787-k.a. Groß-Görschen 2 May 1813)
  • 2b) Marie Christine (Homburg 4 Nov 1749-Homburg May 1750)
  • 2a) Eugen (Homburg 9 Jun 1725-Homburg 21 Jul 1725)
  • 3a) Ulrike Sofie (Hötensleben 31 May 1726-Homburg 10 Dec 1792)
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. View more
Cookies settings
Accept
Decline
Privacy & Cookie policy
Privacy & Cookies policy
Cookies list
Cookie name Active

Privacy and Cookie Policy Last updated: 11 August 2026

Neue Gotha respects your privacy and is committed to handling personal data lawfully, fairly, and transparently. This Privacy and Cookie Policy explains who is responsible for personal data, what information we process, why we process it, how long we retain it, who may receive it, and the rights available to individuals under the General Data Protection Regulation (EU) 2016/679 (“GDPR”) and applicable national data-protection and electronic-communications law.

1. Who is responsible for your personal data?

The controller responsible for the processing described in this policy is:

  • Legal name: Neue Gotha Historical Register gUG
  • Trading or project name: Neue Gotha
  • Postal address: Musterstraße 12, 10115 Berlin, Germany
  • Email: editor@neuegotha.de
  • EU/EEA representative: Not applicable (the controller is established in Germany).
  • Data Protection Officer: No Data Protection Officer has been appointed. Privacy enquiries are handled through editor@neuegotha.de.

Questions about this policy or requests concerning personal data may be sent to the email or postal address above.

2. Scope of this policy

This policy applies to personal data processed through https://neuegotha.com, correspondence with the Neue Gotha editorial office, material submitted for editorial consideration, and editorial or archival records concerning identifiable living individuals.

It does not govern independent third-party websites or services linked from this website. Those providers are responsible for their own privacy practices.

3. Personal data we process and why

Processing activity Personal data Purpose Legal basis Retention
Website delivery, logging, and security IP address; date and time of access; requested page or file; referring page; browser, operating-system, and device information; error and security-event data Deliver the website, maintain availability, diagnose faults, prevent abuse, and protect the website and its users Article 6(1)(f) GDPR — our legitimate interests in operating a secure and reliable website. Where processing is required by law, Article 6(1)(c) GDPR may also apply. Routine access and error logs are retained for 14 days. Records isolated for investigation of a suspected security incident may be retained for up to 90 days after the incident is resolved, or longer where required for legal claims.
Editorial correspondence and enquiries Name, contact details, message content, correspondence history, and any documents or other information voluntarily provided Respond to enquiries, assess corrections or submissions, maintain editorial records, and protect legal rights Article 6(1)(f) GDPR — our legitimate interests in conducting editorial work and responding to correspondence; Article 6(1)(b) GDPR where processing is necessary to take steps at an individual’s request before entering into a contract; Article 6(1)(c) GDPR where retention or disclosure is legally required Correspondence is ordinarily retained for 24 months after the matter closes. Material required to document an editorial decision, resolve a dispute, meet a legal obligation, or establish, exercise, or defend a legal claim may be retained for the applicable limitation period.
Editorial, genealogical, and archival records Names; titles and styles; dates and places associated with public or genealogical events; family relationships; jurisdictions, offices, and public roles; images; biographical information; source and citation information; and correspondence relating to accuracy or provenance Research, document, preserve, verify, correct, and publish material concerning dynastic, genealogical, heraldic, and institutional history Article 6(1)(f) GDPR — our legitimate interests and those of readers, researchers, and institutions in maintaining an accurate historical and genealogical reference work, subject to a documented necessity and balancing assessment. Applicable national rules implementing Article 85 GDPR concerning freedom of expression and information may also apply. For as long as the information remains relevant to the legitimate editorial or archival purpose, subject to accuracy review, correction, restriction, erasure, and applicable archiving or legal requirements
Cookie-consent and language preferences Consent choice, language preference, cookie identifiers, and related technical information Remember privacy choices, demonstrate consent where required, and provide the language selected by the visitor Article 6(1)(f) GDPR for strictly necessary preference and consent-management functions; Article 6(1)(a) GDPR for optional storage, access, or associated processing based on consent As stated in the cookie table below
Optional external services IP address, page URL, device and browser information, language choice, and service-interaction data, depending on the provider Provide optional translation, embedded content, analytics, or similar features actually enabled on the website Article 6(1)(a) GDPR — consent. Non-essential services remain disabled until consent is given. As described for each service and by the relevant provider

We do not use personal data for solely automated decisions that produce legal effects or similarly significant effects concerning individuals.

4. Editorial and archival information obtained from other sources

Neue Gotha is an editorial and historical reference project. Some information in the register may concern identifiable living individuals and may not have been collected directly from those individuals.

Depending on the record, information may be obtained from official gazettes and public registers; archives and libraries; published books and scholarly works; institutional publications; reputable news sources; publicly accessible websites; submissions from the individual concerned or their authorised representative; family representatives; and other documented sources.

The categories of information may include the categories listed under “Editorial, genealogical, and archival records” above. The material may be made available to website visitors and may be indexed by search engines. Neue Gotha seeks to use relevant, proportionate, and appropriately sourced information and to distinguish documented fact from uncertainty or editorial interpretation.

Individuals may contact the editorial office to request access, correction, contextualisation, restriction, or erasure. Requests are assessed under the GDPR and applicable national law, taking into account accuracy, source integrity, the public interest, freedom of expression and information, archival considerations, and the rights and freedoms of other people. No provision of this policy removes a right granted by applicable law.

Neue Gotha does not intentionally publish special-category personal data or information concerning criminal convictions about living individuals unless a specific lawful basis and any additional legal condition have been identified and documented.

5. Cookies and similar technologies

Cookies are small text files stored on, or read from, a visitor’s device. Similar technologies may perform comparable functions. Some are strictly necessary for a website or a service expressly requested by the visitor. Others, including many analytics, advertising, social-media, translation, or embedded-content technologies, require prior consent under applicable EU electronic-communications rules.

Neue Gotha does not place or access non-essential cookies, or activate non-essential external services, before valid consent has been given. Visitors may accept or reject optional purposes separately and may withdraw consent at any time by selecting the permanently available “Cookie settings” control. Withdrawing consent does not affect processing that was lawful before withdrawal. Strictly necessary technologies cannot be disabled through the consent tool, but they may be controlled through browser settings where technically possible.

The following table reflects the technologies currently deployed on the website. It is updated whenever a plugin, host, analytics tool, embedded service, or cookie configuration changes.

Name Provider Purpose Category Duration Third-party access
_scc_session Neue Gotha / managed hosting and site-control provider Maintains a short-lived session for website security and site-control functions Strictly necessary Browser session The contracted hosting or site-control provider may access the identifier when providing technical support
_tccl_visit Neue Gotha / managed website-analytics provider Distinguishes a single website visit and reduces duplicate counting within the same session Analytics — disabled until consent 30 minutes Yes; the contracted analytics provider processes the identifier on Neue Gotha’s behalf
_tccl_visitor Neue Gotha / managed website-analytics provider Assigns a pseudonymous visitor identifier used to produce aggregated website-usage statistics Analytics — disabled until consent 12 months Yes; the contracted analytics provider processes the identifier on Neue Gotha’s behalf
googtrans Neue Gotha / Google Translate Stores or applies the visitor’s language selection for the translation feature Functional — disabled until consent 12 months Google may receive technical and service-interaction data when Google Translate is activated
ng_gt_default_applied Neue Gotha / website translation plugin Records whether the website’s default translation setting has been applied Functional — disabled until consent 24 hours No direct vendor access is assumed; Google may receive data if activation causes Google Translate to load
eu_cookies_bar_consent Neue Gotha / locally hosted EU Cookies Bar plugin Stores the visitor’s cookie choices and prevents the banner from being shown unnecessarily Strictly necessary 6 months No, provided the consent plugin remains locally hosted and does not transmit consent records to its developer
wordpress_test_cookie Neue Gotha / WordPress Checks whether the browser supports cookies when an authorised user visits the sign-in page Strictly necessary Browser session No; the cookie is processed by Neue Gotha and its contracted host

Authorised editorial users may receive WordPress authentication, security, or preference cookies when they sign in. wordpress_logged_in_[hash] maintains an authenticated session for up to two weeks when “Remember Me” is selected; wordpress_sec_[hash] protects administrative access for the session; and wp-settings-[user_id] stores an editor’s interface preferences for up to one year. These internal cookies are processed solely for editorial access and site administration.

6. Google Translate, web fonts, and other external content

Where enabled with the visitor’s consent, Neue Gotha may use Google Translate to provide machine-generated translations. Activating the service may cause the visitor’s browser to connect to Google and disclose technical information such as the IP address, requested page URL, browser or device information, and language or service-interaction data. Machine translations may contain errors and do not replace the original editorial text.

Website fonts are hosted locally by Neue Gotha and do not require a connection to Google. Google Translate remains an optional external service that is activated only after the visitor provides consent.

Information about Google’s processing is available in the Google Privacy Policy and Google’s explanation of how it uses information from sites and applications that use its services.

Embedded material from another website may allow that provider to process personal data as if the visitor had visited the provider directly. Non-essential embeds remain blocked until consent is obtained. Each enabled provider is identified in this policy and in the consent interface.

7. Recipients of personal data

Personal data may be disclosed only where necessary to:

  • hosting, content-delivery, backup, website-maintenance, email, security, and consent-management providers acting under contract;
  • translation, analytics, media, or other external-service providers selected by the visitor through the consent interface;
  • professional advisers, insurers, auditors, or other specialists where necessary to protect legal or operational interests;
  • courts, regulators, law-enforcement bodies, or public authorities where disclosure is required or permitted by law; and
  • the public and search engines where personal data form part of a lawfully published editorial or archival record.

8. International data transfers

Some service providers may process personal data outside the European Economic Area. Where the GDPR restricts such a transfer, Neue Gotha relies on an applicable European Commission adequacy decision or appropriate safeguards under Article 46 GDPR, such as the European Commission’s Standard Contractual Clauses, together with supplementary measures where required.

Cloudflare and Google may transfer limited technical information to recipients in the United States. Where the recipient is validly certified, the transfer is based on the European Commission’s adequacy decision for the EU–US Data Privacy Framework. Where that mechanism is unavailable or does not cover a transfer, the relevant provider’s European Commission Standard Contractual Clauses and supplementary technical and organisational measures are used. Information about the applicable safeguards, including how to obtain a copy, may be requested from editor@neuegotha.de.

9. How long we retain personal data

We retain personal data only for as long as necessary for the purposes described in this policy, including security, editorial integrity, source verification, dispute resolution, and compliance with legal obligations. The specific periods or criteria are stated in the processing and cookie tables above.

When a retention period ends, information is deleted or anonymised unless continued retention is required by law, is necessary for legal claims, or is justified by a documented editorial or archival purpose. Encrypted rolling backups are retained for 35 days and are then overwritten automatically, unless a backup has been isolated for incident recovery or a legal hold.

10. Security

Neue Gotha uses appropriate technical and organisational measures designed to protect personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure, or access. No method of internet transmission or electronic storage is completely secure, and absolute security cannot be guaranteed.

11. Your data-protection rights

Subject to the conditions and limitations in the GDPR and applicable national law, an individual may have the right to:

  • obtain confirmation as to whether personal data concerning them are processed and request access to those data;
  • request correction of inaccurate or incomplete personal data;
  • request erasure of personal data;
  • request restriction of processing;
  • object, on grounds relating to their particular situation, to processing based on legitimate interests;
  • receive personal data they provided in a structured, commonly used, machine-readable format and transmit those data to another controller where the right to portability applies;
  • withdraw consent at any time, without affecting the lawfulness of processing carried out before withdrawal; and
  • lodge a complaint with a competent data-protection supervisory authority.

To exercise a right, contact editor@neuegotha.de. Please identify the information or record concerned and the nature of the request. We may request information reasonably necessary to verify identity and protect personal data from unauthorised disclosure. Requests are normally answered within one month, subject to any extension permitted by law.

Where a request concerns published editorial or archival content, applicable rights may be limited where necessary and proportionate to reconcile data protection with freedom of expression and information or other rights recognised by law. Each request will be assessed individually.

12. Complaints

We encourage individuals to contact us first so that we can try to resolve a concern. Individuals also have the right to complain to the supervisory authority in the EU or EEA country of their habitual residence, place of work, or the place of the alleged infringement.

For this Berlin-based controller the supervisory authority is the Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin, Germany; telephone +49 30 13889-0; email mailbox@datenschutz-berlin.de; website https://www.datenschutz-berlin.de/.

13. Children

The website is intended as a general historical and reference resource and is not directed specifically at children. We do not knowingly request personal data directly from children for an online service requiring parental consent. If you believe a child has provided personal data inappropriately, please contact us.

14. Changes to this policy

We may update this policy when our processing activities, service providers, technologies, or legal obligations change. The current version will be published on this page with a revised “Last updated” date. Where required, we will provide additional notice or request renewed consent before introducing a new processing purpose.

Decline All
Save settings Accept All
Cookies settings