BIZTRAC BETA
Uoppgitt

VALBERG GENERATOR AS

Org. no. 934752430 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

VALBERG GENERATOR AS is registered as a limited company in Asker, Akershus with organisation number 934752430. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med investering i aksjer og verdipapirer, inkludert, men ikke begrenset til, kjøp, salg og forvaltning av aksjer, obligasjoner, derivater og andre finansielle instrumenter. I tillegg til konsulenttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2024

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

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

Who owns VALBERG GENERATOR AS?

LARS HENNING VIKJORD
VALBERG GENERATOR AS
NOK 0 rev. · NOK 0 profit

VALBERG GENERATOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VALBERG GENERATOR AS own?

VALBERG GENERATOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VALBERG GENERATOR AS

Who owns VALBERG GENERATOR AS?

LARS HENNING VIKJORD is the largest registered owner, with 100.0%.

What is the revenue of VALBERG GENERATOR AS?

VALBERG GENERATOR AS had revenue of NOK 0 in 2024.

Where is VALBERG GENERATOR AS based?

VALBERG GENERATOR AS has its business address in Vollen.

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.