biztrac. BETA
COMPANY REGISTER PROFILE
915593658 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

GRAVINORD AS

Org. no. 915593658 Limited company (AS) Narvik Incorporated 2015 Active
Revenue 2024 NOK 12.1m
Operating profit NOK 785,000
Equity NOK 1.2m
Incorporated 2015
Employees 9
Share capital NOK 640,000

GRAVINORD AS is registered as a limited company in Narvik, Nordland with organisation number 915593658. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015 and has 9 registered employees. Registered share capital is NOK 640,000, divided into 640 shares. The company's stated purpose is: “Kjøp, salg og utleie av utstyr innen håndverkbransjen, salg av transporttjenester og deltagelse i andre virksomheter, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.1m in revenue and NOK 785,000 in operating profit.

Former names: EIENDOM I NORD AS

Key figures · 2024

Revenue
NOK 12.1m
▼ −31 %
Operating profit
NOK 785,000
▲ +209 %
Equity
NOK 1.2m
▲ +84 %
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
0.81
Weak
Current assets ÷ current liabilities
Profitability
13.2%
Good
Return on total assets
Solidity
26.6%
Good
Equity as a share of total capital

Who owns GRAVINORD AS?

GRAVINORD AS
NOK 12.1m rev. · NOK 785,000 profit

GRAVINORD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRAVINORD AS

Who owns GRAVINORD AS?

Knut Håvard Kristoffersen is the largest registered owner, with 100.0%.

What is the revenue of GRAVINORD AS?

GRAVINORD AS had revenue of NOK 12.1m in 2024.

Who is the general manager of GRAVINORD AS?

Knut Håvard Kristoffersen is registered as general manager of GRAVINORD AS.

Where is GRAVINORD AS based?

GRAVINORD AS has its business address in Bjerkvik.

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.