BIZTRAC BETA
COMPANY REGISTER PROFILE
921803036 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

VOLLGRAV AS

Org. no. 921803036 Limited company (AS) Bodø Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 1.8m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

VOLLGRAV AS is registered as a limited company in Bodø, Nordland with organisation number 921803036. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet.”.

Former names: JOHAN LØVOLD AS

Key figures · 2025

Operating profit
NOK −11,000
▼ −21 %
Equity
NOK 1.8m
▲ +37 %
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
261.29
Very good
Current assets ÷ current liabilities
Profitability
31.3%
Very good
Return on total assets
Solidity
99.6%
Very good
Equity as a share of total capital

Who owns VOLLGRAV AS?

VOLLGRAV AS
· NOK −11,000 profit

VOLLGRAV AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VOLLGRAV AS own?

VOLLGRAV AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VOLLGRAV AS

Who owns VOLLGRAV AS?

JOHAN ANDRÉ LØVOLD is the largest registered owner, with 100.0%.

Where is VOLLGRAV AS based?

VOLLGRAV AS has its business address in Bodø.

Property

Business address Langåsveien 28B, 8010 Bodø
Cadastral unit 1804-31/90/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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