BIZTRAC BETA
COMPANY REGISTER PROFILE
997738535 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
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 2025 NOK 2.4m
Operating profit NOK 1.3m
Equity NOK 4.8m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • 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 2025 financial year, show NOK 2.4m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
▲ +17 %
Operating profit
NOK 1.3m
▲ +412 %
Equity
NOK 4.8m
▼ −1 %
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
12.4%
Good
Return on total assets
Solidity
42.5%
Very good
Equity as a share of total capital

Who owns FAGERNES EIENDOM AS?

FAGERNES EIENDOM AS
NOK 2.4m rev. · NOK 1.3m 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.4m in 2025.

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 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.