BIZTRAC BETA
⚠DEKAGON AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Construction of residential and non-residential buildings

DEKAGON AS

Org. no. 932563509 Limited company (AS) Ringsaker Incorporated 2023 Bankrupt
Ownership graph ↗
Incorporated 2023
Share capital NOK 83,000
OverviewDetailsFinancialsKey figuresRoles and ownersOrganisationAnnouncementsPublic records

Announcements

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

  1. 11 Mar 2026 Register change

    Enhet endret i Enhetsregisteret

  2. 17 Feb 2026 Register change

    Enhet endret i Enhetsregisteret

  3. 16 Feb 2026 Bankruptcy

    Konkurs

  4. 13 Sep 2025 Register change

    Enhet endret i Enhetsregisteret

  5. 14 Jul 2025 Register change

    Enhet endret i Enhetsregisteret

  6. 10 Jul 2025 Register change

    Enhet endret i Enhetsregisteret

  7. 12 Jun 2025 Register change

    Enhet endret i Enhetsregisteret

  8. 13 Mar 2025 Register change

    Enhet endret i Enhetsregisteret

  9. 12 Feb 2025 Register change

    Enhet endret i Enhetsregisteret

  10. 14 Jan 2025 Register change

    Enhet endret i Enhetsregisteret

  11. 12 Dec 2024 Register change

    Enhet endret i Enhetsregisteret

  12. 12 Sep 2024 Register change

    Enhet endret i Enhetsregisteret

  13. 13 Jul 2024 Register change

    Enhet endret i Enhetsregisteret

  14. 12 Jun 2024 Register change

    Enhet endret i Enhetsregisteret

  15. 11 Apr 2024 Register change

    Enhet endret i Enhetsregisteret

  16. 5 Mar 2024 Register change

    Enhet endret i Enhetsregisteret

  17. 13 Feb 2024 Register change

    Enhet endret i Enhetsregisteret

  18. 26 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  19. 18 Dec 2023 Register change

    Enhet endret i Enhetsregisteret

  20. 4 Dec 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.