BIZTRAC BETA
Business and other management consultancy activities

ERAKS DRIFT AS

Org. no. 918765859 Limited company (AS) Lier Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 218,000
Operating profit NOK −64,000
Equity NOK 768,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−64k kr).

ERAKS DRIFT AS is registered as a limited company in Lier, Buskerud with organisation number 918765859. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Levere konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 218,000 in revenue and NOK −64,000 in operating profit.

Key figures · 2025

Revenue
NOK 218,000
Operating profit
NOK −64,000
Equity
NOK 768,000
Est. value
NOK 603,000

Financial health · 2025

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

Who owns ERAKS DRIFT AS?

BJØRN SKARE
ERAKS DRIFT AS
NOK 218,000 rev. · NOK −64,000 profit

ERAKS DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERAKS DRIFT AS own?

ERAKS DRIFT AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ERAKS DRIFT AS

Who owns ERAKS DRIFT AS?

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

What is the revenue of ERAKS DRIFT AS?

ERAKS DRIFT AS had revenue of NOK 218,000 in 2025.

Who is the general manager of ERAKS DRIFT AS?

Bjørn Skare is registered as general manager of ERAKS DRIFT AS.

Where is ERAKS DRIFT AS based?

ERAKS DRIFT AS has its business address in Lier.

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.