JBL Expedition South Seas I and II

JBL Expedition South Seas I and II

Deadly cube jellyfish or a harmless species?

One evening at the stern of the Aquatiki III, our group members were watching the sharks as usual, when one of us saw a jellyfish. We immediately found a jar and caught it. It was undoubtedly a cube jellyfish! The notorious Australian sea wasp (Chironex fleckeri), the cause of many fatal accidents in humans, belongs to this group.

On closer inspection, however, it turned out that it was only a slightly poisonous species of cube jellyfish. And we only ever saw the jellyfish at one anchorage. We quickly learnt why. The anchor buoy lay at a depth of 60 m on a reef slope that went several hundred metres further down. Deep-sea plankton, attracted by the light, came to the surface at night there. A biologist had reported in a specialist magazine that she was able to attract and photograph many unknown deep-sea organisms using a light source at a depth of 30 m above such a deep-sea slope.

After the "jellyfish evening", we often fished for plankton in the dark and examined it under the microscope. Unfortunately, the outer areas of the atolls were often very low in plankton and many of the organisms we caught were far too large for our microscope. But it was exciting every time!

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.
I accept the YouTube Terms of Service and confirm that I have read and understood the YouTube Terms of Service .

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.