BIZTRAC BETA
Rental and operating of own or leased real estate

WERGELAND BOLIGUTVIKLING AS

Org. no. 913106520 Limited company (AS) Osterøy Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −556,000
Equity NOK 3.2m
Incorporated 2014
Share capital NOK 30,000

Signals

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

WERGELAND BOLIGUTVIKLING AS is registered as a limited company in Osterøy, Vestland with organisation number 913106520. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Næringsdrift, i hovedsak kjøp og salg av fast eiendom og alt hva herved er forbundet, investeringsvirksomhet og deltakelse i andre virksomheter.”.

Key figures · 2024

Operating profit
NOK −556,000
Equity
NOK 3.2m
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.8%
Good
Equity as a share of total capital

Who owns WERGELAND BOLIGUTVIKLING AS?

SAGA BOLIG AS
WERGELAND BOLIGUTVIKLING AS
· NOK −556,000 profit

WERGELAND BOLIGUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does WERGELAND BOLIGUTVIKLING AS own?

WERGELAND BOLIGUTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WERGELAND BOLIGUTVIKLING AS

Who owns WERGELAND BOLIGUTVIKLING AS?

SAGA BOLIG AS is the largest registered owner, with 50.0%.

Who is the general manager of WERGELAND BOLIGUTVIKLING AS?

Johannes Seim Mjelde is registered as general manager of WERGELAND BOLIGUTVIKLING AS.

Where is WERGELAND BOLIGUTVIKLING AS based?

WERGELAND BOLIGUTVIKLING AS has its business address in Haus.

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.