BIZTRAC BETA
Rental and operating of own or leased real estate

FAG EIENDOM AS

Org. no. 968944681 Limited company (AS) Nord-Aurdal Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 186,000
Operating profit NOK 408
Equity NOK 789,000
Incorporated 1994
Share capital NOK 525,000

FAG EIENDOM AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 968944681. 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 525,000, divided into 525 shares. The company's stated purpose is: “Utleie, kjøp og salg av fast eiendom, drift og forvaltning av eiendom, samt alt hva hermed står i forbindelse. Herunder deltagelse i andre forretningsforetak knyttet til eiendom under selskapets forvaltning.”. The most recent filed accounts, for the 2024 financial year, show NOK 186,000 in revenue and NOK 408 in operating profit.

Key figures · 2024

Revenue
NOK 186,000
Operating profit
NOK 408
Equity
NOK 789,000
Est. value
NOK 541,000

Financial health · 2024

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

Who owns FAG EIENDOM AS?

THOR IVAR BREISETH
FAG EIENDOM AS
NOK 186,000 rev. · NOK 408 profit

FAG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FAG EIENDOM AS

Who owns FAG EIENDOM AS?

THOR IVAR BREISETH is the largest registered owner, with 100.0%.

What is the revenue of FAG EIENDOM AS?

FAG EIENDOM AS had revenue of NOK 186,000 in 2024.

Who is the general manager of FAG EIENDOM AS?

Thor Ivar Breiseth is registered as general manager of FAG EIENDOM AS.

Where is FAG EIENDOM AS based?

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