BIZTRAC BETA
Development of building projects

VARDETANGEN EIENDOM AS

Org. no. 980008428 Limited company (AS) Bergen Incorporated 1998 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK −3.7m
Incorporated 1998
Share capital NOK 3.5m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−25k kr).

VARDETANGEN EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 980008428. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1998. Registered share capital is NOK 3.5m, divided into 3000 shares. The company's stated purpose is: “Erverv, utvikling og drift av fast eiendom og alt som er naturlig forbundet med dette, samt delta med eierandeler i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −25,000
Equity
NOK −3.7m

Financial health · 2024

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

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

Who owns VARDETANGEN EIENDOM AS?

NISTADGRUPPEN AS
VARDETANGEN EIENDOM AS
· NOK −25,000 profit

VARDETANGEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VARDETANGEN EIENDOM AS own?

VARDETANGEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VARDETANGEN EIENDOM AS

Who owns VARDETANGEN EIENDOM AS?

NISTADGRUPPEN AS is the largest registered owner, with 50.0%.

Who is the general manager of VARDETANGEN EIENDOM AS?

Pål Magne Hisdal is registered as general manager of VARDETANGEN EIENDOM AS.

Where is VARDETANGEN EIENDOM AS based?

VARDETANGEN EIENDOM AS has its business address in Bergen.

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.