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

VEGÅRSHEI BYGG AS

Org. no. 916696167 Limited company (AS) Vegårshei Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 7.5m
Operating profit NOK 116,000
Equity NOK 1.1m
Incorporated 2016
Share capital NOK 40,000

VEGÅRSHEI BYGG AS is registered as a limited company in Vegårshei, Agder with organisation number 916696167. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Tømrer- og betongarbeid, konsulent- og tegnetjenester og hva som naturlig hører inn under dette. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.5m in revenue and NOK 116,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.5m
▼ −17 %
Operating profit
NOK 116,000
▼ −46 %
Equity
NOK 1.1m
▼ −12 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
31.0%
Good
Equity as a share of total capital

Who owns VEGÅRSHEI BYGG AS?

VEGÅRSHEI BYGG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEGÅRSHEI BYGG AS

Who owns VEGÅRSHEI BYGG AS?

Arnold Simonstad is the largest registered owner, with 25.0%.

What is the revenue of VEGÅRSHEI BYGG AS?

VEGÅRSHEI BYGG AS had revenue of NOK 7.5m in 2025.

Who is the general manager of VEGÅRSHEI BYGG AS?

Øystein Vierli is registered as general manager of VEGÅRSHEI BYGG AS.

Where is VEGÅRSHEI BYGG AS based?

VEGÅRSHEI BYGG AS has its business address in Vegårshei.

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.