BIZTRAC BETA
Rental and operating of own or leased real estate

FISCHER & KNUTSEN EIENDOM AS

Org. no. 970896848 Limited company (AS) Haugesund Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 12.0m
Operating profit NOK 7.0m
Equity NOK 7.7m
Incorporated 1994
Share capital NOK 1.0m

FISCHER & KNUTSEN EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 970896848. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1994. Registered share capital is NOK 1.0m. The company's stated purpose is: “Kjøp og salg av varer og tjenester samt kjøp, salg og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.0m in revenue and NOK 7.0m in operating profit.

Key figures · 2024

Revenue
NOK 12.0m
Operating profit
NOK 7.0m
Equity
NOK 7.7m
Est. value
NOK 20.6m

Financial health · 2024

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.8%
Good
Equity as a share of total capital

Who owns FISCHER & KNUTSEN EIENDOM AS?

JK EIENDOM HOLDING AS
FISCHER & KNUTSEN EIENDOM AS
NOK 12.0m rev. · NOK 7.0m profit

FISCHER & KNUTSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FISCHER & KNUTSEN EIENDOM AS

Who owns FISCHER & KNUTSEN EIENDOM AS?

JK EIENDOM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FISCHER & KNUTSEN EIENDOM AS?

FISCHER & KNUTSEN EIENDOM AS had revenue of NOK 12.0m in 2024.

Who is the general manager of FISCHER & KNUTSEN EIENDOM AS?

Gudmund Jonny Knutsen is registered as general manager of FISCHER & KNUTSEN EIENDOM AS.

Where is FISCHER & KNUTSEN EIENDOM AS based?

FISCHER & KNUTSEN EIENDOM AS has its business address in Haugesund.

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.