BIZTRAC BETA
Activities of excursion and event organisers

ARCTIC BREEZE AS

Org. no. 979889135 Limited company (AS) Tromsø Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 16.8m
Operating profit NOK 5.7m
Equity NOK 8.1m
Incorporated 1998
Employees 15
Share capital NOK 100,000

Announcements

Changes recorded in the Brønnøysund registers, collected continuously from the update feed.

  1. 13 Apr 2026 Register change

    Enhet endret i Enhetsregisteret

  2. 13 Jan 2026 Register change

    Enhet endret i Enhetsregisteret

  3. 25 Oct 2025 Register change

    Enhet endret i Enhetsregisteret

  4. 8 Apr 2025 Register change

    Enhet endret i Enhetsregisteret

  5. 12 Feb 2025 Register change

    Enhet endret i Enhetsregisteret

  6. 14 Jan 2025 Register change

    Enhet endret i Enhetsregisteret

  7. 2 Sep 2024 Register change

    Enhet endret i Enhetsregisteret

  8. 13 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  9. 1 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  10. 12 Aug 2023 Register change

    Enhet endret i Enhetsregisteret

  11. 11 Oct 2022 Register change

    Enhet endret i Enhetsregisteret

  12. 6 Aug 2022 Register change

    Enhet endret i Enhetsregisteret

  13. 13 Sep 2021 Register change

    Enhet endret i Enhetsregisteret

  14. 11 Sep 2021 Register change

    Enhet endret i Enhetsregisteret

  15. 15 Sep 2020 Register change

    Enhet endret i Enhetsregisteret

  16. 17 Aug 2020 Register change

    Enhet endret i Enhetsregisteret

  17. 11 Jun 2020 Register change

    Enhet endret i Enhetsregisteret

  18. 12 Mar 2020 Register change

    Enhet endret i Enhetsregisteret

  19. 1 Jan 2020 Register change

    Enhet endret i Enhetsregisteret

  20. 31 Dec 2019 Register change

    Enhet endret i Enhetsregisteret

  21. 2 Jul 2019 Register change

    Enhet endret i Enhetsregisteret

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.