Why is the KH higher than the GH?

Many aquarium owners think that the general hardness represents the total of all minerals and the carbonate hardness only a part of it. Then how can the carbonate hardness sometimes be higher than the total of minerals?

In a large number, indeed practically in all tropical waters, however we find just this situation: In Lake Malawi and Lake Tanganyika the KH lies significantly above the GH, and also in many rivers we can find a low KH, although a GH is not measurable. If you take a close look at the definition of the values, you will notice that the GH doesn’t represent the total of minerals but only the sum of calcium and magnesium. Actually it should be named Ca-Mg hardness! On the other hand the carbonate hardness indicates the quantity of carbonates (HCO3) and bicarbonates (HCO3)2. Non-chemist can’t be expected to understand what this means. But it’s a fact that both forms of carbonate are bound to metals, which normally would be calcium, magnesium, potassium or sodium. The KH doesn’t care what metal it is bound to. If bound to Ca or Mg, there is also a GH present. But if it is bound to K or Na there is a KH present, even if no GH components (Ca and Mg) are available. Since a lot of waters have no calcium and magnesium, their GH is not measurable. But there are often few quantities of carbonates present, which are bound to potassium or sodium. And then you can measure the KH but not the GH. Okay?

If not, just read these lines a few times again. It mostly becomes clearer then. It’s indeed a really interesting situation which explains the results of GH and KH tests with a basic knowledge of chemistry!

© 26.02.2018
Heiko Blessin
Heiko Blessin
Dipl.-Biologe

Tauchen, Fotografie, Aquaristik, Haie, Motorrad

Comments

A word about cookies before we continue

The JBL Homepage also uses several types of cookies to provide you with full functionality and many services: We require technical and functional cookies to ensure that everything works when you visit this website. We also use cookies for marketing purposes. This ensures that we recognise you when you visit our extensive site again, that we can measure the success of our campaigns and that the personalisation cookies allow us to address you individually and directly, adapted to your needs - even outside our website. You can determine at any time - even at a later date - which cookies you allow and which you do not allow (more on this under "Change settings").

The JBL website uses several types of cookies to provide you with full functionality and many services: Technical and functional cookies are absolutely necessary so that everything works when you visit this website. In addition, we use cookies for marketing purposes. You can determine at any time - even at a later date - which cookies you allow and which you do not (more on this under "Change settings").

Our data protection declaration tells you how we process personal data and what purposes we use the data processing for. tells you how we process personal data and what purposes we use the data processing for. Please confirm the use of all cookies by clicking "Accept" - and you're on your way.

Are you over 16 years old? Then confirm the use of all cookies with "Noticed" and you are ready to go.

Choose your cookie settings

Technical and functional cookies, so that everything works when you visit our website.
Marketing cookies, so that we recognize you on our pages and can measure the success of our campaigns.

PUSH messages from JBL

What are PUSH messages? As part of the W3C standard, web notifications define an API for end-user notifications that are sent to the user's desktop and/or mobile devices via the browser. Notifications appear on the end devices as they are familiar to the end user from apps installed on the device (e.g. emails). Notifications appear on the end user’s device, just like an app (e.g. for emails) installed on the device.

These notifications enable a website operator to contact its users whenever they have a browser open - it doesn’t matter whether the user is currently visiting the website or not.

To be able to send web push notifications, all you need is a website with a web push code installed. This allows brands without apps to take advantage of many of the benefits of push notifications (personalised real-time communications at just the right moment).

Web notifications are part of the W3C standard and define an API for end user notifications. A notification makes it possible to inform the user about an event, such as a new blog post, outside the context of a website.

JBL GmbH & Co. KG provides this service free of charge, and it is easy to activate or deactivate.