BIZTRAC BETA
Rental and operating of own or leased real estate

FURNES EIENDOM AS

Org. no. 924899689 Limited company (AS) Stange Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 10.4m
Operating profit NOK 7.9m
Equity NOK 15.9m
Incorporated 2019
Share capital NOK 4.9m

FURNES EIENDOM AS is registered as a limited company in Stange, Innlandet with organisation number 924899689. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 4.9m, divided into 1000 shares. The company's stated purpose is: “Å eie og forvalte eiendom, samt annen økonomisk virksomhet, herunder investeringer i aksjer, fast eiendom og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.4m in revenue and NOK 7.9m in operating profit.

Key figures · 2024

Revenue
NOK 10.4m
Operating profit
NOK 7.9m
Equity
NOK 15.9m
Est. value
NOK 25.5m

Financial health · 2024

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.1%
Good
Equity as a share of total capital

Who owns FURNES EIENDOM AS?

JERN EJENDOMME APS
FURNES EIENDOM AS
NOK 10.4m rev. · NOK 7.9m profit

FURNES EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FURNES EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about FURNES EIENDOM AS

Who owns FURNES EIENDOM AS?

JERN EJENDOMME APS is the largest registered owner, with 100.0%.

What is the revenue of FURNES EIENDOM AS?

FURNES EIENDOM AS had revenue of NOK 10.4m in 2024.

Who is the general manager of FURNES EIENDOM AS?

Jacob Kjær is registered as general manager of FURNES EIENDOM AS.

Where is FURNES EIENDOM AS based?

FURNES EIENDOM AS has its business address in Stange.

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.