BIZTRAC BETA
Development of building projects

AFL EIENDOM AS

Org. no. 999241891 Limited company (AS) Narvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 200,000
Operating profit NOK 118,000
Equity NOK 174,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AFL EIENDOM AS is registered as a limited company in Narvik, Nordland with organisation number 999241891. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikling, salg og utleie av eiendom, samt hertil tilhørende virksomhet, herunder deltakelse og eierskap i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 200,000 in revenue and NOK 118,000 in operating profit.

Key figures · 2024

Revenue
NOK 200,000
Operating profit
NOK 118,000
Equity
NOK 174,000
Est. value
NOK 321,000

Financial health · 2024

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

Who owns AFL EIENDOM AS?

MASKIN-INVEST AS
AFL EIENDOM AS
NOK 200,000 rev. · NOK 118,000 profit

AFL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AFL EIENDOM AS

Who owns AFL EIENDOM AS?

MASKIN-INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of AFL EIENDOM AS?

AFL EIENDOM AS had revenue of NOK 200,000 in 2024.

Who is the general manager of AFL EIENDOM AS?

Anders Lindorff is registered as general manager of AFL EIENDOM AS.

Where is AFL EIENDOM AS based?

AFL EIENDOM AS has its business address in Narvik.

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.