biztrac. BETA
COMPANY REGISTER PROFILE
933814726 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

OLAV WIGESTRAND AS

Org. no. 933814726 Limited company (AS) Stavanger Incorporated 2024 Active
Revenue 2025 NOK 84,000
Operating profit NOK 13,000
Equity NOK 40,000
Incorporated 2024
Share capital NOK 30,000

OLAV WIGESTRAND AS is registered as a limited company in Stavanger, Rogaland with organisation number 933814726. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forvaltning og investeringsselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 84,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 84,000
Operating profit
NOK 13,000
Equity
NOK 40,000
▲ +33 %
Est. value
NOK 53,000

Financial health · 2025

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
32.5%
Weak
Equity as a share of total capital

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

Who owns OLAV WIGESTRAND AS?

OLAV WIGESTRAND AS
NOK 84,000 rev. · NOK 13,000 profit

OLAV WIGESTRAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAV WIGESTRAND AS

Who owns OLAV WIGESTRAND AS?

Olav Wigestrand is the largest registered owner, with 100.0%.

What is the revenue of OLAV WIGESTRAND AS?

OLAV WIGESTRAND AS had revenue of NOK 84,000 in 2025.

Who is the general manager of OLAV WIGESTRAND AS?

Olav Wigestrand is registered as general manager of OLAV WIGESTRAND AS.

Where is OLAV WIGESTRAND AS based?

OLAV WIGESTRAND AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.