BIZTRAC BETA
COMPANY REGISTER PROFILE
990753105 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 25.08.2026
Rental and operating of own or leased real estate

HAVBRUKSKONTROLL AS

Org. no. 990753105 Limited company (AS) Karmøy Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 487,000
Equity NOK 750,000
Incorporated 2006
Share capital NOK 194,000

HAVBRUKSKONTROLL AS is registered as a limited company in Karmøy, Rogaland with organisation number 990753105. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 194,000, divided into 194 shares. The company's stated purpose is: “Investeringer i fast eiendom, eie og forvalte verdipapirer samt hva hermed står i forbindelse, herunder delta i andre foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 487,000 in operating profit.

Former names: KHV OFFSHORE HOLDING AS

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 487,000
▲ +408 %
Equity
NOK 750,000
▲ +200 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
4.04
Very good
Current assets ÷ current liabilities
Profitability
54.1%
Very good
Return on total assets
Solidity
81.2%
Very good
Equity as a share of total capital

Who owns HAVBRUKSKONTROLL AS?

HAVBRUKSKONTROLL AS
NOK 1.5m rev. · NOK 487,000 profit

HAVBRUKSKONTROLL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAVBRUKSKONTROLL AS

Who owns HAVBRUKSKONTROLL AS?

GEIR IVAR LANES is the largest registered owner, with 100.0%.

What is the revenue of HAVBRUKSKONTROLL AS?

HAVBRUKSKONTROLL AS had revenue of NOK 1.5m in 2025.

Where is HAVBRUKSKONTROLL AS based?

HAVBRUKSKONTROLL AS has its business address in Kopervik.

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

Report a problem

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