BIZTRAC BETA
Construction of residential and non-residential buildings

OPTIMAL BYGG AS

Org. no. 930157082 Limited company (AS) Vestnes Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 125,000
Equity NOK −155,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−155k kr).

OPTIMAL BYGG AS is registered as a limited company in Vestnes, Møre og Romsdal with organisation number 930157082. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppføring av bygninger, riving av bygninger og andre konstruksjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 125,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 125,000
Equity
NOK −155,000
Est. value
NOK 846,000

Financial health · 2024

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-39.1%
Weak
Equity as a share of total capital

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

Who owns OPTIMAL BYGG AS?

DAG RUNE VIGGEN
OPTIMAL BYGG AS
NOK 2.2m rev. · NOK 125,000 profit

OPTIMAL BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPTIMAL BYGG AS

Who owns OPTIMAL BYGG AS?

DAG RUNE VIGGEN is the largest registered owner, with 100.0%.

What is the revenue of OPTIMAL BYGG AS?

OPTIMAL BYGG AS had revenue of NOK 2.2m in 2025.

Who is the general manager of OPTIMAL BYGG AS?

Dag Rune Viggen is registered as general manager of OPTIMAL BYGG AS.

Where is OPTIMAL BYGG AS based?

OPTIMAL BYGG AS has its business address in Vestnes.

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.