BIZTRAC BETA
Business and other management consultancy activities

GRANHEIM INVEST AS

Org. no. 920253903 Limited company (AS) Ål Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 7.7m
Operating profit NOK 692,000
Equity NOK 1.2m
Incorporated 2017
Employees 8
Share capital NOK 30,000

Announcements

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

  1. 6 Jun 2026 Register change

    Enhet endret i Enhetsregisteret

  2. 2 Jun 2026 Register change

    Enhet endret i Enhetsregisteret

  3. 11 May 2026 Register change

    Enhet endret i Enhetsregisteret

  4. 13 Apr 2026 Register change

    Enhet endret i Enhetsregisteret

  5. 11 Mar 2026 Register change

    Enhet endret i Enhetsregisteret

  6. 11 Dec 2025 Register change

    Enhet endret i Enhetsregisteret

  7. 15 Oct 2025 Register change

    Enhet endret i Enhetsregisteret

  8. 5 Oct 2025 Address change

    Forretningsadresse endret

  9. 3 Jun 2025 Register change

    Enhet endret i Enhetsregisteret

  10. 4 Jun 2024 Register change

    Enhet endret i Enhetsregisteret

  11. 1 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  12. 25 May 2023 Register change

    Enhet endret i Enhetsregisteret

  13. 30 May 2022 Register change

    Enhet endret i Enhetsregisteret

  14. 11 May 2022 Register change

    Enhet endret i Enhetsregisteret

  15. 22 Jun 2021 Register change

    Enhet endret i Enhetsregisteret

  16. 19 May 2021 Register change

    Enhet endret i Enhetsregisteret

  17. 4 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. 3 Aug 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.