BIZTRAC BETA
⚠TRUE VESTERÅLEN HOTEL AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Hotels and similar accommodation

TRUE VESTERÅLEN HOTEL AS

Org. no. 932135841 Limited company (AS) Sortland Incorporated 2023 Bankrupt
Ownership graph ↗
Incorporated 2023
Share capital NOK 30,000
OverviewDetailsFinancialsKey figuresRoles and ownersOrganisationAnnouncements

Announcements

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

  1. 11 Feb 2026 Register change

    Enhet endret i Enhetsregisteret

  2. 8 Feb 2026 Register change

    Enhet endret i Enhetsregisteret

  3. 4 Feb 2026 Bankruptcy

    Konkurs

  4. 13 Jan 2026 Register change

    Enhet endret i Enhetsregisteret

  5. 15 Oct 2025 Register change

    Enhet endret i Enhetsregisteret

  6. 11 Aug 2025 Register change

    Enhet endret i Enhetsregisteret

  7. 14 Jul 2025 Register change

    Enhet endret i Enhetsregisteret

  8. 12 Jun 2025 Register change

    Enhet endret i Enhetsregisteret

  9. 7 May 2025 Register change

    Enhet endret i Enhetsregisteret

  10. 6 May 2025 Register change

    Enhet endret i Enhetsregisteret

  11. 12 Apr 2025 Register change

    Enhet endret i Enhetsregisteret

  12. 14 Jan 2025 Register change

    Enhet endret i Enhetsregisteret

  13. 17 Nov 2024 Register change

    Enhet endret i Enhetsregisteret

  14. 12 Sep 2024 Register change

    Enhet endret i Enhetsregisteret

  15. 13 Jul 2024 Register change

    Enhet endret i Enhetsregisteret

  16. 21 May 2024 Register change

    Enhet endret i Enhetsregisteret

  17. 18 Mar 2024 Register change

    Enhet endret i Enhetsregisteret

  18. 12 Mar 2024 Register change

    Enhet endret i Enhetsregisteret

  19. 3 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  20. 26 Sep 2023 New registration

    Ny enhet registrert 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.