BIZTRAC BETA
Construction of residential and non-residential buildings

VORAA VERDI AS

Org. no. 917649006 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 567,000
Equity NOK 2.9m
Incorporated 2016
Share capital NOK 130,000

VORAA VERDI AS is registered as a limited company in Bærum, Akershus with organisation number 917649006. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 130,000, divided into 1000 shares. The company's stated purpose is: “Forvaltning og investering av kapital og eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 567,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 567,000
Equity
NOK 2.9m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns VORAA VERDI AS?

ANDREAS WEIDEMANN VORAA
VORAA VERDI AS
NOK 1.6m rev. · NOK 567,000 profit

VORAA VERDI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VORAA VERDI AS own?

VORAA VERDI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VORAA VERDI AS

Who owns VORAA VERDI AS?

ANDREAS WEIDEMANN VORAA is the largest registered owner, with 100.0%.

What is the revenue of VORAA VERDI AS?

VORAA VERDI AS had revenue of NOK 1.6m in 2024.

Who is the general manager of VORAA VERDI AS?

Andreas Weidemann Voraa is registered as general manager of VORAA VERDI AS.

Where is VORAA VERDI AS based?

VORAA VERDI AS has its business address in Haslum.

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.