BIZTRAC BETA
Other support activities for petroleum and natural gas extraction

KIMEK OFFSHORE RESOURCES AS

Org. no. 991314482 Limited company (AS) Sør-Varanger Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 1.2m
Incorporated 2007
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KIMEK OFFSHORE RESOURCES AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 991314482. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2007. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Drive næringsmessige aktiviteter i Norge og Russland, samt annen relevant næringsmessig virksomhet i ethvert marked.”.

Key figures · 2025

Operating profit
NOK −6,000
Equity
NOK 1.2m
Est. value
NOK 722,000

Financial health · 2025

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

Who owns KIMEK OFFSHORE RESOURCES AS?

KIMEK HOLDING AS
KIMEK OFFSHORE RESOURCES AS
· NOK −6,000 profit

KIMEK OFFSHORE RESOURCES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KIMEK OFFSHORE RESOURCES AS

Who owns KIMEK OFFSHORE RESOURCES AS?

KIMEK HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of KIMEK OFFSHORE RESOURCES AS?

Greger Mannsverk is registered as general manager of KIMEK OFFSHORE RESOURCES AS.

Where is KIMEK OFFSHORE RESOURCES AS based?

KIMEK OFFSHORE RESOURCES AS has its business address in Kirkenes.

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.