BIZTRAC BETA
Rental and operating of own or leased real estate

AKLA EIENDOM AS

Org. no. 922895724 Limited company (AS) Grimstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 189,000
Operating profit NOK −54,000
Equity NOK 1.5m
Incorporated 2019
Share capital NOK 1.9m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−54k kr).

AKLA EIENDOM AS is registered as a limited company in Grimstad, Agder with organisation number 922895724. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 1.9m, divided into 18889 shares. The company's stated purpose is: “Eie aksjer i bygg og eiendom, samt investeringer i andre selskap og annet som anses tilknyttet dette selskap og dette selskaps virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 189,000 in revenue and NOK −54,000 in operating profit.

Key figures · 2025

Revenue
NOK 189,000
Operating profit
NOK −54,000
Equity
NOK 1.5m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns AKLA EIENDOM AS?

KJELL MAGNE MARKHUS
AKLA EIENDOM AS
NOK 189,000 rev. · NOK −54,000 profit

AKLA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKLA EIENDOM AS

Who owns AKLA EIENDOM AS?

KJELL MAGNE MARKHUS is the largest registered owner, with 100.0%.

What is the revenue of AKLA EIENDOM AS?

AKLA EIENDOM AS had revenue of NOK 189,000 in 2025.

Who is the general manager of AKLA EIENDOM AS?

Kjell Magne Markhus is registered as general manager of AKLA EIENDOM AS.

Where is AKLA EIENDOM AS based?

AKLA EIENDOM AS has its business address in Grimstad.

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.