BIZTRAC BETA
Rental and operating of own or leased real estate

KJØLLEFJORD EIENDOM AS

Org. no. 933037460 Limited company (AS) Lebesby Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −4,000
Equity NOK 141,000
Incorporated 2024
Share capital NOK 150,000

Signals

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

KJØLLEFJORD EIENDOM AS is registered as a limited company in Lebesby, Finnmark with organisation number 933037460. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 150,000, divided into 150000 shares. The company's stated purpose is: “Tilby utleie av fast eiendom, inkludert, men ikke begrenset til, utleie av boliger, kontorer, kommersielle eiendommer, lagerplasser, og andre typer fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 141,000
Est. value
NOK 128,000

Financial health · 2024

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

Who owns KJØLLEFJORD EIENDOM AS?

PER JØRGEN IRGENS SØRBØ
KJØLLEFJORD EIENDOM AS
NOK 0 rev. · NOK −4,000 profit

KJØLLEFJORD EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KJØLLEFJORD EIENDOM AS

Who owns KJØLLEFJORD EIENDOM AS?

PER JØRGEN IRGENS SØRBØ is the largest registered owner, with 20.0%.

What is the revenue of KJØLLEFJORD EIENDOM AS?

KJØLLEFJORD EIENDOM AS had revenue of NOK 0 in 2024.

Where is KJØLLEFJORD EIENDOM AS based?

KJØLLEFJORD EIENDOM AS has its business address in Kjøllefjord.

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.