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

FLYT SERVICE AS

Org. no. 928655156 Limited company (AS) Oslo Incorporated 2021 Bankrupt
Ownership graph ↗
Incorporated 2021
Share capital NOK 100,000

Announcements

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

  1. 13 Apr 2026 Register change

    Enhet endret i Enhetsregisteret

  2. 30 Mar 2026 Register change

    Enhet endret i Enhetsregisteret

  3. 28 Mar 2026 Bankruptcy

    Konkurs

  4. 12 Feb 2026 Register change

    Enhet endret i Enhetsregisteret

  5. 11 Dec 2025 Register change

    Enhet endret i Enhetsregisteret

  6. 12 Jun 2025 Register change

    Enhet endret i Enhetsregisteret

  7. 9 Apr 2025 Register change

    Enhet endret i Enhetsregisteret

  8. 12 Feb 2025 Register change

    Enhet endret i Enhetsregisteret

  9. 23 May 2024 Register change

    Enhet endret i Enhetsregisteret

  10. 11 Apr 2024 Register change

    Enhet endret i Enhetsregisteret

  11. 30 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  12. 11 Dec 2023 Register change

    Enhet endret i Enhetsregisteret

  13. 14 Nov 2023 Register change

    Enhet endret i Enhetsregisteret

  14. 12 Oct 2023 Register change

    Enhet endret i Enhetsregisteret

  15. 14 Aug 2023 Register change

    Enhet endret i Enhetsregisteret

  16. 26 Apr 2023 Register change

    Enhet endret i Enhetsregisteret

  17. 14 Dec 2022 Register change

    Enhet endret i Enhetsregisteret

  18. 6 Dec 2022 Register change

    Enhet endret i Enhetsregisteret

  19. 2 Jun 2022 Register change

    Enhet endret i Enhetsregisteret

  20. 7 Feb 2022 Register change

    Enhet endret i Enhetsregisteret

  21. 1 Feb 2022 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.