BIZTRAC BETA
Site preparation

GRAVESERVICE KIRKENES AS

Org. no. 931041657 Limited company (AS) Sør-Varanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK 998,000
Equity NOK 1.2m
Incorporated 2023
Employees 5
Share capital NOK 30,000

GRAVESERVICE KIRKENES AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 931041657. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Graving, transport, brøyting, VA-anlegg, hustomter, kabelgrøfter og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK 998,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK 998,000
Equity
NOK 1.2m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns GRAVESERVICE KIRKENES AS?

MORTEN IVERSEN IHLER
GRAVESERVICE KIRKENES AS
NOK 7.6m rev. · NOK 998,000 profit

GRAVESERVICE KIRKENES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRAVESERVICE KIRKENES AS

Who owns GRAVESERVICE KIRKENES AS?

MORTEN IVERSEN IHLER is the largest registered owner, with 50.0%.

What is the revenue of GRAVESERVICE KIRKENES AS?

GRAVESERVICE KIRKENES AS had revenue of NOK 7.6m in 2024.

Who is the general manager of GRAVESERVICE KIRKENES AS?

Martin Iversen Ihler is registered as general manager of GRAVESERVICE KIRKENES AS.

Where is GRAVESERVICE KIRKENES AS based?

GRAVESERVICE KIRKENES AS has its business address in Hesseng.

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.