BIZTRAC BETA
Business and other management consultancy activities

DRIFTSKONSULT AS

Org. no. 979268580 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK −3.4m
Equity NOK 1.9m
Incorporated 1997
Employees 6
Share capital NOK 108,000

Signals

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

DRIFTSKONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 979268580. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1997 and has 6 registered employees. Registered share capital is NOK 108,000, divided into 540 shares. The company's stated purpose is: “Rådgivning, konsulenttjenester, salg og kjøp av varer og tjenester, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK −3.4m in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK −3.4m
Equity
NOK 1.9m
Est. value
NOK 8.1m

Financial health · 2024

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

Who owns DRIFTSKONSULT AS?

BJØRN EGGEN
DRIFTSKONSULT AS
NOK 6.9m rev. · NOK −3.4m profit

DRIFTSKONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRIFTSKONSULT AS

Who owns DRIFTSKONSULT AS?

BJØRN EGGEN is the largest registered owner, with 100.0%.

What is the revenue of DRIFTSKONSULT AS?

DRIFTSKONSULT AS had revenue of NOK 6.9m in 2024.

Who is the general manager of DRIFTSKONSULT AS?

Eirik Eggen is registered as general manager of DRIFTSKONSULT AS.

Where is DRIFTSKONSULT AS based?

DRIFTSKONSULT 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.