BIZTRAC BETA
Rental and operating of own or leased real estate

VÅLER BYGG EIENDOM AS

Org. no. 939164731 Limited company (AS) Våler Incorporated 1985 Active
Ownership graph ↗
Revenue 2024 NOK 683,000
Operating profit NOK 323,000
Equity NOK 1.4m
Incorporated 1985
Share capital NOK 300,000

VÅLER BYGG EIENDOM AS is registered as a limited company in Våler, Innlandet with organisation number 939164731. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1985. Registered share capital is NOK 300,000. The company's stated purpose is: “Utleie, omsetning og utvikling av eiendom samt utleie av utstyr tilknyttet bygg- og anleggsbrensjen og annen virksomhet som faller naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 683,000 in revenue and NOK 323,000 in operating profit.

Key figures · 2024

Revenue
NOK 683,000
Operating profit
NOK 323,000
Equity
NOK 1.4m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns VÅLER BYGG EIENDOM AS?

GUNNAR SKJÆRET
VÅLER BYGG EIENDOM AS
NOK 683,000 rev. · NOK 323,000 profit

VÅLER BYGG EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VÅLER BYGG EIENDOM AS

Who owns VÅLER BYGG EIENDOM AS?

GUNNAR SKJÆRET is the largest registered owner, with 80.0%.

What is the revenue of VÅLER BYGG EIENDOM AS?

VÅLER BYGG EIENDOM AS had revenue of NOK 683,000 in 2024.

Who is the general manager of VÅLER BYGG EIENDOM AS?

Jan Ivar Skjæret is registered as general manager of VÅLER BYGG EIENDOM AS.

Where is VÅLER BYGG EIENDOM AS based?

VÅLER BYGG EIENDOM AS has its business address in Våler I Solør.

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.