BIZTRAC BETA
Uoppgitt

AEGIS EIENDOM AS

Org. no. 935700345 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 91,000
Operating profit NOK −21,000
Equity NOK −19,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−19k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

AEGIS EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 935700345. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive med eiendomsutvikling, utleie av eiendom, kjøp og salg av eiendom og vedlikehold av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 91,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 91,000
Operating profit
NOK −21,000
Equity
NOK −19,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.4%
Weak
Equity as a share of total capital

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

Who owns AEGIS EIENDOM AS?

AEGIS INVEST AS
AEGIS EIENDOM AS
NOK 91,000 rev. · NOK −21,000 profit

AEGIS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AEGIS EIENDOM AS

Who owns AEGIS EIENDOM AS?

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

What is the revenue of AEGIS EIENDOM AS?

AEGIS EIENDOM AS had revenue of NOK 91,000 in 2025.

Who is the general manager of AEGIS EIENDOM AS?

Eivind Bakke Knudtzon is registered as general manager of AEGIS EIENDOM AS.

Where is AEGIS EIENDOM AS based?

AEGIS EIENDOM AS has its business address in Bergen.

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.