BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

PETO AS

Org. no. 961959497 Limited company (AS) Lebesby Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 86,000
Operating profit NOK −257,000
Equity NOK 1.8m
Incorporated 1991
Share capital NOK 200,000

Announcements

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

  1. 21 May 2026 Register change

    Enhet endret i Enhetsregisteret

  2. 8 Apr 2025 Register change

    Enhet endret i Enhetsregisteret

  3. 19 Feb 2025 Register change

    Enhet endret i Enhetsregisteret

  4. 4 Jun 2024 Register change

    Enhet endret i Enhetsregisteret

  5. 1 Jan 2024 Register change

    Enhet endret i Enhetsregisteret

  6. 16 Dec 2023 Register change

    Enhet endret i Enhetsregisteret

  7. 21 Jun 2023 Register change

    Enhet endret i Enhetsregisteret

  8. 14 Dec 2022 Register change

    Enhet endret i Enhetsregisteret

  9. 24 Nov 2022 Register change

    Enhet endret i Enhetsregisteret

  10. 23 Nov 2022 Register change

    Enhet endret i Enhetsregisteret

  11. 12 Sep 2022 Register change

    Enhet endret i Enhetsregisteret

  12. 12 Jul 2022 Register change

    Enhet endret i Enhetsregisteret

  13. 17 Mar 2022 Register change

    Enhet endret i Enhetsregisteret

  14. 12 Aug 2021 Register change

    Enhet endret i Enhetsregisteret

  15. 3 Apr 2021 Register change

    Enhet endret i Enhetsregisteret

  16. 17 Aug 2020 Register change

    Enhet endret i Enhetsregisteret

  17. 22 Jun 2020 Register change

    Enhet endret i Enhetsregisteret

  18. 12 Feb 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. 19 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.