BIZTRAC BETA
PRESIS BOLIG AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Buying and selling of own real estate

PRESIS BOLIG AS

Org. no. 922286302 Limited company (AS) Tromsø Incorporated 2019 Bankrupt
Ownership graph ↗
Incorporated 2019
Share capital NOK 30,000

Announcements

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

  1. 11 Aug 2025 Register change

    Enhet endret i Enhetsregisteret

  2. 19 Jun 2025 Register change

    Enhet endret i Enhetsregisteret

  3. 18 Jun 2025 Register change

    Enhet endret i Enhetsregisteret

  4. 12 Apr 2025 Register change

    Enhet endret i Enhetsregisteret

  5. 16 Jul 2024 Register change

    Enhet endret i Enhetsregisteret

  6. 1 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  7. 14 Nov 2023 Register change

    Enhet endret i Enhetsregisteret

  8. 27 Jul 2023 Register change

    Enhet endret i Enhetsregisteret

  9. 12 Jul 2023 Register change

    Enhet endret i Enhetsregisteret

  10. 12 Jan 2023 Register change

    Enhet endret i Enhetsregisteret

  11. 1 Sep 2022 Register change

    Enhet endret i Enhetsregisteret

  12. 14 Dec 2021 Register change

    Enhet endret i Enhetsregisteret

  13. 12 Oct 2021 Register change

    Enhet endret i Enhetsregisteret

  14. 28 Apr 2021 Register change

    Enhet endret i Enhetsregisteret

  15. 11 Mar 2021 Register change

    Enhet endret i Enhetsregisteret

  16. 11 Jan 2021 Register change

    Enhet endret i Enhetsregisteret

  17. 12 Nov 2020 Register change

    Enhet endret i Enhetsregisteret

  18. 27 Aug 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. 31 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.