BIZTRAC BETA
Construction of residential and non-residential buildings

AAFAG EIENDOM AS

Org. no. 992244542 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 1.6m
Equity NOK 1.4m
Incorporated 2008
Share capital NOK 50,000

AAFAG EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 992244542. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Selskapets virksomhet er: Bygge, eie, drive og utvikle eiendommer for utleie eller salg og ellers drive annen forretningsvirksomhet som naturlig hører til, herunder delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 1.6m
Equity
NOK 1.4m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns AAFAG EIENDOM AS?

FREDRIK FAGERLI
AAFAG EIENDOM AS
NOK 4.1m rev. · NOK 1.6m profit

AAFAG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AAFAG EIENDOM AS

Who owns AAFAG EIENDOM AS?

FREDRIK FAGERLI is the largest registered owner, with 100.0%.

What is the revenue of AAFAG EIENDOM AS?

AAFAG EIENDOM AS had revenue of NOK 4.1m in 2025.

Who is the general manager of AAFAG EIENDOM AS?

Fredrik Fagerli is registered as general manager of AAFAG EIENDOM AS.

Where is AAFAG EIENDOM AS based?

AAFAG EIENDOM AS has its business address in Trondheim.

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.