BIZTRAC BETA
Site preparation

GRAV OG PLAN AS

Org. no. 914861659 Limited company (AS) Porsanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 395,000
Operating profit NOK −6,000
Equity NOK 115,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

GRAV OG PLAN AS is registered as a limited company in Porsanger, Finnmark with organisation number 914861659. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenester innen maskinentreprenør, anleggsvirksomhet innenfor bygg og anlegg, diverse reparasjoner, salg av sportsutstyr, samt annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 395,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 395,000
Operating profit
NOK −6,000
Equity
NOK 115,000
Est. value
NOK 187,000

Financial health · 2025

Liquidity
2.70
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
62.9%
Very good
Equity as a share of total capital

Who owns GRAV OG PLAN AS?

KRISTIAN ØVERVOLD
GRAV OG PLAN AS
NOK 395,000 rev. · NOK −6,000 profit

GRAV OG PLAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRAV OG PLAN AS

Who owns GRAV OG PLAN AS?

KRISTIAN ØVERVOLD is the largest registered owner, with 100.0%.

What is the revenue of GRAV OG PLAN AS?

GRAV OG PLAN AS had revenue of NOK 395,000 in 2025.

Who is the general manager of GRAV OG PLAN AS?

Kristian Øvervold is registered as general manager of GRAV OG PLAN AS.

Where is GRAV OG PLAN AS based?

GRAV OG PLAN AS has its business address in Lakselv.

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.