BIZTRAC BETA
Other captive investment companies

KALFARLIEN AS

Org. no. 914118883 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 210,000
Incorporated 2014
Share capital NOK 224,000

Signals

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

KALFARLIEN AS is registered as a limited company in Bergen, Vestland with organisation number 914118883. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 224,000, divided into 2240 shares. The company's stated purpose is: “Eie aksjer, andeler i andre virksomheter samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 210,000
Est. value
NOK 192,000

Financial health · 2025

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

Who owns KALFARLIEN AS?

PETTER ANDREAS ALFSEN
KALFARLIEN AS
NOK 0 rev. · NOK −4,000 profit

KALFARLIEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KALFARLIEN AS own?

KALFARLIEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KALFARLIEN AS

Who owns KALFARLIEN AS?

PETTER ANDREAS ALFSEN is the largest registered owner, with 100.0%.

What is the revenue of KALFARLIEN AS?

KALFARLIEN AS had revenue of NOK 0 in 2025.

Who is the general manager of KALFARLIEN AS?

Petter Andreas Alfsen is registered as general manager of KALFARLIEN AS.

Where is KALFARLIEN AS based?

KALFARLIEN AS has its business address in Bergen.

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.