BIZTRAC BETA
Investigation and private security activities

RISIKO RESPONS AS

Org. no. 815000072 Limited company (AS) Moss Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 172,000
Operating profit NOK 56,000
Equity NOK −88,000
Incorporated 2015
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. 2 Aug 2025 Register change

    Enhet endret i Enhetsregisteret

  3. 24 Sep 2024 Register change

    Enhet endret i Enhetsregisteret

  4. 11 Apr 2024 Register change

    Enhet endret i Enhetsregisteret

  5. 1 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  6. 13 Nov 2023 Register change

    Enhet endret i Enhetsregisteret

  7. 3 Jun 2023 Register change

    Enhet endret i Enhetsregisteret

  8. 12 Jan 2023 Register change

    Enhet endret i Enhetsregisteret

  9. 28 May 2022 Register change

    Enhet endret i Enhetsregisteret

  10. 14 Feb 2022 Register change

    Enhet endret i Enhetsregisteret

  11. 24 Aug 2021 Register change

    Enhet endret i Enhetsregisteret

  12. 12 Jun 2021 Register change

    Enhet endret i Enhetsregisteret

  13. 11 Mar 2021 Register change

    Enhet endret i Enhetsregisteret

  14. 1 Feb 2021 Register change

    Enhet endret i Enhetsregisteret

  15. 17 Jun 2020 Register change

    Enhet endret i Enhetsregisteret

  16. 12 Feb 2020 Register change

    Enhet endret i Enhetsregisteret

  17. 1 Jan 2020 Register change

    Enhet endret i Enhetsregisteret

  18. 31 Dec 2019 Register change

    Enhet endret i Enhetsregisteret

  19. 11 Nov 2019 Register change

    Enhet endret i Enhetsregisteret

  20. 15 Jun 2019 Register change

    Enhet endret i Enhetsregisteret

  21. 11 Jun 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.