BIZTRAC BETA
Business and other management consultancy activities

ELVEBYEN PROSJEKT AS

Org. no. 915936792 Limited company (AS) Drammen Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −81,000
Equity NOK 52.7m
Incorporated 2015
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−81k kr).

ELVEBYEN PROSJEKT AS is registered as a limited company in Drammen, Buskerud with organisation number 915936792. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Eiendomsselskap, herunder å investere i eiendom, aksjer, obligasjoner, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette. Selskapet skal også drive prosjektledelse og teknisk rådgivning.”.

Key figures · 2024

Operating profit
NOK −81,000
Equity
NOK 52.7m
Est. value
NOK 28.1m

Financial health · 2024

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

Who owns ELVEBYEN PROSJEKT AS?

ELVEBYEN INVEST AS
ELVEBYEN PROSJEKT AS
· NOK −81,000 profit

ELVEBYEN PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ELVEBYEN PROSJEKT AS own?

ELVEBYEN PROSJEKT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELVEBYEN PROSJEKT AS

Who owns ELVEBYEN PROSJEKT AS?

ELVEBYEN INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of ELVEBYEN PROSJEKT AS?

Per Inge Haugan is registered as general manager of ELVEBYEN PROSJEKT AS.

Where is ELVEBYEN PROSJEKT AS based?

ELVEBYEN PROSJEKT 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.