BIZTRAC BETA
AVERION SØR ØST AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Business and other management consultancy activities

AVERION SØR ØST AS

Org. no. 998528984 Limited company (AS) Sandefjord Incorporated 2012 Bankrupt
Ownership graph ↗
Incorporated 2012
Share capital NOK 57,000

Announcements

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

  1. 11 Nov 2025 Register change

    Enhet endret i Enhetsregisteret

  2. 28 Oct 2025 Register change

    Enhet endret i Enhetsregisteret

  3. 27 Oct 2025 Bankruptcy

    Konkurs

  4. 14 May 2025 Register change

    Enhet endret i Enhetsregisteret

  5. 14 Jan 2025 Register change

    Enhet endret i Enhetsregisteret

  6. 12 Nov 2024 Register change

    Enhet endret i Enhetsregisteret

  7. 11 Nov 2024 Register change

    Enhet endret i Enhetsregisteret

  8. 15 May 2024 Register change

    Enhet endret i Enhetsregisteret

  9. 1 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  10. 20 Jul 2023 Register change

    Enhet endret i Enhetsregisteret

  11. 14 Feb 2023 Register change

    Enhet endret i Enhetsregisteret

  12. 21 Jul 2022 Register change

    Enhet endret i Enhetsregisteret

  13. 16 Sep 2021 Register change

    Enhet endret i Enhetsregisteret

  14. 11 Jan 2021 Register change

    Enhet endret i Enhetsregisteret

  15. 13 Oct 2020 Register change

    Enhet endret i Enhetsregisteret

  16. 12 Oct 2020 Register change

    Enhet endret i Enhetsregisteret

  17. 1 Jan 2020 Register change

    Enhet endret i Enhetsregisteret

  18. 31 Dec 2019 Register change

    Enhet endret i Enhetsregisteret

  19. 7 Sep 2019 Register change

    Enhet endret i Enhetsregisteret

  20. 13 Jul 2019 Register change

    Enhet endret i Enhetsregisteret

  21. 12 Jun 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.