BIZTRAC BETA
Operation of marine hatcheries

KNIVE LAKS AS

Org. no. 821645042 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −36,000
Equity NOK 614,000
Incorporated 2018
Share capital NOK 500,000

Signals

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

KNIVE LAKS AS is registered as a limited company in Drammen, Buskerud with organisation number 821645042. The business is classified under operation of marine hatcheries (NACE 03.212). The company was incorporated in 2018. Registered share capital is NOK 500,000, divided into 50000 shares. The company's stated purpose is: “Investering i aksjer og eiendom, samt det som naturlig hører innunder dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 614,000
Est. value
NOK 584,000

Financial health · 2025

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

Who owns KNIVE LAKS AS?

KNIVE GÅRD AS
KNIVE LAKS AS
NOK 0 rev. · NOK −36,000 profit

KNIVE LAKS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KNIVE LAKS AS own?

KNIVE LAKS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KNIVE LAKS AS

Who owns KNIVE LAKS AS?

KNIVE GÅRD AS is the largest registered owner, with 100.0%.

What is the revenue of KNIVE LAKS AS?

KNIVE LAKS AS had revenue of NOK 0 in 2025.

Who is the general manager of KNIVE LAKS AS?

Knut Langeteig is registered as general manager of KNIVE LAKS AS.

Where is KNIVE LAKS AS based?

KNIVE LAKS AS has its business address in Drammen.

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.