BIZTRAC BETA
Rental and operating of own or leased real estate

BJARNE NILSEN EIENDOM AS

Org. no. 929581601 Limited company (AS) Hammerfest Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 6,000
Equity NOK 1.4m
Incorporated 2022
Share capital NOK 100,000

BJARNE NILSEN EIENDOM AS is registered as a limited company in Hammerfest, Finnmark with organisation number 929581601. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Eie og drive fast eiendom, eie aksjer og andeler i andre selskaper og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 6,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 6,000
Equity
NOK 1.4m
Est. value
NOK 935,000

Financial health · 2024

Liquidity
0.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.9%
Weak
Equity as a share of total capital

Who owns BJARNE NILSEN EIENDOM AS?

KBN HOLDING AS
BJARNE NILSEN EIENDOM AS
NOK 1.0m rev. · NOK 6,000 profit

BJARNE NILSEN EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BJARNE NILSEN EIENDOM AS own?

BJARNE NILSEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJARNE NILSEN EIENDOM AS

Who owns BJARNE NILSEN EIENDOM AS?

KBN HOLDING AS is the largest registered owner, with 42.5%.

What is the revenue of BJARNE NILSEN EIENDOM AS?

BJARNE NILSEN EIENDOM AS had revenue of NOK 1.0m in 2024.

Where is BJARNE NILSEN EIENDOM AS based?

BJARNE NILSEN EIENDOM AS has its business address in Forsøl.

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.