BIZTRAC BETA
Rental and operating of own or leased real estate

KORSHAMN EFTF. AS

Org. no. 910064843 Limited company (AS) Oslo Incorporated 1976 Active
Ownership graph ↗
Revenue 2024 NOK 176,000
Operating profit NOK −115,000
Equity NOK 3.8m
Incorporated 1976
Share capital NOK 106,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−115k kr).

KORSHAMN EFTF. AS is registered as a limited company in Oslo, Oslo with organisation number 910064843. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1976. Registered share capital is NOK 106,000, divided into 425 shares. The company's stated purpose is: “Investering i verdipapirer, aksjer, fast eiendom samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 176,000 in revenue and NOK −115,000 in operating profit.

Key figures · 2024

Revenue
NOK 176,000
Operating profit
NOK −115,000
Equity
NOK 3.8m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns KORSHAMN EFTF. AS?

HENRIK ANDREAS JENSEN
KORSHAMN EFTF. AS
NOK 176,000 rev. · NOK −115,000 profit

KORSHAMN EFTF. AS has 6 registered shareholders:

All shareholders and roles →

Which companies does KORSHAMN EFTF. AS own?

KORSHAMN EFTF. AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about KORSHAMN EFTF. AS

Who owns KORSHAMN EFTF. AS?

HENRIK ANDREAS JENSEN is the largest registered owner, with 68.0%.

What is the revenue of KORSHAMN EFTF. AS?

KORSHAMN EFTF. AS had revenue of NOK 176,000 in 2024.

Where is KORSHAMN EFTF. AS based?

KORSHAMN EFTF. AS has its business address in Oslo.

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.