BIZTRAC BETA
Preventive health care activities

PEOPLE AT WORK AS

Org. no. 921058497 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −1.0m
Equity NOK 4.0m
Incorporated 2018
Share capital NOK 33,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,0 mill kr).

PEOPLE AT WORK AS is registered as a limited company in Oslo, Oslo with organisation number 921058497. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2018. Registered share capital is NOK 33,000, divided into 1100 shares. The company's stated purpose is: “Konsulentvirksomhet knyttet til å redusere sykefravær. Selskapets formål er å redusere korttidsfraværet i virksomheter gjennom systematisk arbeid med beste praksis.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −1.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −1.0m
Equity
NOK 4.0m
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
5.81
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
82.8%
Very good
Equity as a share of total capital

Who owns PEOPLE AT WORK AS?

PROSESSPARTNER AS
PEOPLE AT WORK AS
NOK 1.1m rev. · NOK −1.0m profit

PEOPLE AT WORK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PEOPLE AT WORK AS

Who owns PEOPLE AT WORK AS?

PROSESSPARTNER AS is the largest registered owner, with 90.9%.

What is the revenue of PEOPLE AT WORK AS?

PEOPLE AT WORK AS had revenue of NOK 1.1m in 2024.

Who is the general manager of PEOPLE AT WORK AS?

Anders Hovengen Sætre is registered as general manager of PEOPLE AT WORK AS.

Where is PEOPLE AT WORK AS based?

PEOPLE AT WORK AS has its business address in Oslo.

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.