BIZTRAC BETA
Civil engineering activities

BE UTVIKLING AS

Org. no. 985862265 Limited company (AS) Drammen Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 286,000
Equity NOK 1.2m
Incorporated 2003
Share capital NOK 100,000

BE UTVIKLING AS is registered as a limited company in Drammen, Buskerud with organisation number 985862265. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av varer, kjøp og salg av fast eiendom, konsulenttjenester, herunder å delta i andre selskaper med lignende virksomhet samt annet med tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 286,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 286,000
Equity
NOK 1.2m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns BE UTVIKLING AS?

FRØYDAR AS
BE UTVIKLING AS
NOK 1.7m rev. · NOK 286,000 profit

BE UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BE UTVIKLING AS own?

BE UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BE UTVIKLING AS

Who owns BE UTVIKLING AS?

FRØYDAR AS is the largest registered owner, with 100.0%.

What is the revenue of BE UTVIKLING AS?

BE UTVIKLING AS had revenue of NOK 1.7m in 2025.

Who is the general manager of BE UTVIKLING AS?

Nils Gunnar Egenæs is registered as general manager of BE UTVIKLING AS.

Where is BE UTVIKLING AS based?

BE UTVIKLING AS has its business address in Drammen.

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.