BIZTRAC BETA
Rental and operating of own or leased real estate

AKA EIENDOM AS

Org. no. 924307846 Limited company (AS) Bodø Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 23,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

AKA EIENDOM AS is registered as a limited company in Bodø, Nordland with organisation number 924307846. 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 30,000, divided into 300 shares. The company's stated purpose is: “Invester i eiendom og aksjer i andre selskaper, herunder all virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 23,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns AKA EIENDOM AS?

THOMAS TEIGSTAD
AKA EIENDOM AS
NOK 0 rev. · NOK −7,000 profit

AKA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does AKA EIENDOM AS own?

AKA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AKA EIENDOM AS

Who owns AKA EIENDOM AS?

THOMAS TEIGSTAD is the largest registered owner, with 50.0%.

What is the revenue of AKA EIENDOM AS?

AKA EIENDOM AS had revenue of NOK 0 in 2025.

Where is AKA EIENDOM AS based?

AKA EIENDOM AS has its business address in Bodø.

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.