Abstract

Investigations into the 0-group fish in the Barents Sea have been carried out since 1965, with the goal of estimating the abundance of 0-group fish. 0-group abundance indices have been used in the assessment of the recruitment level and in recruitment variability studies. However, the ecological importance of the 0-group fish in the Barents Sea has been less studied. Although 0-group capelin, herring, cod and haddock are widely distributed in the Barents Sea, the central area seems to be the most important, accounting for approximately 50–80% of the annual biomass. The total biomass of the four most abundant 0-group fish species can be up to 3.3 million tonnes, with an average of 1.3 million tonnes (1993–2009). Wide distribution and high biomass of pelagically distributed 0-group fish make these fishes an important element in the energy transport between different trophic levels and different geographical areas, having a critical impact on the entire Barents Sea ecosystem. In recent years, capelin have shown a pronounced northward shift in biomass distribution, and several successive strong year classes occurred during warm temperature conditions. Cod biomasses were unexpectedly low during warm years and were positively correlated with spawning stock biomass, while the correlation with temperature was not significant. Haddock and herring show, as expected, increasing biomass with increased temperature when the spawning stock is at a sufficiently high level.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.