BIZTRAC BETA
Public relations and communication activities

SJO KOMMUNIKASJON AS

Org. no. 940681731 Limited company (AS) Asker Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 10,000
Operating profit NOK −95,000
Equity NOK 313,000
Incorporated 1986
Share capital NOK 30,000

Announcements

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

  1. 18 May 2026 Register change

    Enhet endret i Enhetsregisteret

  2. 25 Jun 2025 Register change

    Enhet endret i Enhetsregisteret

  3. 4 Jun 2025 Register change

    Enhet endret i Enhetsregisteret

  4. 6 May 2025 Register change

    Enhet endret i Enhetsregisteret

  5. 5 May 2025 Register change

    Enhet endret i Enhetsregisteret

  6. 22 Apr 2025 Register change

    Enhet endret i Enhetsregisteret

  7. 8 Apr 2025 Register change

    Enhet endret i Enhetsregisteret

  8. 30 May 2024 Register change

    Enhet endret i Enhetsregisteret

  9. 13 Feb 2024 Register change

    Enhet endret i Enhetsregisteret

  10. 1 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  11. 26 Jun 2023 Register change

    Enhet endret i Enhetsregisteret

  12. 14 Feb 2023 Register change

    Enhet endret i Enhetsregisteret

  13. 25 May 2022 Register change

    Enhet endret i Enhetsregisteret

  14. 14 Jan 2022 Register change

    Enhet endret i Enhetsregisteret

  15. 20 Apr 2021 Register change

    Enhet endret i Enhetsregisteret

  16. 28 Dec 2020 Register change

    Enhet endret i Enhetsregisteret

  17. 13 Oct 2020 Register change

    Enhet endret i Enhetsregisteret

  18. 14 Sep 2020 Register change

    Enhet endret i Enhetsregisteret

  19. 2 Apr 2020 Register change

    Enhet endret i Enhetsregisteret

  20. 1 Jan 2020 Register change

    Enhet endret i Enhetsregisteret

  21. 31 Dec 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.