biztrac. BETA
COMPANY REGISTER PROFILE
836297202 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

VOLLANE GRAVING AS

Org. no. 836297202 Limited company (AS) Vegårshei Incorporated 2025 Active
Revenue 2025 NOK 51,000
Operating profit NOK 20,000
Equity NOK 46,000
Incorporated 2025
Share capital NOK 30,000

VOLLANE GRAVING AS is registered as a limited company in Vegårshei, Agder with organisation number 836297202. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Entreprenørvirksomhet innenfor bygg og anlegg 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 51,000 in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 51,000
Operating profit
NOK 20,000
Equity
NOK 46,000
Est. value
NOK 78,000

Financial health · 2025

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

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

Who owns VOLLANE GRAVING AS?

VOLLANE GRAVING AS
NOK 51,000 rev. · NOK 20,000 profit

VOLLANE GRAVING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOLLANE GRAVING AS

Who owns VOLLANE GRAVING AS?

Bjørn Kåre Heum is the largest registered owner, with 100.0%.

What is the revenue of VOLLANE GRAVING AS?

VOLLANE GRAVING AS had revenue of NOK 51,000 in 2025.

Who is the general manager of VOLLANE GRAVING AS?

Bjørn Kåre Heum is registered as general manager of VOLLANE GRAVING AS.

Where is VOLLANE GRAVING AS based?

VOLLANE GRAVING 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.