BIZTRAC BETA
Other specialised construction activities in construction of buildings

VEGARD HOVLAND AS

Org. no. 932751038 Limited company (AS) Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 211,000
Equity NOK 56,000
Incorporated 2023
Employees 9
Share capital NOK 30,000

VEGARD HOVLAND AS is registered as a limited company in Hå, Rogaland with organisation number 932751038. The business is classified under other specialised construction activities in construction of buildings (NACE 43.420). The company was incorporated in 2023 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Grunn- og betongarbeid samt deltakelse i annen virksomhet med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 211,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
Operating profit
NOK 211,000
Equity
NOK 56,000
Est. value
NOK 740,000

Financial health · 2025

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

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

Who owns VEGARD HOVLAND AS?

VEGARD HOVLAND
VEGARD HOVLAND AS
NOK 8.7m rev. · NOK 211,000 profit

VEGARD HOVLAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEGARD HOVLAND AS

Who owns VEGARD HOVLAND AS?

VEGARD HOVLAND is the largest registered owner, with 100.0%.

What is the revenue of VEGARD HOVLAND AS?

VEGARD HOVLAND AS had revenue of NOK 8.7m in 2025.

Who is the general manager of VEGARD HOVLAND AS?

Vegard Hovland is registered as general manager of VEGARD HOVLAND AS.

Where is VEGARD HOVLAND AS based?

VEGARD HOVLAND AS has its business address in Vigrestad.

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.