BIZTRAC BETA
Construction of residential and non-residential buildings

OLASTUEN BYGG AS

Org. no. 913543351 Limited company (AS) Våler Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 23.8m
Operating profit NOK 427,000
Equity NOK 623,000
Incorporated 2014
Employees 17
Share capital NOK 230,000

OLASTUEN BYGG AS is registered as a limited company in Våler, Innlandet with organisation number 913543351. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014 and has 17 registered employees. Registered share capital is NOK 230,000, divided into 230 shares. The company's stated purpose is: “Drive med bygg- og anleggsvirksomhet, kjøp og salg av eiendom og utvikling av disse, samt alt som herved står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.8m in revenue and NOK 427,000 in operating profit.

Key figures · 2024

Revenue
NOK 23.8m
Operating profit
NOK 427,000
Equity
NOK 623,000
Est. value
NOK 1.5m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.8%
Satisfactory
Equity as a share of total capital

Who owns OLASTUEN BYGG AS?

OLASTUEN BYGG HOLDING AS
OLASTUEN BYGG AS
NOK 23.8m rev. · NOK 427,000 profit

OLASTUEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLASTUEN BYGG AS

Who owns OLASTUEN BYGG AS?

OLASTUEN BYGG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OLASTUEN BYGG AS?

OLASTUEN BYGG AS had revenue of NOK 23.8m in 2024.

Who is the general manager of OLASTUEN BYGG AS?

Georg Olastuen is registered as general manager of OLASTUEN BYGG AS.

Where is OLASTUEN BYGG AS based?

OLASTUEN BYGG 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.