BIZTRAC BETA
Rental and operating of own or leased real estate

FAGERNES EIENDOM AS

Org. no. 997738535 Limited company (AS) Nord-Aurdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −425,000
Equity NOK 4.9m
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−425k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FAGERNES EIENDOM AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 997738535. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Leie og eie egen fast eiendom, samt videreutvikle denne.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −425,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −425,000
Equity
NOK 4.9m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns FAGERNES EIENDOM AS?

AKERSHUS HANDELSSELSKAP AS
FAGERNES EIENDOM AS
NOK 2.1m rev. · NOK −425,000 profit

FAGERNES EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FAGERNES EIENDOM AS

Who owns FAGERNES EIENDOM AS?

AKERSHUS HANDELSSELSKAP AS is the largest registered owner, with 100.0%.

What is the revenue of FAGERNES EIENDOM AS?

FAGERNES EIENDOM AS had revenue of NOK 2.1m in 2024.

Where is FAGERNES EIENDOM AS based?

FAGERNES EIENDOM AS has its business address in Fagernes.

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.