BIZTRAC BETA
Rental and operating of own or leased real estate

AILO EIENDOM AS

Org. no. 913886119 Limited company (AS) Kautokeino Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 206,000
Operating profit NOK −118,000
Equity NOK −1.1m
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−118k kr).

AILO EIENDOM AS is registered as a limited company in Kautokeino, Finnmark with organisation number 913886119. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å eie, utvikle, kjøpe, selge og leie ut egne og andres eiendommer og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 206,000 in revenue and NOK −118,000 in operating profit.

Key figures · 2024

Revenue
NOK 206,000
Operating profit
NOK −118,000
Equity
NOK −1.1m

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-75.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AILO EIENDOM AS?

AILO HOLDING AS
AILO EIENDOM AS
NOK 206,000 rev. · NOK −118,000 profit

AILO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AILO EIENDOM AS

Who owns AILO EIENDOM AS?

AILO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AILO EIENDOM AS?

AILO EIENDOM AS had revenue of NOK 206,000 in 2024.

Where is AILO EIENDOM AS based?

AILO EIENDOM AS has its business address in Kautokeino.

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.