biztrac. BETA
COMPANY REGISTER PROFILE
914043034 ORG. NO. 2023 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

HYTTEUTVIKLING AS

Org. no. 914043034 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK −926,000
Incorporated 2014
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2023 Bokført egenkapital er negativ (−926k kr).
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−17k kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.

HYTTEUTVIKLING AS is registered as a limited company in Bærum, Akershus with organisation number 914043034. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling, utbygging og investering i fast eiendom, og alt som står i naturlig sammenheng med dette.”.

Former names: RAULAND HYTTEUTVIKLING AS

Key figures · 2023

Operating profit
NOK −17,000
▲ +9 %
Equity
NOK −926,000
▼ −1 %

Financial health · 2023

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-8.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HYTTEUTVIKLING AS?

HYTTEUTVIKLING AS
· NOK −17,000 profit

HYTTEUTVIKLING AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2023.

All shareholders and roles →

Frequently asked questions about HYTTEUTVIKLING AS

Who owns HYTTEUTVIKLING AS?

DRIFT SNPH AS is the largest registered owner, with 100.0%.

Where is HYTTEUTVIKLING AS based?

HYTTEUTVIKLING AS has its business address in Lysaker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.